Claude Usage and Cost Analytics API
A usage and cost attribution analytics interface provided by Anthropic for the Claude API. It reports token usage and attributed costs across four dimensions: model, workspace, API key, and user. It is intended for team-level cost governance and budget allocation.
Timeline (last 90 days)
Anthropic launched the Claude Usage and Cost Analytics API (beta), which reports token usage and cost across four dimensions: model, workspace, API key and user.
This API is currently in beta, and its interface shape, fields and statistical definitions may all change, so it is not suitable as the sole data source for a financial system.
Usage data is usually not returned in real time item by item but aggregated over time windows, so this API is not suitable for second-level monitoring and is better suited to daily reports, weekly reports and periodic cost reviews.
Beta versions may be subject to rate limits or data retention period constraints.
When migrating to this API, you need to check whether the old and new definitions match, especially the boundaries of token counting (for example, whether cache hits are included and whether input and output tokens are distinguished), and whether cost calculation uses the same unit prices as billing.
It is recommended to run both in parallel for a period, reconcile the new API's aggregated results against the official bill, and switch over only after confirming the source of any differences.
Connecting usage data to an internal cost dashboard, building daily spend curves per API key and setting threshold alerts can surface abnormal calls in some integration at the first opportunity.
All Facts (7)
Beta versions may be subject to rate limits or data retention period constraints.
50%UnverifiedThis API is currently in beta, and its interface shape, fields and statistical definitions may all change, so it is not suitable as the sole data source for a financial system.
50%UnverifiedUsage data is usually not returned in real time item by item but aggregated over time windows, so this API is not suitable for second-level monitoring and is better suited to daily reports, weekly reports and periodic cost reviews.
50%UnverifiedConnecting usage data to an internal cost dashboard, building daily spend curves per API key and setting threshold alerts can surface abnormal calls in some integration at the first opportunity.
50%UnverifiedWhen migrating to this API, you need to check whether the old and new definitions match, especially the boundaries of token counting (for example, whether cache hits are included and whether input and output tokens are distinguished), and whether cost calculation uses the same unit prices as billing.
50%UnverifiedIt is recommended to run both in parallel for a period, reconcile the new API's aggregated results against the official bill, and switch over only after confirming the source of any differences.
50%UnverifiedAnthropic launched the Claude Usage and Cost Analytics API (beta), which reports token usage and cost across four dimensions: model, workspace, API key and user.
50%