Skip to main content
Scaling does not resell model usage. Sessions run on an Anthropic API key that your organisation brings, and Anthropic bills you for what they use. Add the key once, and every session in the organisation uses it.

​
What you need

  • The admin role in your organisation. A member cannot see the Anthropic key page in the product.
  • An API key from the Anthropic Console.

​
Add the key

Open Anthropic key in the sidebar, paste the key into Anthropic API key, and choose Add key under the field. While you are there the sidebar shows settings. Choose Back to app to return to Runs. The key is checked with Anthropic before it is stored. A key that Anthropic refuses is not stored, and the page says so.

​
What we keep and what you can see

The key is stored encrypted, under an encryption key that belongs to your organisation alone. The page shows the key as sk-ant-… followed by its last four characters, and the date it was added, and nothing more. Nobody can read the key back through Scaling, including you. The field is always empty, even when a key is stored.

​
Replace the key

Paste the new key into New key and choose Replace key under the field. The old one stops being used as soon as the new one is stored. If sessions were paused for the key, the page tells you how many are starting again.

​
When the key stops working

A session pauses at its last completed step when the key is missing, is refused, or keeps being rate limited. No work is lost. The Anthropic key page says how many sessions are waiting. Store a working key and the page tells you how many are starting again. Storing the same key again is fine once its limit has cleared.

​
Remove the key

Choose Remove key and confirm. Running sessions pause the next time they need the key, and stay paused until you add one. When a removal finishes, the page reads the key again and shows what is stored. If the key is still there, the page says The key was not removed and you can try again. If the key is gone, the page shows No key yet, even when the removal reported a problem. If you add a key straight after removing one, the page may answer The previous key is still being removed. Try again in a minute. Wait a minute and add it again.

​
Limits

You can try five keys per organisation in fifteen minutes. A sixth attempt in that window is refused until the oldest one is more than fifteen minutes old.

​
From the API

Reading, storing and removing the key are three requests to /model-key. All three need the admin role.
Response
key is null when the organisation has none. pausedSessions is how many sessions are waiting for one.
Response
resumedSessions is how many paused sessions started again because of this key.
Removing answers with 204 and no body.

​
When it fails

Branch on code, never on message.