From the Anthropic edition of October 30, 2026
Claude Platform launches a beta Usage and Cost Analytics API that breaks down token spend by model, workspace, API key and user
Anthropic · Cross-sector (Claude API and Enterprise organizations) · Global
- Publisher
- Claude Platform documentation (release notes)
- Original publication
- October 29, 2026 (release-notes entry)
- Source retrieved
- 2026-10-31
- Event date
- 2026-10-29
What happened
On Oct. 29, 2026 Anthropic launched in beta a Usage and Cost Analytics API whose usage and cost endpoints report token usage and cost for Claude Console and Claude Enterprise organizations, filterable by model, workspace, API key and the user or service account behind each request. The prior Usage and Cost API and Enterprise usage/cost report endpoints are now legacy but supported. The same page records a fast-mode deprecation for Opus 4.8 (removal Nov. 30) and an Oct. 28 restriction on Managed Agents web_fetch to reduce exfiltration risk.
Why it matters
Gives SLTT and campus IT teams a programmatic way to attribute Claude spend to departments, projects or service accounts, which consumption billing under OneGov makes necessary. Applicability to Claude for Government tenants is not stated.
Evidence and measured results
Vendor release note; beta status. No usage data.
Limitations and uncertainty
Beta API; endpoints and header may change. Claude for Government coverage not stated. Release notes are vendor statements.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Shared Claude contracts make it hard to show which department or project drove token spend.
- Stakeholders
- Agency CIO
- Finance/budget office
- Department heads
- Discovery questions
- How do you allocate shared IT costs today?
- Are workspaces or API keys aligned to cost centers?
- Which Claude product are you on, and does it support this API?
- Value hypothesis
- Programmatic spend attribution may make chargeback feasible and reduce disputes over shared AI costs.
- Potential engagement
- A chargeback/showback design sprint using the analytics API in a test workspace.
- Unsupported claims
- That the beta API is production-stable
- That it is available for Claude for Government
- That visibility alone reduces spend
Pre-sales engineering
Role takeaway
- Fit
- Fits API and Enterprise organizations with multiple departments or projects.
- Architecture and integration
- Call usage and cost endpoints with the beta header; group by workspace, API key or service account; load into FinOps or BI tooling.
- Prerequisites
- Admin API key with appropriate scope
- Workspace/key naming aligned to cost centers
- Reporting destination
- Constraints
- Beta status
- Product coverage for Claude for Government not stated
- Legacy endpoints will need migration
- Security
- Store admin keys as privileged secrets; restrict who can query per-user cost data.
- Proof of value
- Reconcile API cost totals with a monthly invoice
- Verify grouping by service account matches agent workloads
Delivery
Role takeaway
- Work
- Build a monthly showback report and migration plan off legacy endpoints.
- Dependencies
- Cost-center tagging scheme
- Admin credentials
- Finance sign-off on allocation rules
- Ownership
- Central IT FinOps or platform team with finance.
- Skills and adoption
- Basic FinOps training for IT staff running the reports.
- Governance checkpoints
- Allocation rules approved by finance
- Privacy review of per-user cost data
- Acceptance criteria
- Proposed: monthly showback delivered to each department
- Proposed: API totals reconcile to invoice within agreed tolerance
- Risks
- Beta API changes
- Per-user data misuse
- Incomplete tagging leaves spend unattributed
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agencies can pull spend data into existing FinOps or chargeback tools, keyed by workspace, API key or service account, if they structure workspaces and keys by cost center. Integrations built on the now-legacy endpoints should plan migration.
Governance
Who approves, reviews and stays accountable for outcomes?
Per-user and per-service-account attribution supports chargeback and accountability but is also employee-level usage data subject to agency policy.
Security and privacy
What data, permissions and controls need testing?
Requires admin API credentials; these should be scoped and stored as privileged secrets. The Oct. 28 web_fetch restriction is a vendor-side exfiltration control relevant to agent deployments.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Implementing chargeback needs FinOps skills that many SLTT IT shops lack.
Procurement
What should contracts, pricing and exit terms secure?
Buyers can require programmatic cost reporting in statements of work and confirm availability for the specific product ordered.
Operating model
Which teams own the service once it runs?
Supports a showback/chargeback model in which departments see their own token spend.
Publication history
- 2026-10-30Anthropic · Issue 0210 resources
Stable resource ID: claude-platform-usage-cost-analytics-api-beta-20261029