GPT API access, up to 90% off list price

Router One is an LLM API gateway that resells metered GPT API access at posted per-token rates — select GPT models go as low as 10% of official list prices (up to 90% off) — on both /v1/chat/completions and the native /v1/responses wire format Codex CLI needs, with a cost trace for every request and top-ups that need no US credit card. If your product runs on GPT-family models, the token bill is its biggest line item; every rate is posted per token on the /models page.

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 GPT model lists its current input/output and cache rates on /models, struck through against the base rate, 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 GPT call in 3 steps

Create a key, top up in your currency, and point any OpenAI-compatible client at the gateway — 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 by card or Alipay on the hosted checkout, or with USDT/USDC — no US credit card required.
2. 2Point your client at the gatewaySet the base URL to https://api.router.one/v1 in any OpenAI SDK or tool. Codex CLI users keep wire_api = "responses" — the gateway implements it natively.
3. 3Verify the cost traceOpen Dashboard → Logs after your first request to see model, tokens, latency, and the exact discounted cost per call.

# OpenAI-compatible — only the base URL changes
curl -X POST https://api.router.one/v1/chat/completions \
  -H "Authorization: Bearer sk-your-router-one-key" \
  -H "Content-Type: application/json" \
  -d '{"model": "<gpt-model-id>",
       "messages": [{"role": "user", "content": "Hello!"}]}'

No low fixed cap for normal paid usage. Abuse prevention, per-account protection limits, and upstream constraints may still apply; if a request returns 429, check Dashboard -> Logs or contact support to raise limits.

FAQ