Get and connect your Anthropic key
Every plan runs Live on your own Claude API key (BYOK): create one in the Claude Console and save it once for your organization.
Updated September 30, 2026 · 2 min read
Why your own key
- You pay Anthropic directly. Tokens are billed to your Anthropic account at its prices. The platform doesn't charge for tokens and adds no markup.
- You stay in control. Spend limits, usage reports and revoking the key are in your Claude Console.
- No key yet? Simulation runs every workflow without one, at no cost.
Create the key
Open the Claude Console
Sign in at
console.anthropic.com(create an account with your company e-mail if you don't have one).Add credits
In Billing, add credits: the API is prepaid.
Set a spend limit
In Limits, set a monthly spend limit. It's your safety net.
Create the key
In API Keys, choose Create Key, name it (for example “AI Context Orchestrator”) and copy it. It starts with
sk-ant-and is shown only once.
Connect it
Open Connections
Go to Connections and find Claude (Anthropic).
Save it
Paste the key and save. It's encrypted in the Vault (AES-256-GCM) as soon as it arrives and never comes back to the browser.
Check the test
The app tests the key right away. Connected means Live runs and the Co-Pilot can use it.
A single workflow can use a different key: save it on its Root Orchestrator (Vault). Otherwise every workflow uses the organization's key.
Troubleshooting
| Symptom | What to do |
|---|---|
| “BYOK required” when running Live | No key is saved for the organization or on the Root Orchestrator: connect one as above. |
| The test says the key was refused | It was revoked, mistyped or belongs to another account: create a new one and save it again. |
| Runs stopped with a rate-limit message | Your Anthropic account hit its rate or spend limit: wait, or raise the limit in the Console. |
| You want to rotate it | Save a new key the same way: every workflow follows. Then revoke the old one in the Console. |