← Reddit

Ran ccusage on my Max 20x: $6,677 of API-rate usage in 37 days on a $200/mo plan. What's your number?

Reddit · Kitchen_Ice1021 · July 22, 2026
A user ran API usage tracking on a Claude Max 20x subscription and found $6,677.54 in standard API rate pricing accumulated over 37 days, substantially exceeding the $200 monthly subscription cost. The usage consisted of 5.65 billion tokens primarily processed through Fable 5 (61%) and Opus 4.8 models, with 98% of the tokens being cached reads billed at a reduced rate.

Detailed Analysis

A Reddit post detailing one developer's Claude Code usage illustrates the extreme value arbitrage possible under Anthropic's Max subscription tiers. The user, on a $200/month Max 20x plan, ran the open-source `ccusage` tool to calculate that their actual API-rate-equivalent consumption over 37 days totaled $6,677.54 — roughly 27 times the subscription cost paid over the same period. The breakdown shows heavy reliance on higher-tier models (a combination the poster refers to as "Fable 5" and "Opus 4.8," alongside Sonnet and Haiku variants), with 5.65 billion total tokens processed, the overwhelming majority (5.55 billion, or ~98%) being cached reads rather than fresh input or output tokens. Peak single-day usage hit $894 in equivalent API cost, averaging $180/day.

The mechanics behind this gap are important to understand correctly. Anthropic's prompt caching system bills cached token reads at a fraction (roughly 10%) of standard input pricing, which is why the ccusage tool's dollar-denominated comparison is presented as more meaningful than raw token counts — a naive token tally would wildly overstate the economic reality. Still, even with caching discounts applied, the gap between subscription cost and API-equivalent value is enormous, reflecting how coding agents like Claude Code generate massive token throughput through iterative file reads, tool calls, and context re-processing across a long session history. This is a structural feature of agentic coding workflows: each interaction may re-send large swaths of codebase context, and prompt caching exists specifically to make that repeated context economically viable rather than prohibitively expensive.

This post is emblematic of a broader trend within the Claude Code and power-user community: using usage-tracking tools like `ccusage` to quantify and publicly compare how much value subscribers are extracting from flat-rate Max plans relative to metered API pricing. Similar posts have proliferated on r/ClaudeAI and adjacent forums, turning usage transparency into a kind of badge of honor or curiosity exercise among developers who treat Claude Code as a near-continuous coding collaborator rather than an occasional query tool. The "what's your number" framing invites a crowdsourced benchmark, and it also implicitly stress-tests Anthropic's pricing model — flat subscriptions are profitable for the company on average users but can be loss-leaders on the heaviest ones, a dynamic familiar from telecom "unlimited" plans and cloud storage tiers.

More broadly, this reflects the economics underpinning the current wave of AI coding agents. Anthropic, along with competitors like OpenAI and Google, is betting that subscription pricing drives adoption and stickiness for agentic tools, even as usage patterns for top-decile users push far past what per-token API pricing would imply is sustainable. The heavy skew toward cached tokens also signals how much of an agent's real-world cost lies not in generating novel output but in maintaining and re-reading context — a technical challenge that caching, sliding context windows, and more efficient memory architectures are designed to solve. As agentic coding tools become mainstream, incidents like this one raise real questions about whether flat-rate consumer pricing can hold up against increasingly autonomous, high-throughput usage, or whether providers will eventually need tiered usage caps, dynamic pricing, or additional throttling to protect margins on their most engaged customers.

Article image Read original article →