Your key, your bill
For requests your key handles, BazaarLink doesn't charge the model cost; if you also use a platform feature such as web search, that feature is billed at platform prices.
You already have BYOK in your account
— you just have to log in to see it.
BazaarLink can act purely as a router, not a middleman: connect your own upstream account and the bill goes straight to you.
When your key has a problem, the request can try another source
Each BYOK key has its own error handling. "Try another available source" (the default) moves on to the next source in your fallback order when your key errors. "Return the error directly" hands a 4xx from your key (except 429) straight back to you, while timeouts, network errors, 429 and 5xx still try the next source. Once a response starts streaming, it stays on that source. Requests handled by a platform model are billed at regular platform rates. You can adjust all of this per key on the Fallback Settings page.
Your BYOK keyFailedAnother available sourceMay tryRequest result
Your key still goes through our content review
BYOK doesn't mean we connect your account and walk away. Before a request reaches your own upstream account, it goes through the same content review as requests on our platform routing; a request judged to violate policy is not sent. You can also turn on sensitive-data filtering at /content-filter to mask keys, card numbers and similar data in prompts before they go out.
Also worth knowing
One endpoint for every provider
Mix your own keys with the providers we proxy, through the same API. Your own key currently serves /v1/chat/completions, /v1/responses, /v1/messages, and image generation (/v1/images).
Usage visibility
See which requests went through your key.
Images can use your key too
Image generation and editing support BYOK: images produced by your key carry no model charge, and images handled by the platform are billed at platform prices.
You set the order and the scope
On the Fallback Settings page, set the source order, per-model sources and platform candidate models, and choose which BazaarLink API keys each source applies to.
Organizations can manage it centrally
Organization admins can set up BYOK keys for the whole organization, with usage tracked per key.
Web search works with your own key
Requests handled by your key can add :online too, so the model checks the web before answering. The search runs on the platform side and the results go to your key together with the question. BazaarLink doesn't charge the model cost — only the search fee, at platform prices — so your account needs enough balance to cover the search.
When you'd use this
You have an enterprise OpenAI contract to work through, but also want to use Claude and Gemini, and don't want to maintain three separate SDKs in your code. BYOK lets you plug in your contracted quota while everything else runs through our routing — your code only ever points at one base URL.
You've connected your own OpenAI key through BYOK, and someone on your team sends a request that violates policy. Before it reaches your upstream, it goes through the same content review as platform routing; if it's judged a violation, it isn't sent.
Ready to set it up?
Add a key, choose how errors are handled, and set the source order and scope — all step by step on the BYOK settings page.
Connect your first key
Five minutes to set up, and from then on, matching requests are handled by your own account.
Set up BYOK