What is prxy.monster?
prxy.monster makes AI agent work visible, controllable, verifiable, and reusable — with a base URL change. It is the control and receipt layer in front of your existing model calls. It is not an inference provider.
Is this an inference provider?
No. We sit in front of Anthropic, OpenAI, Google, Groq, AWS Bedrock, and OpenRouter. The provider runs the model and bills inference. prxy bills the gateway / control layer separately.
Whose key pays for tokens?
Yours, by default. BYOK: configure your provider key once and the provider bills you directly at list rates. We never mark up provider inference. The MPP route is the exception — agents pay for managed-MPP calls via Stripe SPT after the protocol surface goes through HTTP 402 / quote / sessions / charge.
What is a receipt?
A signed JSON record of one inference call: identity, provider attribution, tokens, cost with pricing-table provenance, pipeline metadata, four canonical request/response hashes, and an Ed25519 signature. Verifiable against the public JWKS at /.well-known/prxy-receipt-keys.json by anyone — no prxy code required.
What is an outcome?
An outcome is a learning signal anchored on a receipt: did this call solve the user's problem, fail it, or land somewhere in between. Positive outcomes feed the memory_candidates queue. A reviewer in lair promotes useful candidates into patterns, which then ride into future calls via the patterns module.
What is retained, by default?
hash_only is the default. We persist the four canonical sha-256 hashes plus receipt metadata. Plaintext request and response bodies are
not stored unless you opt in to
encrypted_at_rest, in which case they are sealed under your X25519 public key. Outcome notes are hashed server-side and never persist in raw form. Full matrix at
/security/data-retention/.
How do modules work across providers?
Each module declares which provider capabilities it requires (chat, streaming, tools, prompt caching, embeddings) and how it falls back. If a capability is missing, the module either skips, degrades, or blocks — never silently corrupts a request. The receipt's module_chain tells you exactly which modules ran.
What is the anonymous sandbox for?
Try the product without a signup or a credit card. The sandbox runs 5 real Bedrock Nova Micro calls and emits 5 signed public_demo receipts you can click into. Do not paste secrets, private code, or customer data — sandbox receipts are public_demo by design.
How does local mode differ?
prxy-monster-local is the MIT self-host edition. Same module API as cloud. No telemetry to prxy.monster, no hosted sync, no managed MPP. State (cache, patterns, archived context) lives in your local volume. Use it when policy or compliance forbids sending traffic through a hosted gateway.
Can agents pay per call?
MPP discovery, the HTTP 402 challenge flow, /v1/agent/quote, and /v1/agent/sessions are live. Production Stripe SPT settlement is gated on Stripe Link SPT GA + production-payment credentials. Until that is configured, paid retries can return verification-failed. Managed MPP is $0.05 per call and includes the upstream model call. The protocol surface is wired end-to-end so you can build against it now.
Open source?
prxy-monster-local, @prxy/module-sdk, and prxy-cli are MIT-licensed on npm. Self-host the entire pipeline on your own infrastructure for free. The hosted gateway, lair operator dashboard, and the receipts ledger surfaces are closed source.
Cancel anytime?
Yes. Stripe customer portal, one click. No retention games. Your API key keeps working until the end of the billing period.
