Direct answer
Compare an entered plan price with your measured API-equivalent pace
Claude subscription entitlement and Claude API billing are different products. This worksheet projects a local API-equivalent usage estimate to 30 days and compares it with a price you enter. It does not calculate your subscription bill, remaining allowance, quota, reset window, or guaranteed economic value—and a result above 1× does not mean your plan covers the same volume of API traffic. Local /costand log-derived estimates remain estimates; neither one equals the subscription bill.
Project observed usage to a 30-day pace
All three inputs stay in this browser. The worksheet compares two dollar-shaped numbers; it does not query your Anthropic account or plan allowance.
Projected 30-day API-equivalent cost
$77.14
Observed cost ÷ 7 days × 30. This is a pace projection, not a bill.
API-equivalent / entered-price ratio
2.08×
A ratio above 1 is not guaranteed savings and does not mean a subscription covers that API volume.
Projected minus entered price
+$40.14
Projected API-equivalent usage is above the entered subscription price
Break-even daily API-equivalent pace
$1.23
$37.00 ÷ 30 days; a comparison threshold, not a quota.
Scenario comparison
Entered monthly price vs projected API-equivalent pace
Projected API-equivalent usage is above the entered subscription price
Bar lengths compare only the two worksheet values. They do not visualize allowance, remaining quota, reset windows, request limits, or subscription coverage.
Transparent projection
What the 30-day comparison actually computes
The calculator takes the API-equivalent cost observed across a known number of calendar days, estimates a daily pace, and multiplies that pace by 30. It then divides the projection by the user-entered monthly price for a ratio and subtracts the price for a neutral dollar difference. It uses the shared calculator math for every live result.
Choose the right question
When this comparison helps—and when it does not
Useful for a personal planning scenario
- • Comparing your measured API-equivalent pace with the price you personally pay.
- • Testing how a longer or shorter observation window changes a planning estimate.
- • Finding the daily API-equivalent pace that equals the entered monthly price.
- • Discussing workload mix and utilization without pretending the estimate is an invoice.
Not suitable for account or billing decisions
- • Predicting exact subscription limits, reset windows, priority, or remaining usage.
- • Claiming that API-equivalent dollars were avoided or would have been purchased.
- • Reconciling provider invoices, taxes, credits, overages, or enterprise terms.
- • Comparing coworkers without normalizing days, models, cache mix, tasks, and coverage.
Gather a defensible input
How to gather observed API-equivalent cost
Choose a complete window
Use exact start and end dates. Seven to thirty calendar days usually reveals work and idle patterns better than one unusually heavy session.
Read the official/local view
Use Claude Code's documented /cost command or compatible local logs to collect token and API-equivalent estimates. Record what the view includes and its date range.
Keep rates and models visible
Confirm which models, input/output buckets, cache reads/writes, and dated prices are represented. Missing pricing makes a low estimate look more precise than it is.
whoburnedmore can read supported local Claude Code usage and produce daily/model history. The standard command signs in and submits daily aggregate rows; npx whoburnedmore --local creates a local report without sign-in or aggregate upload unless you accept its interactive publish offer, which signs in and submits aggregates. Neither route turns an API-equivalent estimate into a statement about subscription allowance.
Worked example
An illustrative seven-day worksheet
This intentionally generic example is not a current or historical Claude plan price, recommendation, or typical user profile. It simply demonstrates the calculator's outputs.
| Worksheet value | Illustrative input | Calculated output |
|---|---|---|
| User-entered monthly price | $37.00 | assumption only |
| Observed API-equivalent estimate | $18.00 over 7 days | $77.14 at a 30-day pace |
| Neutral comparison | projection ÷ entered price | 2.08× · +$40.14 |
| Break-even daily pace | entered price ÷ 30 | $1.23 per day |
Interpretation guardrails
Why a precise ratio can still be uncertain
Short-window volatility
A deadline week projected across 30 days can exaggerate normal usage; a holiday or onboarding week can understate it. Compare several windows before treating the pace as stable.
Workdays versus calendar days
If the observed cost covers five active workdays but you enter five instead of the seven calendar days that elapsed, the projection assumes that work pace continues every day. Choose deliberately and label it.
Cache and model mix
API-equivalent cost depends on which model handled each turn and how input, output, cache reads, and cache writes are priced. Token totals alone cannot recover missing bucket detail.
Rate coverage and freshness
Local logs may contain models without a recognized price or may use a dated public rate table. Record the source and date; provider billing remains authoritative.
Methodology and limitations
Every calculation uses the user-entered monthly price, observed API-equivalent cost, and observation days. The live projection is observed cost divided by days and multiplied by 30. The ratio divides that projection by the entered price; the difference subtracts the price; the break-even pace divides the entered price by 30. Inputs are processed locally in the browser and are not submitted by this page.
API-equivalent cost means what measured tokens could cost under the selected or recognized API rates. It is not the amount billed to a Claude subscription, a statement that an API purchase would otherwise have occurred, or evidence that subscription entitlement covers the projected API volume. Account status and provider documentation remain the source of truth for current plans, limits, reset behavior, and billing.
The result is only as complete as the logs, models, cache buckets, and dated price entries behind the observed estimate. Use a longer representative window, preserve idle days when modeling calendar pace, and test high/low scenarios before using the comparison in a budget.
Sources
- Claude Code cost and usage documentation
Official guidance for inspecting API-equivalent Claude Code usage; subscription entitlement and API billing remain distinct.
- LiteLLM model pricing dataset
Public model pricing reference used for API-equivalent estimates; provider billing remains authoritative.