Bring your own key
Connect your own Anthropic or OpenAI API key to ASE: AI usage is billed to your provider account, token quotas no longer apply, and your key is stored encrypted.
By default your agents run on ASE's platform key, within your plan's token quota. With BYOK you connect your own Anthropic or OpenAI key instead: AI calls go to your provider account and are billed there.
What changes
- Token quotas no longer apply; the message quota of your plan still does.
- All other limits (agents, domains, entries, intents) are unchanged.
- You can pick models from your provider in Agent Settings: Claude models with an Anthropic key, GPT models with an OpenAI key.
- AI tool runs are billed to your key as well.
Connect a key
- Open Account and scroll to BYOK.
- Click Add Anthropic Key (keys start with
sk-ant-, from console.anthropic.com) or Add OpenAI Key (keys start withsk-, from platform.openai.com). - Paste the key and save. It is shown once; afterwards the panel only shows that a key is connected.
Agents switch to your key immediately. To go back to the platform key, remove the key on the same page.
Is my key safe?
Keys are encrypted before they are stored and decrypted only on the server at the moment of an API call. They are never sent to the browser or shown in any response. If you think a key has leaked, remove it in ASE and revoke it in your provider's console.
Prompt caching
ASE marks the stable part of each request (your system prompt and knowledge base) for caching with Anthropic. Repeated requests reuse the cache at a fraction of the input price, so a large knowledge base costs much less than its token count suggests. Caching works the same on the platform key and on your own Anthropic key; your Anthropic console shows the cache read and write breakdown. OpenAI applies its own automatic caching to long prompts.