How I measured Claude Code usage.

Read this before you quote it

What the $11,442 does and does not mean.

• The cost at API list prices is not savings.

  Without the plan I would have run less work. The plan did not discount an API bill; it changed how much work I did. $11,442 prices that work at API list rates.

• The plan fee is what I paid.

  The money that left my account was $640.00 for this window, at $200 a month. The larger figure is what the same tokens would have cost through the API at list prices — nothing more.

• Usage and plan fees cover the same period.

  Usage runs from 24 May to 27 August 2026: 96 calendar days, 60 of them active. The fee covers the same 96 days, which is why the page shows $640.00, not $200. This is ordinary work across 35 projects, not a benchmark run for a headline.

• A later counting fix does not touch it.

  On 3 October 2026 Caprock stopped pricing twice the turns a forked session copies from its parent. On this machine every such copy came from one fork made on 2 September, after this window closed, so these figures needed no correction.

• It is one developer's machine.

  A sample of one, published because it is measured, not because it is typical. Yours will differ; the tool reads yours.

The dashboard labels this as an API-list equivalent next to the figure. Without that label, a large dollar figure can look like an amount owed.

How it was measured

Four steps, all of them checkable.

1. 01

   Read the transcripts Claude Code already writes.

   Every session leaves a JSONL transcript on disk with per-turn token counts — input, output, cache read, cache write — reported by the API itself. Caprock tails those files; an optional hook shim adds lifecycle events live. The records exist whether or not Caprock is installed.

2. 02

   Price the tokens against a dated table.

   Cost is tokens × the provider's list price for that model, from a versioned pricing table in the repository; this page used table 2026-08-27.1. A price change is a dated version bump, not a silent edit.

3. 03

   Read local files without a proxy.

   Caprock reads local transcripts without routing your requests or needing an Anthropic API key. It listens on 127.0.0.1 by default. The transcripts do not say what your plan costs, so Caprock asks.

4. 04

   Prorate the plan fee to the window, then divide.

   First calculate the plan fee for the measured window, then divide the API-list total by it: $200/month × 96 days ÷ 30 = $640.00, and $11,442 ÷ $640.00 = 17.9×. The product does the same on your data and prints the prorated fee and the caveat next to the multiple, so you can check the division.