> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orchestrahq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Your own model key

> Which model key cloud sessions run on, who is billed, and how to add your own Anthropic API key

Cloud sessions talk to an AI model through Orchestra. By default they run on
Orchestra's own model keys, so a new workspace can start one with no setup.
You can add your workspace's own Anthropic API key instead, and Anthropic then
bills your account for this workspace's cloud sessions.

## Which agents run on which key

| Agent | Without your key | With your Anthropic key |
| - | - | - |
| Orchestra (built on the Claude Agent SDK) | Orchestra's key | Your key |
| OpenCode | Orchestra's key | Your key |
| Codex | Orchestra's OpenAI key | Orchestra's OpenAI key |
| Claude Code | Not available in the cloud | Your key |

Claude Code needs your own key to run in the cloud. Its terms do not let a
product pay for Claude Code usage on its users' behalf: each user's usage has
to be billed to them by Anthropic. The Orchestra agent is built on the Claude
Agent SDK, which may run on Orchestra's key, so you can use it without a key
of your own.

Cloud sessions in every workspace have a monthly compute budget and a limit on
how many run at once. Those cover the machines Orchestra runs, so they apply
the same whichever key a session uses.

## Add a key

1. Create an API key in the [Claude Console](https://platform.claude.com/).
2. Open **Settings**, then **Integrations**.
3. Under **Models**, paste the key and click **Save key**.

Orchestra checks the key with Anthropic before saving it, so a mistyped key is
refused at the form rather than at your first session. Once saved, the key is
encrypted and never shown again: Settings shows only a masked form ending in its last four characters,
who added it and when. Saving a new key replaces the old one.

Only an Anthropic API key works here. A Claude subscription sign-in cannot be
used, and Amazon Bedrock, Google Cloud Vertex AI and Microsoft Foundry
credentials are not supported yet.

## Remove a key

Click **Remove** next to the key. It takes effect within a minute: a Claude
Code session that is already running stops at its next model request, and
other sessions carry on, on Orchestra's key. To stop the key working anywhere
at once, also revoke it in the Claude Console.

## Where the key goes

* The key is stored encrypted, per workspace, and only Orchestra's servers
  can read it. No other workspace can read, use or remove it.
* It never enters a session's machine. The agent sends its model requests to
  Orchestra, which adds the key on the way to Anthropic.
* It is never written to Orchestra's history, logs or error messages. Adding
  and removing it are recorded, with who did it and when, but not the key.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.