Bring your own key
Route through your own provider account, keep your negotiated rates, and still get one endpoint and one usage view.
If you already hold an account with a provider — committed spend, negotiated rates, a rate limit you had to ask for — you can point the gateway at it instead of at ours.
What changes
- Billing. Provider charges land on your provider invoice. The gateway charges nothing per token for a request it routed to your key.
- Rate limits. Yours, not the shared pool's.
- Everything else. Same endpoint, same request shape, same metering, same Usage screen.
Adding a key
Add the provider credential from the dashboard. It is encrypted at rest and never returned to the browser once saved — the same one-way handling as your own API keys.
How routing picks
For a given model, the gateway prefers your key when one is on file for that provider and healthy, and falls back to the shared pool when it is not. A provider that starts erroring is taken out of rotation until it recovers.
Still metered
Requests on your own key still write a metering row — tokens, latency, status —
because that is how Usage stays complete. cost_micros records the
catalogue price for reference, and no ledger entry is written, so nothing is
drawn from your balance.