Cost explained · 4 min read

API-equivalent cost is not your Claude subscription bill

A profile can show thousands of dollars in estimated usage without you owing that amount. Here is what the cost number actually means.

By claudeusage · Updated 2026-09-27

What the dollar number measures

claudeusage estimates what the uploaded token usage would cost at the API rates in its stored pricing snapshots. Each token category is priced separately for its model. Input, output, cache writes, and cache reads do not necessarily have the same rate.

That estimate helps compare usage over time. It does not read your Anthropic payment history, subscription invoice, account credits, or negotiated rates. It is not a receipt.

Subscription usage and API billing are different

If you use Claude Code through a subscription, the subscription's price and usage limits govern that access. A large API-equivalent estimate does not by itself create an extra charge. Separate API-key usage or other paid usage settings can have different billing rules, so check the account you actually used.

Anthropic's own usage and billing tools are the source for remaining allowances and actual charges. The claudeusage profile answers a narrower question: how much usage is represented in the logs you uploaded?

Why a new model may use an estimated rate

Pricing snapshots are refreshed separately from the CLI. If a snapshot has an exact model entry, that entry is used. Otherwise the resolver can use a related model identifier or a Claude-family fallback. That prevents a new Claude model from silently appearing to cost nothing, but it also means the result is an estimate.

Models without a usable price show Unpriced in the model breakdown. Their token counts remain visible. Summed dollar totals therefore cover priced usage only and can understate the total API-equivalent value of a mixed-model history.

Compare costs fairly

Use the same date range and model mix. Cache-heavy work can have a much larger raw token total without a proportional dollar increase. A profile rank reflects uploaded estimated usage, not software quality, working hours, or money saved.

If you are checking a discrepancy, record the date range, model, raw token categories, and pricing assumptions. Those details are more useful than comparing two rounded headline numbers.

Sources and further reading