One key, four models: BYOK failover explained
A bring-your-own-key gateway lets you call OpenAI, Anthropic, Zhipu and DeepSeek through a single endpoint, with automatic failover when a key is rate-limited. No token resale involved.
What "failover" means here
You register multiple provider keys as virtual keys. When you call the gateway, it tries your primary. If that provider returns a 429 or 5xx, the gateway retries the next configured key — automatically, in the same request. Your app sees one smooth response.
Why BYOK failover is cleaner than resale failover
| Resale gateway | BYOK gateway | |
|---|---|---|
| Key ownership | Reseller's | Yours |
| Failover target | Reseller's other bulk account | Your own backup key |
| Blast radius if one key dies | All reseller customers | Only you |
Example: route across providers
// Same base_url + virtual key, just change the model field
{ "model": "gpt-4o-mini", "messages": [{"role":"user","content":"hi"}] }
{ "model": "claude-3-5-haiku","messages": [{"role":"user","content":"hi"}] }
{ "model": "glm-4-flash", "messages": [{"role":"user","content":"hi"}] }
Because token cost is billed by each provider to your own account, there is no central balance to exhaust and no resale margin. The gateway is purely the routing layer.
Start routing
Create a virtual key for each provider you use, then call them through one endpoint.
Top comments (0)