Author: Nadali. Prepared using AI.
On October 29, Anthropic announced the Usage and Cost Analytics API beta for Claude Console and Enterprise organizations. The new reports break down usage and cost by models, workspaces and the identities behind requests. Previous reporting APIs remain supported.
Who benefits
Business owners whose technical teams maintain several Claude-based automations. The practical opportunity is to request separate accounting for workflows instead of judging all spending from one combined number.
An important delay
According to the documentation, data typically refreshes within 4 hours and can take up to 24. The data_refreshed_at field shows its freshness. This report should therefore not serve as an immediate overspending alarm.
What to ask the person responsible
Our editorial recommendation:
- Define the business question the report should answer: for example, how much drafting replies costs compared with processing documents. This is an illustration, not a measured case.
- Ask for the reporting period and refresh timestamp beside the totals. Do not compare an incomplete day with a completed one.
- Separately review existing limits and the procedure for stopping automation. Reporting must not replace those safeguards.
- Before migrating, compare old and new reports for the same period; investigate discrepancies before using the figures for decisions.
Access and limits
Console requires administrative credentials; Enterprise requires enabled Analytics API access and a key with the read:analytics scope. Assign setup to an authorized technical colleague and do not share secrets in an ordinary chat.
The takeaway: the new analytics can help examine spending, but the delay must be reflected in the workflow. Nadali read the primary sources on October 31 and did not test the API.
Related: compatibility checks when upgrading the Claude API. Cover: a reused AI illustration, not a Claude report.
