Claude tokens
Which Claude token to save, where it's kept, and how the monthly spending cap counts runs.
Each run uses a Claude token saved on the dashboard. The workflow holds none: the action gets the token from the Axon Shaft API for the run.
The two kinds
| Kind | Who it's for | How to get it |
|---|---|---|
| OAuth token | A Claude Pro or Max plan | Install Claude Code and run claude setup-token. Save what it prints. |
| API key | Claude Console billing | Create one on the Console's API keys page. |
Runs on a plan count against the plan's usage. Runs on an API key are billed to the Console account, and the run's page and the summary comment's footer show what each one cost.
Account or project
The account's admin can save a token on the account's settings, and it covers every project on the account. A project's own token, saved on its Claude token page, wins over the account's. Saving a project's token takes the account's admin, or the Admin or Maintain role on the repo.
The dashboard shows only the kind, the last four characters, who saved it and when. The value is stored encrypted, and no response, error or log line contains it.
Testing a token
The card's Test button sends Anthropic one request for one output token, with the token a run would use: the project's own, else the account's. Only an API key can be tested. Anthropic takes an OAuth token only from Claude Code, so for one the card says it can't be tested.
The monthly spending cap
The account's admin can set a monthly cap in whole US dollars, on the account or on one project.
- Only runs on an API key count, since a run on a plan costs nothing extra.
- The month is the calendar month in UTC.
- A project's own cap counts only that project's runs. The account's cap counts every project without its own.
- Once the month's runs reach the cap, runs end with the
spending_capnotice until the 1st, or until the admin raises the cap.
Last updated on