Connect Anthropic
Add your Claude Analytics, Claude Platform, and Compliance API keys so Tokenize can read Claude usage, spend, and budgets.
Tokenize connects to Anthropic with up to three keys. Each one comes from a different place and unlocks different parts of the dashboard. You can add any of them on their own.
The keys live in the Anthropic section of Settings → Providers. Click a section title, such as Claude Analytics, to open it. A check mark before the title means a working key is saved. The Claude Analytics and Compliance API key sections carry an Enterprise badge: they need a Claude Enterprise plan.
Who can do this: Admins in Tokenize. Each key also needs the right admin role on the Anthropic side, listed below.
Which key do you need
| Key | Where it comes from | What it unlocks in Tokenize |
|---|---|---|
| Claude Analytics | claude.ai admin settings | Claude analytics, the member directory, and reading and changing per-person budgets. Spend billed to service accounts counts in organization totals. |
| Claude Platform | Claude Platform (Console) admin keys | Usage and cost reports, API key metadata, and Claude Code analytics for API usage. This feeds Platform Usage. |
| Compliance API key | claude.ai admin settings, Compliance API | Read access to the compliance activity feed, organization data, and user data |
The Claude Analytics key and the Claude Platform key are different key types. One does not work in the other's slot.
Add the Claude Analytics key
A Claude Enterprise Owner or Primary Owner must create this key.
- Open API access in your claude.ai admin settings. Enable the Analytics API, then choose Create key.
- Enable these scopes:
read:analyticsread:membersread:spend_limitswrite:spend_limits
- Copy the key.
- In Tokenize, go to Settings → Providers. In the Anthropic section, open Claude Analytics, paste the key into API key, and click Save.
Tokenize needs read:spend_limits to accept the key. Anthropic fixes a key's scopes when you create it. If you leave out write:spend_limits, Tokenize can show budgets but can't change them. To add a scope later, create a new key and replace the old one. See Budgets.
Add the Claude Platform key
A Claude Platform admin must create this key.
- Open Admin API keys in Claude Platform.
- Choose Create admin key.
- Copy the key.
- In Tokenize, open Claude Platform, paste it into API key, and click Save.
A regular model API key is not accepted here. It must be an organization Admin API key.
Add the Compliance API key
A Claude Enterprise Primary Owner must create this key.
- Open API access in your claude.ai admin settings and turn on the Compliance API. Anthropic's setup documentation has more detail.
- Choose Create key and enable these scopes:
read:compliance_activitiesread:compliance_user_dataread:compliance_org_data
- Copy the key.
- In Tokenize, open Compliance API key, paste it into API key, and click Save.
Tokenize only asks for read scopes. It never deletes provider data, so leave the delete scope off. Tokenize checks all three read scopes when you save. If any of them fails, the key is still saved with the unverified badge and the panel says "Key saved. Some permissions couldn't be confirmed." The lines Compliance activity feed, Compliance organization data, and Compliance user data show which check failed. Create a key with every scope above and click Replace.
After you save
Tokenize checks the key with Anthropic before storing it. The panel then shows the last four characters of the key, a status badge, when the key was last checked, and one line per feature with the result of the access check. See Provider key errors for what each status and message means.
Every How to create a key link inside a section opens these same steps.
To disconnect a key, click Revoke (or Remove for the Compliance API key). Data Tokenize already read stays. The source stops being read.