Connect Anthropic

CostReveal reads what Anthropic bills from your organization's cost report, the same figures as the Cost page in the Claude Console, with an Admin API key. Nothing changes in the code that calls Claude.

What you need

• An Anthropic organization in the Claude Console. The Admin API is not available to individual accounts.
• An organization admin, who can create Admin API keys.
• An owner or admin role in CostReveal.

Connect

1. In the Claude Console, go to Settings, Admin keys and create a key. Name it for CostReveal, so it can be revoked on its own.
2. In CostReveal, go to Connections and choose Connect Anthropic.
3. Paste the key and choose Verify and connect. CostReveal reads your organization, its workspaces and its cost report with the key before saving anything, and says exactly what is wrong if it cannot.

Anthropic reports usage and cost within minutes, and CostReveal reads it every hour. The first read brings in the current month and the twelve before it, as far as Anthropic holds them. Where Anthropic holds no older months, Connections says how far back it reached, and each read asks again.

What an admin key can do

Anthropic admin keys cannot be limited to reading: a key could also manage your organization's members, workspaces and API keys. CostReveal only ever reads usage and cost with it. The key is encrypted at rest, is never shown again after you enter it, and is deleted when you remove the connection. Revoke it in the Claude Console at any time; CostReveal then keeps every figure already read and tells you new data has stopped.

How spend is explained

• Service and model come from Anthropic itself, so they are DIRECT. Token costs are billed per model; web search and code execution fees are not, so they have no model. Usage data that reports a call's web searches and code executions divides those fees too; see Sending usage data.
• Team, feature and customer come from your workspaces, in this order:
  1. an owner you name for the workspace under Connections, Workspace owners;
  2. the workspace's own tags in the Claude Console, read with the project's tag keys, the same ones used for AWS resource tags;
  3. otherwise the spend is UNKNOWN, shown as such and never spread across teams.
• Renaming or re-tagging a workspace, or naming its owner, explains every past period again. The billed figures themselves never change.

Coverage by model is measured against the spend billed per model, so cloud spend never dilutes it.

How figures are checked

• Every line is recorded as Anthropic reported it: a day, a workspace and one line item, by model, token type, service tier, context window and inference region. A day Anthropic restates is recorded as a correction, and what it said before is kept.
• Reading the same data again records nothing new.
• Each month's detailed lines must add up to the organization's total for the month, read separately. While a month is open a difference is shown as pending; once the month has closed it is flagged.

Priority Tier costs are billed differently and are not in Anthropic's cost report, so they are not included.