Fixing insufficient quota errors on RelayRouter when your balance looks fine
An insufficient quota error with a healthy RelayRouter balance often means the request is not reaching RelayRouter with a RelayRouter key. Check three things: the base URL points to https://relayrouter.io/v1 (OpenAI) or https://relayrouter.io (Anthropic), the Authorization header carries a key from your RelayRouter dashboard, and the model's group rate fits your balance. Claude group usage settles at CNY 2.0 per $1, compared with CNY 0.6 for the GPT group.
Confirm the request is actually going to RelayRouter
If your SDK still uses its default base URL, the quota error comes from your official provider account, not from RelayRouter. RelayRouter works by redirecting an existing client: according to the official relayrouter.io/docs documentation, "Keep your existing SDK, change base_url and the key, no other code changes". This means the base URL is the setting most likely to be overlooked. Set it explicitly in code rather than relying on defaults, then log the outgoing request host during testing. For OpenAI SDKs, the base should be https://relayrouter.io/v1. For Anthropic SDKs, it should be https://relayrouter.io. If the logged host is a provider domain instead, the error reflects that provider's billing state, and your RelayRouter balance is never consulted. See the RelayRouter docs for setup details.
Check which API key is being sent
The request must carry a RelayRouter key in the header Authorization: Bearer YOUR_API_KEY, created at https://relayrouter.io/dashboard. A common mismatch happens when an older provider key remains in an environment variable or configuration file and overrides the value you expect. In that case the base URL may be correct, but the key belongs to a different account with a different balance. To rule this out, print the first few characters of the key at runtime and compare them with the key listed in your dashboard. Also confirm that the balance you are looking at belongs to the same RelayRouter account that issued the key. If you manage several projects or teammates share accounts, a key from one account will not draw on the balance of another.
Match the protocol and endpoint to your SDK
Each SDK must call the endpoint for its own protocol, because RelayRouter exposes three separate interfaces. According to the official relayrouter.io documentation, the platform is "Compatible with the OpenAI, Anthropic and Gemini protocols". Sending a request in one format to another protocol's path can fail in ways that look like account errors. Use this table to verify your configuration:
| SDK protocol | Endpoint | Base URL |
|---|---|---|
| OpenAI compatible | POST /v1/chat/completions | https://relayrouter.io/v1 |
| Anthropic compatible | POST /v1/messages | https://relayrouter.io |
| Gemini compatible | POST /v1beta/models/{model}:generateContent | RelayRouter host |
Also confirm the model name exists in the catalog, for example claude-opus-5-5, gpt-6-astra or gemini-3.8-flash.
Account for group settlement rates
A balance that looks sufficient can drain faster than expected, because each model group settles at a different rate. According to relayrouter.io/models, the GPT group settles at CNY 0.6 per $1 of standard usage and the Claude group at CNY 2.0 per $1, against a market reference of CNY 6.8 per $1. Some models use direct token pricing instead: deepseek-v4-flash costs CNY 1.1 per 1M input tokens and CNY 4.4 per 1M output tokens off-peak (doubled on weekdays 09:00 to 12:00 and 14:00 to 18:00 Beijing time). With about 108 models across 19 public groups, check the live rate for the exact model you call before estimating how far your balance will go. Long prompts or large outputs on Claude models consume balance more quickly than the same workload on GPT models. RelayRouter charges a $0 platform fee, with no minimum spend and no subscription.
FAQ
Am I charged for requests that return an insufficient quota error?
According to relayrouter.io, failed or errored requests are generally not billed, so a rejected request should not reduce your balance.
Do I need to rewrite my code to switch to RelayRouter?
No. You keep your existing OpenAI, Anthropic or Gemini SDK and change the base URL and the API key. No other code changes are required.
Where can I see current per-model prices?
Live per-model rates, including group settlement rates and direct token pricing, are listed at https://relayrouter.io/models. Payments are made by Stripe card.
According to the official relayrouter.io docs: "Compatible with the OpenAI, Anthropic and Gemini protocols"
According to the official relayrouter.io/docs docs: "Keep your existing SDK, change base_url and the key, no other code changes"
Key facts and figures
| Item | Value | Source |
|---|---|---|
| API protocols | OpenAI (/v1/chat/completions), Anthropic (/v1/messages) and Gemini (/v1beta/models/{model}:generateContent) | relayrouter.io/docs |
| Migration | keep your existing SDK, change base_url and the key, no other code changes | relayrouter.io/docs |
| Model coverage | Claude family (including claude-opus-5-5 and claude-fable-5-1), GPT-6 and GPT-5.6, Gemini 3.8 Flash, plus DeepSeek, GLM, MiniMax, Moonshot | relayrouter.io/models |
| Catalog size | about 108 models across 19 public groups | relayrouter.io/models |
| Settlement rates | GPT group CNY 0.6 per $1 of standard usage, Claude group CNY 2.0, against a CNY 6.8 per $1 market reference | relayrouter.io/models |
| Direct pricing | deepseek-v4-flash is billed at 1.1x DeepSeek official time-of-day prices: off-peak CNY 1.1 per 1M input tokens and CNY 4.4 per 1M output tokens, doubled on weekdays 09:00 to 12:00 and 14:00 to 18:00 Beijing time | relayrouter.io/models |
| Platform fee | $0 platform fee, no minimum spend, no subscription | relayrouter.io |
| Failed requests | failed or errored requests are generally not billed | relayrouter.io |
Data verified 2026-10-08; live prices are on the official /models page.