Anthropic Billing Setup

Anthropic reports cost through two APIs. They use different keys and are not interchangeable. Pick the connector that matches where you pay, then paste the matching key. If you call Claude through Amazon Bedrock instead of Anthropic’s own APIs, that spend lands via the AWS connector. For team-level allocation after data is in, see LLM cost allocation.

Which connector to use

Your organization	Connector in Costory	Key
Claude Console (Claude Platform)	Anthropic Claude Code	Admin API key (`sk-ant-admin01-…`)
Claude Enterprise (claude.ai)	Anthropic Claude AI	Analytics API key (`sk-ant-api01-…`, scope `read:analytics`)

Claude Enterprise parent organizations do not appear in Claude Console and have no Admin API keys. A Console Admin key will not work on Anthropic Claude AI. An Analytics API key will not work on Anthropic Claude Code.

Connect both if you pay for Console API usage and a claude.ai Enterprise org. Each connector is a separate billing datasource.

Connect Anthropic Claude Code

Use this connector for Claude Console (Claude Platform) API usage and subscription usage exposed by the Usage and Cost Admin API.

Manual setup
Terraform

Create an Admin API key

In Claude Console > Settings > Admin keys, create an Admin API key with usage and cost access. You must be an organization admin. Copy it immediately (sk-ant-admin01-…). A standard Claude API key will not work.

Connect in Costory

Go to Integrations, click + Add integration, then choose Anthropic Claude Code under Billing.

Enter connection details

Fill Connection name (default Anthropic) and Admin API key. Start date is optional. Leave it empty to use Costory’s default lookback.

Validate, then save

Click Validate. Save stays disabled until the Admin API key can read organization usage and cost. If this is the only billing source and it is demo data, Costory asks you to confirm before replacing it.

On first sync, Costory backfills up to 12 months of historical usage data. New data then follows the usual data refresh cadence. SaaS sources typically appear in about 10 minutes.

terraform {
  required_providers {
    costory = {
      source  = "costory-io/costory"
      version = ">= 0.1.0"
    }
  }
}

variable "costory_api_token" {
  type        = string
  description = "Costory API token."
  sensitive   = true
}

variable "anthropic_admin_api_key" {
  type        = string
  description = "Anthropic admin API key used to fetch billing data."
  sensitive   = true
}

provider "costory" {
  token = var.costory_api_token
}

resource "costory_billing_datasource_anthropic" "main" {
  name          = "Anthropic Billing"
  admin_api_key = var.anthropic_admin_api_key
}

What Costory includes

API usage and subscription usage from Anthropic billing exports.
Included plan usage labeled as Included<subscription_type> in Charge description (for Business/Enterprise plans).
Per-model breakdown (group by Service name = model).
Per-actor attribution using user email or API key name.

What Costory does not include

Taxes, credits, and adjustments outside usage line items.
Non-usage fees that do not appear in the Anthropic billing export.
claude.ai Enterprise seat or usage-credit costs. Use Anthropic Claude AI for those.

How to analyze Anthropic Claude Code costs

Included vs API usage: filter by Charge description:
- Included<subscription_type> for subscription usage.
- API for pay-as-you-go usage.
Per-user email spend: group by Resource name or Sub account id (mapped to the actor email or API key name).
Per-model costs: group by Service name (model) and break down by SKU (input vs output tokens).

Anthropic Console costs are attributed to input tokens. Output token rows are included for usage analysis but have $0 cost.

Connect Anthropic Claude AI

Use this connector for Claude Enterprise costs on claude.ai. Costory reads per-user cost from the Get Per-User Cost endpoint. See Anthropic’s Analytics API for how to enable access.

You must sign in as the organization primary owner. Only the primary owner can enable public API access and create the Analytics API key.

Enable public API access

Sign in to claude.ai as the primary owner. Open claude.ai > Organization settings > API and enable public API access.

Create an Analytics API key

Create an Analytics API key with scope read:analytics. Copy it immediately (sk-ant-api01-…). A Console Admin key (sk-ant-admin01-…) will not work.

Connect in Costory

Go to Integrations, click + Add integration, then choose Anthropic Claude AI under Billing.

Enter connection details

Fill Connection name (default Anthropic Claude AI), Account name, and Analytics API key. Start date is optional. Leave it empty to use Costory’s default lookback.

Validate, then save

Click Validate. Save stays disabled until the Analytics API key can read Claude Enterprise per-user cost. If this is the only billing source and it is demo data, Costory asks you to confirm before replacing it.

On first sync, Costory backfills up to 12 months of historical usage data, depending on what Anthropic retains. New data then follows the usual data refresh cadence.

Field reference

Field	Required	Description
Connection name	Yes	Label in Integrations.
Account name	Yes	Label for this Claude Enterprise org. Stored as Sub account id. Not sent to Anthropic.
Analytics API key	Yes	Primary-owner key with `read:analytics`. Stored in Costory’s secret manager.
Start date	No	Optional start of the first sync. Leave empty for the default lookback.

What Costory includes

Per-user cost from the Claude Enterprise Analytics API.
Your Account name as Sub account id, so you can tell multiple Enterprise orgs apart.

What Costory does not include

Claude Console / API usage. Use Anthropic Claude Code for that.
Unattributed org-wide API-key or automation traffic (the org-wide cost report is out of scope).
Seat SKU on seat-based Enterprise plans. Those plans only show usage credits.

Seat-based Enterprise plans only show usage credits, not the seat SKU. Cost and usage endpoints apply to usage-based Enterprise plans. For seat-based plans they reflect usage credits only.

Rotate the Analytics API key from Integrations when you need a new credential. Account name stays the same.

Troubleshooting

Issue	What to check
Admin key rejected on Claude AI	You pasted a Console Admin key (`sk-ant-admin01-…`). Use Anthropic Claude Code for that key, or create an Analytics key (`sk-ant-api01-…`) as primary owner.
Analytics key rejected on Claude Code	You pasted an Analytics API key. Use Anthropic Claude AI for claude.ai Enterprise costs.
Access denied (403)	Confirm you are the primary owner, public API access is enabled, and the key has `read:analytics`.
No cost data on a seat-based plan	Expected. Seat-based plans expose usage credits only, not the seat SKU.
Failed to authenticate	Recreate the key in the matching console: Admin keys in Claude Console, Analytics keys in claude.ai Organization settings > API.

Get Started

Setup

Understand

Tag & Allocate

Share

Teams

Technical Documentation

Glossary

Which connector to use

Connect Anthropic Claude Code

What Costory includes

Connect Anthropic Claude AI

Field reference

What Costory includes

Troubleshooting

​Which connector to use

​Connect Anthropic Claude Code

​What Costory includes

​Connect Anthropic Claude AI

​Field reference

​What Costory includes

​Troubleshooting

​Related

Which connector to use

Connect Anthropic Claude Code

What Costory includes

Connect Anthropic Claude AI

Field reference

What Costory includes

Troubleshooting

Related