New usage and cost analytics API in beta; the older usage and cost reports are now legacy

Anthropic added usage and cost analytics endpoints for Console and Enterprise organizations. The older reports still work but are marked legacy.

what changed

On 29 October 2026 the Claude Platform release notes announced a Usage and Cost Analytics API, in beta. It has two endpoints: /v1/organizations/analytics/usage for token usage and /v1/organizations/analytics/cost for cost. It is for Claude Console and Claude Enterprise organizations.

Calls need the beta header analytics-usage-cost-2026-08-24. Results can be filtered and grouped by dimensions such as model, workspace, API key, and the user or service account behind a request.

The same entry marks the existing Usage and Cost API as legacy. Four Claude Enterprise Analytics API reports are also legacy: usage_report, cost_report, user_usage_report and user_cost_report. All of them remain supported. The notes give no sunset date and link to migration guides.

why it matters

Teams that track Claude spend usually build on the older reports. Those reports now have a named successor, so any new dashboard or chargeback job should start on the new endpoints.

Grouping by workspace, key and user or service account is what makes cost split by team or product possible. That is the data a model-choice or budget review needs.

The new API is a beta. Fields and behaviour may change, and the release notes do not give schemas or limits.

what we would do

  • List every job, dashboard and finance export that reads the legacy reports, so you know what a migration touches.
  • Build new cost reporting on the new endpoints, and keep the old ones running until the new numbers match.
  • Pin the beta header in one place in your code, so a change is a one-line edit.
  • Use the workspace and key grouping to find which product or team drives most of your spend, before the next planning round.

sources

Drafted with Claude from the linked sources, reviewed by us.