Bring Your Own OpenAI or Anthropic Key Instead of Paying Platform Markup
How to add your own AI provider key in Settings so requests run on your account at a small platform fee instead of full platform pricing.
If you already have accounts with OpenAI, Anthropic, or another model provider, Settings lets you plug those credentials in directly and run requests on your own account instead of the platform's shared pool. This is the Bring Your Own Key (BYOK) page, under AI Keys in Settings.
How it works
You add a key for a provider — OpenAI, Anthropic, Google AI, Groq, Mistral, Cohere, Perplexity, OpenRouter, Cloudflare (your own account), or a custom OpenAI-compatible endpoint. Once it's saved, requests that use that provider run against your account and your quota, and the platform charges a percentage fee on what the request would have cost here, rather than the full retail price. Which providers exist, and which ones need more than just a key (a custom endpoint needs its own base URL, for instance), is something this page asks the backend for rather than deciding on its own — so the list you see always matches what the platform can actually route to.
What you'll never see again after saving a key
Once a key is saved, there's no way to view it again through the product — not because the UI hides a "reveal" button, but because no endpoint returns the stored value at all. The backend doesn't select the encrypted column when listing your keys; all you get back is the last four characters, enough to confirm which key is which without ever exposing the whole thing. Building a "reveal" feature would mean building a new route capable of decrypting and returning a live credential — arguably the single most sensitive thing this part of the platform could expose, and not something added lightly.
If the fee doesn't match what you expected
The rate shown isn't hardcoded into the page — it's fetched live from the same backend service that actually charges it. That matters because a page quoting one number while the charging logic uses a different one is exactly the kind of mismatch that turns into a support ticket where the user is right and the product is wrong. If you see a rate, it's the rate that will actually apply.
When the form won't let you add a key
If your deployment doesn't have an encryption passphrase configured, the page disables the key inputs and tells you why, rather than accepting a key it can't actually protect. The backend refuses to store a credential it has no way to encrypt — better to find that out before you've pasted a real key into a form than after.
Why this is worth doing even before you plan to switch providers
See the companion piece on why BYOK matters beyond just provider flexibility — cost visibility alone is often reason enough.