// guide

How to Track Anthropic (Claude) API Costs

Anthropic spend usually arrives from two directions at once: metered API usage (Claude Opus, Sonnet, and Haiku billed per token) and subscription charges (Claude.ai Pro/Team seats or Individual-plan extra usage billed to your card). Most teams track one and forget the other.

Tracking metered API usage

The Anthropic console shows usage, and the Usage & Cost Admin API (admin key from console.anthropic.com → Settings → Admin keys) exposes daily cost and token data per model and workspace. Like OpenAI's equivalent, it's raw material: accurate, but you build the history, trends, and alerts yourself.

The spend everyone misses: subscription receipts

Claude.ai subscriptions and Individual-plan auto-recharge charges don't appear in the API cost data at all — they arrive as email receipts from Anthropic. If you only track the API, this spend is invisible. If you naively add receipts on top of API data, you risk double-counting the API charges that also generate receipts. The fix is classifying each receipt: consumer/subscription charges count separately; API-billing receipts don't (they're already in the metered data).

How Prism handles it

Prism pulls metered usage from the Admin API daily and detects Anthropic receipts in your inbox, classifying each one as API billing or subscription spend so nothing is missed and nothing is counted twice. You get per-model breakdowns, month-over-month trends, forecasting, and budget alerts — alongside every other tool in your stack.