Click path: Console → left nav → Cost (for real dollars) or Usage (for token counts) → set the date range and workspace/model filters → the export button, which downloads a CSV of the displayed data. The two pages are separate reports, not one screen with two buttons — each mirrors one of the Admin API's two report endpoints, cost_report and usage_report/messages, one bucket-per-row for whatever range you select. (Source: Anthropic Help Center, "Cost and Usage Reporting in the Claude Console," updated 2026-03-16, fetched 2026-08-30; and platform.claude.com/docs/en/manage-claude/usage-cost-api, fetched the same day.)

What's verified here, and what isn't

Unlike our Cursor and Claude Team guides — each written from a real, verified export file — we have not yet gotten our hands on a real Anthropic Console export. The column names below are the shape our parser is built to accept, based on Anthropic's own documented Admin API report endpoints, not a file we've opened ourselves. If your real export's columns differ, they won't silently misread: this tool names any column it doesn't recognize in its data-quality footer instead of guessing. Tell us what you see and we'll fix this page.

One more thing neither export can give you: Anthropic's own help article states plainly, "Currently, it's not possible to break down usage or cost by individual users." Either export rolls up to workspace and API key, not a person — that's why this tool's report shows Console uploads as a single "Unattributed Anthropic API usage" line, not a per-person breakdown.

Cost export — the one with real dollars

Cost export columnsreal Amount (USD)
Date,Workspace,Description,Cost Type,Token Type,Model,Amount (USD)

Cost Type and Token Type split each day's charge into its component pieces per model — this is Anthropic's own vendor-stated figure, the one to treat as spend.

Usage export — tokens only, no dollars

Usage export columnsno dollar column
Start Time,API Key,Workspace,Model,Service Tier,Input Tokens,Output Tokens,Cache Read Tokens,Cache Write 5m Tokens,Cache Write 1h Tokens

Notice what's missing: no Amount column anywhere. This export exists for capacity/rate-limit visibility, not billing — it tells you how many tokens moved, at what cache state, per API key and workspace, not what you were charged for them.

Why pricing this export yourself overstates (or understates) spend

The Usage export's own column layout is the tell: it splits cache tokens into Cache Read Tokens, Cache Write 5m Tokens, and Cache Write 1h Tokens as three separate buckets from ordinary Input Tokens, instead of lumping them all into one input-token total. If a cache read, a cache write, and a plain input token all priced the same, the export wouldn't need three separate columns for them — it does, which means treating every token in this file as one flat rate and multiplying by a single published price is a guess, not a bill. It also has no way to reflect a negotiated enterprise rate, since it carries no dollar figure at all to begin with.

The Cost export doesn't have this problem — its Amount (USD) column is what Anthropic actually charged, already accounting for whatever rate applies to your account. When both exports are available for the same period, the Cost export is the one to reconcile against an invoice; the Usage export is for understanding request/token volume, not spend.