Anthropic launches a Usage and Cost Analytics API that attributes Claude spend to individual users

Anthropic launched a Usage and Cost Analytics API in beta on October 29. Per the release notes, its two endpoints "report token usage and cost for Claude Console and Claude Enterprise organizations," and results can be filtered and grouped "by dimensions such as model, workspace, API key, and the user or service account behind each request." The same release made the existing Usage and Cost API a legacy API, along with the usage and cost report endpoints of the Claude Enterprise Analytics API. All of them remain supported, and Anthropic has published migration guides.

What it reports

One endpoint returns token and request counts and the other returns cost in US dollars. The docs say cost rows include both the amount "after discounts and before any credits are applied" and the cost at list prices. Results can be grouped by up to five dimensions and split into daily, hourly or per-minute buckets. Anthropic lists finding top consumers, such as "which API keys spend the most this month?", as a use case.

The new piece is the actor dimension, which attributes a request to a user, a service account, a federated AWS or Google Cloud identity, or the API key itself when no identity is linked. Usage from keys that Claude Code creates for a member at sign-in is attributed to that member, and so is Claude Code usage after a sign-in without an API key. Legacy workspace keys are not linked to a person, so their usage shows only the key. Some dimensions apply only to one organization type, such as API key IDs for Console organizations and Slack channel IDs for Enterprise ones. Requests need the analytics-usage-cost-2026-08-24 beta header, and Enterprise organizations use a key with the read:analytics scope created by the primary owner.

Why it matters

Anthropic's own reporting can now break down Claude spend by the person or service account behind each request, across API keys, workspaces and Claude Code sign-ins. Two limits apply. The docs say data "typically refreshes within 4 hours" and can take up to 24, and values can be revised "until about 7 days after the end of the calendar month," so month-end reports run on the 1st will change. Spend on legacy workspace keys still cannot be traced to a person, which is a reason to move teams onto personal or service-account keys. Priority Tier requests show zero token cost because the commitment fee is billed separately.