AI news for business · checked October 30, 2026

The Usage and Cost Analytics API shows tokens and cost by model, workspace and user.

On October 29, 2026, Anthropic released the Usage and Cost Analytics API in beta. It reports an organization's historical token usage and cost, broken down by dimensions such as model, workspace, API key or the user or service account behind each request. The same endpoints serve Claude Console and Claude Enterprise organizations. The previous Usage and Cost API and the cost reports of the Enterprise Analytics API are now legacy but remain supported.

LOL.MARKETING / CONNECTING INTELLIGENCE

The essential answer

The Usage and Cost Analytics API has been available in beta since October 29, 2026, with the analytics-usage-cost-2026-08-24 beta header. The /v1/organizations/analytics/usage endpoint returns token and request counts, and /v1/organizations/analytics/cost returns cost in USD. Results can be grouped by up to five dimensions, filtered and split into minute, hour or day buckets. According to Anthropic, data typically refreshes within 4 hours and can take up to 24 hours.

01 / FIT

A good fit when

  • Businesses that use Claude via the API or in Claude Enterprise and want to attribute cost by team, project, model or person, find top consumers or build their own finance dashboards.

02 / LIMITS

Not the first choice when

  • Individual accounts: according to Anthropic, the Admin API is unavailable for individual accounts. Anyone who needs near-real-time data should note the new API's longer refresh time.

What is the Usage and Cost Analytics API?

According to the Claude Platform release notes, Anthropic launched the Usage and Cost Analytics API in beta on October 29, 2026. Its /v1/organizations/analytics/usage and /v1/organizations/analytics/cost endpoints report token usage and cost for Claude Console and Claude Enterprise organizations. According to the documentation, for Console organizations the data is similar to what the Usage and Cost pages of the Claude Console show.

Every request needs the anthropic-beta: analytics-usage-cost-2026-08-24 header and an anthropic-version header. The SDK and the ant CLI send both headers automatically and fetch the remaining pages.

What analyses are possible?

Anthropic names four uses: attribute spend, find top consumers, build time series and integrate once for both Console and Enterprise. Results can be grouped by up to five dimensions, such as model, workspace, API key, service tier or the identity behind the request. Most dimensions have filters, with up to 100 values per filter.

  • Time buckets: optional 1 minute, 1 hour or 1 day in UTC.
  • Date range: from January 1, 2026, within the last 365 days, at most 31 days per request and at most 24 hours with minute buckets.
  • Cost: amount after discounts and before credits, list_amount at list prices, given in cents with six decimal places.

Who needs which key?

According to the documentation, Claude Console organizations use an Admin API key or another Admin API credential, such as an OAuth token with the org:admin scope. Claude Enterprise organizations use a key with the read:analytics scope, created in claude.ai by the primary owner after the Analytics API is enabled for the organization. The Admin API is unavailable for individual accounts.

Anthropic recommends giving the service that collects the data its own key, storing it in a secrets manager and rotating it regularly, or preferably using Workload Identity Federation with short-lived tokens. According to the documentation, both endpoints are also available on Claude Platform on AWS and on Claude Models on Google Cloud (Anthropic managed), using the respective cloud permissions there.

How fresh is the data?

Every response includes a data_refreshed_at timestamp. According to Anthropic, data typically refreshes within 4 hours of usage and can take up to 24 hours. Values can still be revised by late events and reconciliation until about 7 days after the end of the calendar month. For final totals, Anthropic recommends querying only months that ended at least 7 days ago.

According to the migration table, data in the old Usage and Cost API typically appears within 5 minutes. Our assessment, not a vendor statement: the new API is therefore less suited to real-time budget alerts, but well suited to monthly reports and cost attribution.

What happens to the previous interfaces?

Since October 29, 2026, the Usage and Cost API is a legacy API, as are the usage_report, cost_report, user_usage_report and user_cost_report endpoints of the Claude Enterprise Analytics API. According to Anthropic, all of them remain supported; two migration guides cover the switch. The other Enterprise Analytics API endpoints are not legacy.

For Enterprise organizations, Anthropic names benefits such as every group in every time bucket rather than only the top 100, and grouping by actor together with other dimensions. In addition, on October 28, 2026, Anthropic raised the maximum request size for the Messages API and the Token Counting API on the first-party Claude API from 32 MB to 128 MB.

What should businesses do now?

Check whether you currently pull cost reports via the old Usage and Cost API or the Enterprise reports. Test the new API in parallel with its own rotated key and compare the totals for a completed month. Decide which dimensions you use to attribute cost, such as workspace per project or actor per team, and build a simple monthly report on top.

The free AI System Check helps organize AI costs, responsibilities and key management across your team. These notes are suggestions, not customer results.

Keep it verifiable

Primary sources

The next sensible step

Do you know which team drives which AI costs?

Eight steps from a general interest in AI to a clearer decision for your business.

Start AI System Check
FreeProvider-neutralNo credentials