Claude adds an API for cost and usage analytics, not just a dashboard
The new beta endpoints report token usage and spend broken down by model, workspace, API key or user, so you can pull the numbers into your own tools instead of reading them off a console page.
Anthropic shipped a Usage and Cost Analytics API in beta on 29 October, for both Claude Console and Claude Enterprise organisations. It adds two endpoints: GET /v1/organizations/analytics/usage for token and request counts, and GET /v1/organizations/analytics/cost for spend in US dollars.
Results can be grouped by model, workspace, API key, service tier or the user or service account behind each request, and split into daily, hourly or per-minute buckets. Cost data is usually ready within four hours of the underlying usage, sometimes up to 24, and can still be revised for about seven days after the calendar month ends. Calling it requires an anthropic-beta header:
GET /v1/organizations/analytics/cost
anthropic-beta: analytics-usage-cost-2026-08-24Why it matters: anyone running Claude in production has had to screen-scrape the Console’s Usage and Cost pages, or wait for an invoice, to work out who or what is driving spend. A proper API means that data can feed straight into your own billing dashboards, alerts or chargeback reports, attributed down to the API key that made each call.
The caveat: this replaces the older Enterprise usage_report and cost_report endpoints, which Anthropic now calls legacy. They still work, but new integrations should use the new endpoints instead.