Anthropic Claude Integration for LLM Cost Tracker
This guide explains how to connect an Anthropic Claude API organization to Binadox using an Anthropic Admin API key. You will create the key in the Claude Console and use it in Binadox to complete the connection.
Once connected, Binadox reads your organization’s usage and cost reports on a schedule, so you can see token consumption by model, workspace, API key and service tier, follow daily spend, and compare Claude prices with your other LLM providers to cut costs.
Note:
Create the key under an account with the admin role in the organization you want to track. Only admins can create Admin API keys, and a key reads only the organization it was created in. A key from another organization connects successfully but shows usage you do not expect.
Before You Start
Make sure you have:
- A Claude Console organization at platform.claude.com with Claude API usage. This is the organization that holds your API keys and is billed for the Claude API.
- The admin role in that organization. Only admins can create Admin API keys.
- A Binadox account.
Binadox authenticates with an Admin API key, which is not the same as the API keys your applications use to call Claude. A regular API key, starting with sk-ant-api, is rejected. If your company uses Claude Enterprise on claude.ai, the keys created there belong to a different product and do not work with this integration either.
The integration covers the Claude API billed by Anthropic through the Claude Console. It does not cover:
- Claude models used through Amazon Bedrock, Google Vertex AI or Microsoft Foundry. Those are billed by the cloud provider, so connect the Bedrock or Vertex AI integration for them.
- Claude.ai Team and Enterprise seats. That is the chat product rather than the API.
- Priority Tier costs. Anthropic reports Priority Tier usage but excludes it from the cost report, so those tokens appear in usage without a cost.
Note:
Claude Console Admin keys have no scopes. The same key that lets Binadox read usage and cost can also manage members, workspaces and API keys. Binadox calls read endpoints only, listed in What Binadox Reads, and you can revoke the key in the Claude Console at any time.
Generate Anthropic Admin API Key
Log into the Claude Console with an account that has the admin role in your organization.
In the left menu, open Settings and select Admin keys. Click Create key.
Give the key a descriptive name, for example Binadox LLM Cost Tracker, and choose an expiration. Binadox syncs every day, so pick a long expiration or none. When the key expires, the integration stops syncing and reports an authentication error until you connect a new key.
Click Create and copy the key. It starts with sk-ant-admin01-. You will need it to complete the setup in Binadox.
IMPORTANT:
Anthropic shows the full key only once, right after it is created. After you close the dialog, the key is masked and cannot be copied again. Copy the value immediately and store it in a safe place. If you lose it, create a new key and connect Binadox with that one.
Anthropic’s own guide for this step is Create an Admin API key.
Complete Connection in Binadox
Log into your Binadox account.
In the navigation pane on the left, click LLM Cost Tracker. Click Add account.
Select Anthropic Claude from the list of available providers. To quickly locate it, type its name in the search bar.
Create a unique connection name for further differentiation, for example Anthropic.
Enter the Admin API key you copied from the Claude Console. Click Connect.
Binadox verifies the key by reading your organization’s name and ID from Anthropic. Upon successful authorization, the connection status will switch into Connected and the connection takes the name of your organization.
The first data collection loads the last 60 days of usage and cost, so it takes several minutes. After that, the integration syncs once a day and picks up from the last hour already stored. A few things to expect from the data:
- Usage arrives in hourly buckets, so the current day fills in gradually. Anthropic makes new usage available within about five minutes, so each sync reflects everything up to the moment it runs.
- Costs come from Anthropic in whole-day buckets, so a day’s cost is complete only after that day has ended.
- The Anthropic price list is refreshed monthly and used for model-switching and cross-platform savings advice next to your OpenAI, Bedrock, Vertex AI and Azure OpenAI usage.
What Binadox Reads
All calls go to the Anthropic Admin API and only read data. Binadox never creates, changes or deletes anything in your organization.
| Call | Used for |
|---|---|
GET /v1/organizations/me | Checking the key when you connect and naming the connection after your organization |
GET /v1/organizations/workspaces | Showing workspace names instead of IDs next to usage |
GET /v1/organizations/usage_report/messages | Hourly tokens by model, workspace, API key and service tier |
GET /v1/organizations/cost_report | Daily cost in USD |
Binadox also downloads Anthropic’s public pricing page once a month to keep the price list current; that page needs no key.
The Admin API allows 100 requests per minute per organization. A daily sync uses a handful of requests, so the integration does not compete with other tools reading the same organization.
Troubleshooting
| Issue | What you see | What to do |
|---|---|---|
| Wrong kind of key | Connecting fails with “Please check correctness of the connection parameters” | Make sure the key starts with sk-ant-admin01-. Regular API keys and Claude Enterprise keys are rejected. Create a new Admin key if you are not sure which one you pasted. |
| Key revoked or expired | The same message on connect, or a connection that worked before now shows an authentication error | Create a new Admin key in the Claude Console and reconnect the account with it. |
| Key belongs to another organization | Connection works but the usage shown is not what you expect | Sign in to the Claude Console as the organization you want to track and create the key there. A key only reads its own organization. |
| Anthropic unavailable | Connecting or a sync fails with a connection error rather than an authentication error | Anthropic’s API is unreachable or returned a temporary error. Binadox retries automatically; the key is not marked invalid. Try again later. |
| No usage after connecting | The connection is active but no data appears | Check that the organization had Claude API traffic in the last 60 days. Usage through Bedrock, Vertex AI or Foundry is not visible here. |
| Some usage has no cost | Tokens appear for a model but the cost stays empty | Priority Tier requests are excluded from Anthropic’s cost report. Their tokens are still counted. |
| Today’s cost is missing | Usage for today is visible but the cost is not | Anthropic reports cost per whole day. It appears after the day ends and the next sync runs. |
| A workspace shows as an ID | A name like wrkspc_01... instead of a workspace name | The workspace was archived or could not be listed at sync time. Names are refreshed on the next sync. |
Revoke or Rotate the Key
To stop Binadox reading your organization, delete the key in the Claude Console under Settings > Admin keys. The next sync fails with an authentication error and no further data is read. You can also disconnect the account in Binadox, which removes the stored key on our side.
To rotate the key, create a new Admin key first, then reconnect the Binadox account with the new key, and only then delete the old key in the Claude Console. Done in that order, no sync is missed.
Binadox stores the key encrypted and uses it only for the read calls listed above. Because a Claude Console Admin key also carries write permissions, treat it like any other administrative credential: create it under a named admin account, give it an expiration that matches your key-rotation policy, and revoke it when it is no longer needed.
Support and Resources
Binadox Support:
- Email: support@binadox.com
- Documentation: Binadox LLM Cost Tracker Documentation
Anthropic Resources: