Claude's New Usage and Cost Analytics API Is Worth Switching To Before Your Next Bill Review

On 29 October 2026 Anthropic launched the Usage and Cost Analytics API in beta. Two endpoints, usage and cost, report token usage and spend for Claude Console and Claude Enterprise organisations, and you can filter and group the results by model, workspace, API key, and the user or service account behind each request.

That last part is the useful bit. Most teams find AI costs by looking at one total on an invoice, which tells you nothing about which project or which experiment caused it. Grouping by workspace and API key means you can give each client job or internal tool its own key and see its real cost at the end of the month.

The older Usage and Cost API is now legacy, along with several reporting endpoints in the Claude Enterprise Analytics API. They remain supported, so nothing breaks tomorrow, but Anthropic has published migration guides and we would start the move while it is optional.

The practical suggestion is to set up keys by purpose now. One for production, one for experiments, one per client if you rebill. It takes ten minutes, and it turns cost reporting from a guess into a table. Note the beta header requirement in the documentation, and expect details to change before it settles.