prxy.monster API-key BYOK is live. Start free

Quick start — Cloud

Cloud mode is the hosted BYOK gateway. You bring the provider key; prxy.monster runs the module pipeline and meters gateway requests.

Start free

Create an account at lair.prxy.monster/sign-up. No credit card. Free includes 5,000 gateway requests/month — enough to wire your agent and ship real work.

Fastest path: paste the universal agent setup prompt into Claude Code, Cursor, or any coding agent. It walks through key mint + verify in one shot.

Get a PRXY API key

Mint or copy a key in Lair. Keys look like:

prxy_live_a1b2c3d4e5f6...

Keep this secret. Treat it like a provider API key. Revoke and rotate leaked keys from Lair or the key API.

Configure provider access

BYOK means your upstream provider bills you directly. You can register provider keys in Lair, or pass a provider key for supported requests with x-provider-key.

curl https://api.prxy.monster/v1/byok/anthropic \
  -X PUT \
  -H "Authorization: Bearer $PRXY_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "apiKey": "sk-ant-..." }'

Point your app at the gateway

export ANTHROPIC_BASE_URL=https://api.prxy.monster
export ANTHROPIC_API_KEY=prxy_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
import Anthropic from '@anthropic-ai/sdk';
 
const client = new Anthropic();
 
const msg = await client.messages.create({
  model: 'claude-sonnet-4-6',
  max_tokens: 256,
  messages: [{ role: 'user', content: 'hi' }],
});

Verify the pipeline

curl https://api.prxy.monster/v1/pipeline \
  -H "Authorization: Bearer $PRXY_KEY"

Default:

{
  "configured": [],
  "active": [
    { "name": "mcp-optimizer", "version": "1.0.0" },
    { "name": "semantic-cache", "version": "1.0.0" },
    { "name": "patterns", "version": "1.0.0" }
  ],
  "override": null
}

Cache short-circuits set an x-prxy-cache response header naming the module that returned the cached result.

Optional: try MPP discovery

Agents without a prxy key can inspect the MPP surface:

curl https://api.prxy.monster/.well-known/mpp

Discovery, the HTTP 402 challenge flow, /v1/agent/quote, /v1/agent/sessions, production settlement, and Payment-Receipt headers are live for the managed MPP route. ATXP MCP, native x402, and Tempo remain separate blocked or planned rails. See Agent payments.

What just happened?

Your request used the API-key BYOK flow:

  1. prxy authenticated Authorization: Bearer $PRXY_KEY.
  2. The configured module pipeline ran.
  3. If nothing short-circuited, prxy forwarded to your provider key.
  4. Your provider billed you for tokens; prxy counted one gateway request.

Next steps