We’ve launched the Usage and Cost Analytics API in beta with the analytics-usage-cost-2026-08-24 beta header
By Steven Van ·
Token usage and cost reporting for Console and Enterprise organizations moves to new endpoints, while the older usage and cost APIs stay supported as legacy.
The Usage and Cost Analytics API is now in beta for Anthropic, and it covers both Claude Console and Claude Enterprise organizations. The release is called with the analytics-usage-cost-2026-08-24 beta header.
What the endpoints report
Two endpoints, /v1/organizations/analytics/usage and /v1/organizations/analytics/cost, report token usage and cost. Results can be filtered and grouped by dimensions such as model, workspace, API key, and the user or service account behind each request.
Cost data and keys
- Claude Enterprise organizations call the Usage and Cost Analytics API with their Analytics API key, an exception to the rule that Admin API keys and Analytics API keys are not interchangeable.
- Cost and usage data is typically available within 4 hours of the underlying usage but can take up to 24 hours. Values can be revised until about 7 days after the end of the calendar month.
- Amounts are returned as decimal strings in cents, so "41280.000000" represents $412.80.
- Rate limits apply per organization, with a default of 60 requests per minute across all endpoints in the Claude Enterprise Analytics API.
Legacy status of older APIs
The Usage and Cost API is now a legacy API. So are the usage_report, cost_report, user_usage_report, and user_cost_report endpoints of the Claude Enterprise Analytics API. All of them remain supported, and the Claude Enterprise endpoints for engagement and adoption data are not legacy. New integrations are directed to the Usage and Cost Analytics API. Anthropic has published migration guides for moving from the Usage and Cost API and from the Claude Enterprise usage and cost reports.