Guide
BYOK explained: using your own API keys with an AI workspace
BYOK stands for “bring your own key”. Instead of buying model usage through the app you are working in, you connect an API key from the model provider and the app sends requests on your behalf.
Why people use their own keys
There are three common reasons:
- Billing: usage is charged by the provider to your own account, often one your company already has.
- Policy: some teams are required to send data only through provider accounts under their own agreement.
- Control: you can set spending limits, rotate keys and review usage in the provider’s console.
What BYOK changes, and what it does not
With your own key, requests to that provider no longer use your Bonscape credits. Everything else is the same: branching, merging, the canvas, your files and notes all work as before. You can use keys for some providers and credits for others in the same project.
Bonscape supports keys from Anthropic, OpenAI, Google, xAI, Moonshot (Kimi), DeepSeek and Qwen. A key is verified when you add it and encrypted before it is stored, and you can revoke it at any time.
BYOK or BYOS?
An API key means pay-per-use billing. If what you have is a Claude or ChatGPT subscription, BYOS connects that instead, with no key involved. Both are available on the Core and Pro plans.
If your goal is simply to lower your bill, read how to spend less on AI first. Model choice and shorter context usually matter more than who sends the invoice.