Claude cost analytics API: charge back and accrue AI spend at month-end

What’s new

On 29 October 2026, Anthropic launched the Usage and Cost Analytics API in beta, using the header analytics-usage-cost-2026-08-24. It reports token usage and cost for Claude Console and Claude Enterprise organizations. You can filter and group by dimensions such as model, workspace, API key, and the user or service account behind each request.

The older Usage and Cost API is now legacy, as are the usage and cost reports in the Claude Enterprise Analytics API. All remain supported. The documentation we checked shows no end date. The Admin API is not available for individual accounts.

Why it matters for finance

As AI spend grows, finance has to answer three questions. Who used it? Which budget pays? What do we accrue at close? This API gives a direct feed for all three, down to the workspace and the service account. It can replace a manual download from a console.

How to use it

1. Get access from the right owner. Console organizations use an Admin API key. Enterprise organizations use a key with the read:analytics scope, created by the primary owner once the Analytics API is enabled.
2. Ask a developer to send the beta header and an anthropic-version header on every request.
3. Call GET /v1/organizations/analytics/cost for the month, grouped by workspace_id and model, in daily buckets. One request covers up to 31 days.
4. Convert the amounts. They are decimal strings in cents, always in USD, so “41280.000000” means 412.80 USD.
5. Map each workspace to a cost centre, such as Company One’s FP&A and tax teams, and prepare the chargeback.
6. Book the month-end accrual from the latest data, then true it up once the month is final.

Controls and limits

• Revisions: values can change until about 7 days after the end of the calendar month. For final totals, query only months that ended at least 7 days ago.
• Freshness: data typically refreshes within 4 hours and can take up to 24 hours. Record the data_refreshed_at value with your workpaper.
• Credits: the amount field is after discounts but before credits, so reconcile it to the invoice rather than assuming a match.
• Priority Tier: the commitment fee is billed separately and is not in this data. Add it to your accrual if it applies.
• Access: an admin-level key is sensitive. Restrict it, store it securely and name an owner.
• Privacy: grouping by user creates person-level data. Check your internal rules before sharing it.
• Beta status: details may change, so keep your invoice reconciliation in place.

Our take

This is a small release with a practical use for finance. The value is not a new dashboard. It is a repeatable data feed that supports chargeback and accrual. Start with one month in parallel with your current process. Compare the result with the invoice before you rely on it. Only then retire the manual download.

Try this prompt

You are helping a finance team prepare a month-end Claude cost accrual and chargeback. Do not invent any figure.

Company: [Company One]
Month: [month and year]
Attached: [cost export grouped by workspace_id and model, with its data_refreshed_at value]
Cost centre map: [workspace to cost centre table]
Last invoice: [amount and period]
Credits and any Priority Tier commitment fee: [details, or none]

Steps:
1. Convert the amounts, which are decimal strings in cents, to USD.
2. Build a chargeback table by cost centre and model.
3. Propose the accrual, listing credits and commitment fees as separate lines.
4. Reconcile last month’s data to the invoice and show any difference without forcing a match.
5. State whether this month’s data may still be revised, based on today’s date of [date].
6. List open questions for the reviewer.

Return the tables and a short note that a person can review and sign off.

Important. This lesson is general information, not professional or accounting advice; Claude features and plan availability change, so check Anthropic’s current documentation and review every AI output before relying on it.