Claude API spend by initiative: using Anthropic's Usage and Cost Admin API

Luke Wilcox — Fri, 06 Nov 2026 16:54:22 +0000

Roiva wrote this, and Roiva reads the API it describes. The facts about Anthropic's reports were gathered from Anthropic's published docs on October 24, 2026, and the beta cost report on October 30, 2026, and each links to the page it came from. Anthropic changes these APIs often, so check the link before you build on a detail.

How do you report Claude API spend per AI initiative?

Give each initiative its own workspace in the Claude Console, then read Anthropic's cost report grouped by workspace. Anthropic's bill has no idea which initiative a request served; a workspace is the one dimension its cost report can split by that you control. Anthropic documents workspaces as the way to "separate different projects, environments, or teams while maintaining centralized billing and administration" (workspaces).

A workspace is a container inside a Claude Console organization with its own API keys and spend limits. Its costs show up under its own ID in the cost report.

Which Anthropic report gives you what?

Anthropic reports Claude spend in six places, and which one you need depends on how your company pays for Claude.

Report	What it gives	Grain	Key or access
Console Usage page	Tokens by model, workspace, API key, month or day, with CSV export	Daily	Console sign-in
Console Cost page	Dollars by workspace, model and month, with CSV export	Monthly view	Console sign-in
Usage API, `/v1/organizations/usage_report/messages`	Tokens by model, workspace, API key, service tier and more	1 minute, 1 hour or 1 day	Admin API key
Cost API, `/v1/organizations/cost_report`	Dollars by workspace and by line description (model, cost type, token type)	1 day only	Admin API key
Usage and Cost Analytics API (beta), `/v1/organizations/analytics/cost`	Dollars by API key, workspace, model and more	1 day, or the whole range	Admin API key
Claude Code Analytics API, `/v1/organizations/usage_report/claude_code`	One record per user per day: sessions, lines, commits, accepted edits, estimated cost	1 day	Admin API key

Sources: Usage and Cost API,Console reporting, Usage and Cost Analytics API, Claude Code Analytics API.

Claude Enterprise organizations on claude.ai are separate. They don't appear in the Claude Console, carry no Admin API keys, and report through the Claude Enterprise Analytics API with an Analytics API key instead (which API do you need?).

What does the Usage and Cost Admin API need?

An Admin API key, which starts sk-ant-admin01- and which only organization members with the admin role can create. Anthropic also accepts an OAuth token with the org:admin scope, or a personal or service account key that isn't scoped to a workspace; "workspace API keys don't work" (Usage and Cost API). The Admin API isn't available to individual accounts, so set up an organization first.

What else to know before you build on it, as Anthropic documents it:

Money is in cents. "All costs are in USD, reported as decimal strings in lowest units (cents)."
The cost report is daily only, up to 31 days a request, grouped by workspace_id and description. Grouping by description adds the model, the cost type (tokens, web search, code execution) and the token type.
The default workspace has no ID. Its usage and costs carry a null workspace_id, so a script that drops nulls drops the default workspace.
Data is near real time. It "typically appears within 5 minutes," and Anthropic supports polling once a minute.
Pagination uses has_more and next_page.

Can you see Claude API spend by user?

Not for requests made with API keys. Anthropic's support article says "currently, it's not possible to break down usage or cost by individual users" in the Console (Console reporting).

The Usage API can group by the account behind a request only where the request was signed in as a person rather than made with an API key, and the cost report has no user dimension at all.

For Claude Code, the Claude Code Analytics API gives per-user, per-day activity with an estimated cost. For an application your team built, log the user, the task and the engagement or customer in the application itself, and use workspaces or API keys to split the bill.

What isn't in Anthropic's cost report?

Several kinds of Claude spend never reach it, and a total built only from it will be short by exactly those:

Spend	Where it shows instead
Priority Tier	Not in the cost endpoint: "Priority Tier costs use a different billing model." Anthropic says to track Priority Tier usage through the usage endpoint (Usage and Cost API)
Claude on Amazon Bedrock	Your AWS bill; Anthropic lists its Admin and Usage and Cost endpoints among the features Bedrock doesn't support (Claude on Amazon Bedrock)
Claude on Google Cloud	Your Google Cloud bill. For the Anthropic-managed offering, only the usage endpoint works and cost shows on the Console Cost page (Google Cloud)
Claude Team and Enterprise seats	Your invoice from Anthropic, and the claude.ai analytics for Team and Enterprise
Claude Platform on AWS	The Console Usage and Cost pages; the API endpoints aren't available there

How do you split one Claude bill across initiatives?

Claim what you can by workspace, and split only what's left. A method a finance team can audit:

One workspace per initiative, created before the initiative goes live, with its own API keys. Spend that lands in the right workspace needs no allocation at all.
Decide the default workspace's fate. Either keep it empty or treat it as shared. Anthropic doesn't let you set a spend limit on it.
Split out a shared workspace's keys. Anthropic's beta cost report gives dollars by API key, so a key that serves one initiative can be claimed alone.
Split the rest by a stated weight, such as requests or seats by team, and write the weight down before the month closes.
Book the API cost once. The Anthropic invoice in your ERP is the same money as the cost report. Use one as the source for each month, not both.
Add what the report misses. Priority Tier, Bedrock and Google Cloud spend come from their own bills.
Watch unit cost, not just spend. Cost per million output tokens, by model and month, says whether a cheaper model or better caching made each answer cheaper, separately from how much the initiative was used.

How does Roiva book Claude API spend to initiatives?

Roiva does the routine above every night, from the same reports.

It reads the cost and usage reports. Connect Anthropic with an Admin API key and Roiva reads the cost report by workspace and line description, and the usage report by model and workspace, for the last 12 months, then every night after. It never reads a prompt or a response.
Workspaces become initiatives. When you link the connection to an initiative, Roiva asks how much of the bill is the initiative's: all of it, only some workspaces, each booked whole, or a share of every charge. What no initiative takes stays unattributed rather than being spread silently. A changed share applies from the first of that month.
An API key can stand alone. An initiative can claim one key and book what Anthropic's beta report says that key cost. The rest of its workspace books as if the key weren't claimed, and a day whose key figures don't add up to the workspace's bill stays with the workspace.
The invoice isn't counted twice. In any month the connection books, an Anthropic invoice mapped to the same initiative in QuickBooks, Xero or NetSuite is left out, unless an allocation rule or a locked month keeps the invoice instead.
Unit cost, with the cause. Roiva tracks cost per million output tokens by model and month. Where an initiative books a saving on that unit cost, Roiva splits the saving into what Anthropic's price changes gave and what your own choices earned: the models you ran, what you cached and how you shaped the work.
Claude Code and Claude Enterprise. The same key reads Claude Code's daily totals, with user names dropped before anything is saved. Claude Enterprise seats need their own connection with an Analytics API key, which also books usage cost by user group or estimated chat Project. Claude on Bedrock is booked from the AWS connection, by tag or by service, and on Google Cloud from the Google Cloud connection.

Roiva books from Anthropic's cost report, so Priority Tier spend, which isn't in that report, has to reach the initiative as a cost you enter. The Anthropic integration page shows a worked month, and How costs reach an initiative covers every way spend becomes an initiative's cost and where the same dollar can arrive twice.

DEV Community: Luke Wilcox