{"resourceId":"claude-platform-usage-cost-analytics-api-beta-20261029","versions":[{"version":"external-f5896e1d3982cab61178bfcd693339ba13644adb192bffa5086b4255a77e8247","resource":{"id":"claude-platform-usage-cost-analytics-api-beta-20261029","title":"Claude Platform launches a beta Usage and Cost Analytics API that breaks down token spend by model, workspace, API key and user","organization":"Anthropic","sector":"Cross-sector (Claude API and Enterprise organizations)","geography":"Global","publishedAt":"October 29, 2026 (release-notes entry)","publicationDate":"2026-10-29","eventDate":"2026-10-29","sourceName":"Claude Platform documentation (release notes)","sourceLabel":"Vendor documentation","sourceUrl":"https://platform.claude.com/docs/en/release-notes/overview","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","governance-procurement","infrastructure"],"finding":"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.","sledRelevance":"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":"Vendor release note; beta status. No usage data.","architectureImplications":"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.","governanceImplications":"Per-user and per-service-account attribution supports chargeback and accountability but is also employee-level usage data subject to agency policy.","securityPrivacyImplications":"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.","caveats":"Beta API; endpoints and header may change. Claude for Government coverage not stated. Release notes are vendor statements.","streamIds":["anthropic"],"roles":{"sales":"Use this to answer the budget officer's question of who is spending what. The new API breaks token cost down by model, workspace, API key and user, which supports chargeback for departments sharing one contract. It is a beta vendor feature, so present it as a tool to evaluate, not a finished reporting system. Confirm whether the customer's product, especially Claude for Government, supports it before including it in a proposal.","engineering":"Engineers should design workspaces, API keys and service accounts around cost centers so the API's grouping dimensions map to budget lines. Pull data into the agency's existing FinOps or reporting stack and alert on anomalies. Because the endpoint is beta and the older endpoints are now legacy, isolate the integration behind an adapter. Also note the Oct. 28 Managed Agents web_fetch restriction and the Opus 4.8 fast-mode removal on Nov. 30 if agencies depend on either.","delivery":"Delivery should turn the API into a monthly showback report owned by finance and IT together. Agree on cost-center tagging before keys are issued, test the API against invoices, and plan migration for any reports built on legacy endpoints. Track the Nov. 30 fast-mode removal if any workload uses it. Interpretation: this improves visibility; it does not by itself prevent overruns."},"roleDetails":{"sales":{"customerProblem":"Shared Claude contracts make it hard to show which department or project drove token spend.","stakeholders":["Agency CIO","Finance/budget office","Department heads"],"discoveryQuestions":["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?"],"valueHypothesis":"Programmatic spend attribution may make chargeback feasible and reduce disputes over shared AI costs.","potentialEngagement":"A chargeback/showback design sprint using the analytics API in a test workspace.","unsupportedClaims":["That the beta API is production-stable","That it is available for Claude for Government","That visibility alone reduces spend"]},"engineering":{"fit":"Fits API and Enterprise organizations with multiple departments or projects.","architectureIntegration":"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.","proofOfValue":["Reconcile API cost totals with a monthly invoice","Verify grouping by service account matches agent workloads"]},"delivery":{"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.","skillsAdoption":"Basic FinOps training for IT staff running the reports.","governanceCheckpoints":["Allocation rules approved by finance","Privacy review of per-user cost data"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-31T03:11:45Z","enrichedAt":"2026-10-31T03:24:49Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Implementing chargeback needs FinOps skills that many SLTT IT shops lack.","procurementImplications":"Buyers can require programmatic cost reporting in statements of work and confirm availability for the specific product ordered.","operatingModelImplications":"Supports a showback/chargeback model in which departments see their own token spend.","sourceVerification":{"openedUrl":"https://platform.claude.com/docs/en/release-notes/overview","referenceExcerpt":"report token usage and cost for Claude Console and Claude Enterprise organizations.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}