On October 29, Anthropic released the Usage and Cost Analytics API in beta. Two endpoints, one beta header, and for the first time a single interface serving both Claude Console and Claude Enterprise.
GET /v1/organizations/analytics/usage reports token and request counts; GET /v1/organizations/analytics/cost reports cost in USD. Both can be filtered and grouped by dimension: model, workspace, API key, service tier, and the identity behind each request — user or service account.
What you can finally answer
The documentation lists four uses, and three of them used to be painful: attributing spend to a workspace or key, ranking top consumers by tokens, requests or cost (“which API keys spend the most this month?”), and building time series in daily, hourly or per-minute buckets. The fourth is the quietest and probably the most consequential: one integration for both organization types, with the same parameters and the same response fields.
The beta header is anthropic-beta: analytics-usage-cost-2026-08-24, alongside an anthropic-version header. The SDK and the ant CLI send both for you and fetch the remaining pages as you read, so limit only sets the page size there.
Two routes to authorization
Claude Console organizations use an Admin API key or an OAuth token with org:admin, which belongs in an authorization: Bearer header rather than x-api-key. Claude Enterprise works with a key scoped read:analytics, created in claude.ai by the primary owner once the Analytics API has been enabled for the organization.
The docs suggest giving the service that collects these numbers its own key with an expiration set — or better, a Workload Identity Federation rule with org:admin, so the service gets short-lived tokens and no long-lived key sits around waiting to leak.
Legacy does not mean gone here
On the same day, Anthropic marked the previous Usage and Cost API as legacy, along with the usage_report, cost_report, user_usage_report and user_cost_report endpoints of the Claude Enterprise Analytics API. All of them remain supported, with no sunset date attached. The documentation carries two dedicated migration sections.
Anyone who has to split a bill now has the numbers
The run of the last few days points one way: managing cost and ROI for Claude Code on Google Cloud, pooled group budgets for Claude Enterprise, and now an API that breaks spend down to the individual service account. Anthropic is not building new ceilings. It is building the accounting behind them. That is the unglamorous work a finance department weighs before it gives a tool an annual budget.