Claude API access, up to 90% off list price

Router One is an LLM API gateway that resells metered Claude API access at posted per-token rates — the site-wide "up to 90% off official prices" figure is a ceiling reached on select models across the catalog, not a Claude-specific rate; each Claude model's live rate is on /models — through the native /v1/messages endpoint (Claude Code works unchanged) and the OpenAI-compatible /v1/chat/completions, with a cost trace for every request and top-ups that need no US credit card. Same wire format, plus a ledger for every request.

How the discount works

1. 1Metered per token, prepaid walletYou pay the discounted per-token rate shown on the model page — no seats, no minimum commitment. Wallet balance is drawn down per request.
2. 2The catalog is the price sheetEvery Claude model lists its current input and output rates on /models; discounted ones show the base rate struck through, so you can verify the discount before calling.
3. 3Documented methodologyHow Router One sources capacity and sets prices is written up on the pricing methodology page — no mystery meat.

First Claude call in 3 steps

Create a key, top up in your currency, and call /v1/messages — the native Anthropic wire format, reachable from Mainland China without a VPN.

1. 1Create an API keySign up at router.one and create a key in the dashboard. Top up with a card or Alipay in one hosted checkout, or with USDT/USDC — no US credit card required.
2. 2Point your client at the gatewayUse https://api.router.one/v1/messages for the Anthropic-native format (Claude Code works out of the box), or https://api.router.one/v1/chat/completions for OpenAI-compatible clients.
3. 3Verify the cost traceOpen Dashboard → Logs after your first request to see model, tokens, latency, and the exact discounted cost per call.

# Native Anthropic wire format via Router One
curl -X POST https://api.router.one/v1/messages \
  -H "Authorization: Bearer sk-your-router-one-key" \
  -H "Content-Type: application/json" \
  -d '{"model": "<claude-model-id>", "max_tokens": 1024,
       "messages": [{"role": "user", "content": "Hello!"}]}'

No low fixed cap for normal paid usage. Each key and each account runs under default request-per-minute and token-per-minute limits, and upstream constraints may still apply; if a request returns 429, back off and retry (honor Retry-After when it is sent), and if your traffic needs higher limits, email support@router.one to have the key or account limits raised.

FAQ