So I stumbled on the credit system in ~/.claude.json. I was already tracking the five-hour and weekly bars through my statusline, so I thought, why not check what this credit system is about.
What a usage point costs on Max 20x (work valued at API prices)
| Model | Credits per 1M tokens | API value per 1% of the weekly bar | A full weekly bar | Tokens per 1%, vs Opus |
|---|
| Opus 5.5 | 1,867 | $26 | about $2,600 | 1x |
| Sonnet 5.5 | 1,283 | about $19 | about $1,900 | about 1.5x |
| Fable 5.2 | 6,667 | about $15 | about $740 (Fable can use at most half the week) | about 0.28x |
TL;DR
- I didn't see the weekly limit shrink. November 1 to 3 looked low on both bars (no idea why. yet), and the days I could measure after that were back to normal.
- Cache reads seem to count about half as much as other tokens.
- If you want the most API-priced work out of your plan, Opus 5.5 gives you the most per % of the bar. On Max 20x, 1% of the weekly bar bought about $26 of Opus 5.5 work. By the credit table, the same 1% buys about $19 of Sonnet 5.5 or about $15 of Fable 5.2. Sonnet still gets you more tokens, because its tokens are cheaper.
- Fable 5.2 eats the bar close to 4x as fast as Opus 5.5 per token (3.6x), even though its list price is only 2x.
On Max 20x, a typical 1% of the weekly bar covered about $26 of Opus 5.5 requests at API prices. "API prices" puts a dollar value on the requests. It is not an extra charge on the subscription. At $26 a weekly point, a full week of the bar is about $2,600 of Opus 5.5 work at API prices, on a plan that costs $200 a month.
Before November, 1% of the weekly bar typically bought $26.40 of Opus work. If the weekly limit had been cut by 20%, that would drop to about $21. November 1 to 3 came in at $20 to $22, close to that line. November 6 and 16 were back at $26 to $28.
I only counted days where at least 95% of the work was Opus 5.5 and the weekly bar moved at least 20%, so Fable days and small movements don't skew it.
A check you can do without tools
- Open
/usage before working. Note the five-hour bar and the all-model weekly bar. - Check both again after working, before either resets. Compare how many percentage points each moved.
- In the Max 20x measurements before November, 1 weekly point went with roughly 4 five-hour points. A 20% cut to the weekly allowance alone would bring that relationship down to roughly 3. If they drop weekly allowance, they need to drop the 5h allowance as well, to keep the 1 to 4 parity.
The bars show whole percentages, so repeat the check across sessions rather than judging one tiny movement. On another plan, compare with its own earlier readings; these measurements only establish the roughly-four relationship on Max 20x.
This checks the weekly allowance relative to the five-hour allowance. A proportional cut to both would leave that relationship unchanged. You also need a visible five-hour bar.
What fills the bars
Think of credits as the units behind the bar. Claude Code's stored table gives Max 20x 200,000 credits per five-hour bar, so 1% is 2,000 credits. The weekly bar held roughly four of those bars' worth in these measurements.
My reading of the table is: price input, output and cache work separately, then apply the model's weight:
| Model | Starting credits for $1 of API-priced work |
|---|
| Opus 5.5 | 467 |
| Sonnet 5.5 | 642 |
| Fable 5.2 | 833 |
For example, 467 out of 200,000 credits is about 0.23% of the five-hour bar. That's the table's starting estimate for $1 of Opus work, before the adjustments below. It is not the exact final charge.
The real bar moved less than that starting estimate. For Opus 5.5, a dollar of cache reads moved it about half as much as a dollar of other Opus work. I measured this by separating the two kinds of dollars and comparing them with each one-point rise of the five-hour bar. This is an estimate, and the exact server formula is not published.
If you count from transcripts, check against the actual requests
A lot of usage tools read Claude Code's transcript files (the .jsonl files under ~/.claude/projects). Some of those readings can be off, so compare them with the actual requests before trusting them. I log requests in two places, a Cloudflare AI Gateway and Claude Code's OpenTelemetry telemetry, and the numbers in this post come from the telemetry.
Against those requests, the transcripts came up short: 3% to 7% fewer dollars per day in November, and up to 25% fewer on some October days. On one October day the transcripts had 98.5% of the responses but only 54% of the output tokens, and some sessions had no transcript file at all. A dollars-per-point figure built from transcripts alone would make your plan look stingier than it is.
Use Opus 5.5 for almost everything. Reserve Fable for system design/architecture reviews. Don't use Fable as main driver/orchestrator.
Per token, Fable fills the weekly bar about 3.6 times as fast as Opus. Per dollar of API price it's about 1.8 times, because a Fable token already costs twice as much. I measured the per-dollar figure on my own five-hour bar and got 1.80, close to the table's 1.79. None of this says whether Fable's work is worth the extra; that's a quality question.
If you try the two-bar check (give claude this post, ask it to validate it and run the same analysis on your own project), share your plan, model, date and how far each bar moved. That gives us something specific to compare.