Skip to main content

Consumption Pricing

The Claude Developer Platform bills by tokens consumed, not seats sold. The bill scales with how much the product actually runs.

Hand-drawn line illustration in warm terracotta and cream: two loopy line-drawn hands drawn from one continuous line, the left holding a small cream cup and the right a much larger one, a one-line profile face above between them.

The two meters​

Anthropic sells the same models through two different meters. Claude, Claude Code, and Claude for Work subscriptions are seats: a person pays a flat rate and usage lives inside plan limits. The API is consumption: per-token prices by model, published on the platform pricing docs (verify current figures there; prices change with model generations), with no seat in sight.

The distinction matters most to a founder because their product sits on the consumption meter. A seat business's cost is headcount-shaped and predictable; a token business's cost is usage-shaped and grows exactly as fast as the product succeeds. Every scaling story in the customer corpus is implicitly a consumption story: Tasklet reports "450,000 agent actions executed per day across all customer agents" (source), and Windsurf reports "100M tokens processed per minute" (source). Numbers like those are simultaneously growth metrics and cost structures.

Why the alignment is real​

Under consumption pricing, the platform earns nothing extra from a builder's idle integration. Revenue arrives only when the builder's product runs, which means the platform's growth depends on builders' products being worth running at volume. That is a structurally different relationship than a seat license, where the sale precedes the usage and shelfware still bills.

It also explains why the cost levers exist and are documented so aggressively. Prompt caching reads at a fraction of base price, the Batch API at half, the effort dial trimming tokens per step: each one lowers the price of a unit of work, which lowers the threshold at which automating that work is worth it, which expands what gets built. Dust's reported "$10k/day saved" on model spend after optimizing caching (source) is a customer keeping margin, and a workload that stays economical to run.

The unit that matters is the outcome​

Token prices are the input cost; the number a business actually manages is cost per completed unit of work. The corpus's most instructive figures are stated that way: Freedom Forever prices its permit agent at "$0.20–$0.35" per run against a human-equivalent task it says costs several times more (source), and OffDeal reports a buyer list that "would traditionally take a team of analysts more than a week to assemble and cost upward of $12,000" now produced "for roughly $200 in compute." (source)

When the per-outcome math clears, consumption growth is good news on both sides of the meter. When it does not, no discount rescues it; the fix is architecture, which is what the rest of the cost concepts are for.

Further Reading​