Claude Pro limits: how much you really get per week

Measured over 2026 10/01 – 10/08, a full week of Claude Pro ($20 monthly ($17 a month billed yearly)) is worth about $162 of official API usage (≈ $703 a month), 35× its price. That is about 120M tokens a week, of which about 25.3M are not cache reads.

Data updated 2026-10-08

Claude Pro

  • Weekly limit ≈ API value: $162 (≈ $703/mo · middle half of accounts: $149–$175)
  • Tokens excl. cache reads: 25.3M (1.0M output)
  • One 5-hour window ≈: $14 (A week holds ≈ 12 full windows)
  • × monthly price: 35× (280 accounts)

Accounts on the same plan differ too: the middle half of Claude Pro accounts sits between $149–$175 (±8%). Vendors A/B-test limits on a few accounts (SemiAnalysis found one of three identical accounts about 20% lower); we measure dozens to hundreds of accounts per plan, so a single outlier does not move the median.

Model mix (by API value)

Hit your Claude Pro limit?

Wait for the 5-hour window or the week to reset; cut down on fresh sessions and very long outputs; or keep using the same model pay-as-you-go. Wokey serves the same Claude models over the native Anthropic API, so Claude Code only needs a new ANTHROPIC_BASE_URL.

Use Claude Code with Wokey

Subscription or pay-as-you-go

A plan is the best deal when you use all of it. Most people do not: below the share shown here, paying per token costs less than the subscription. When you hit the weekly limit, you can keep using the same model on Wokey.

  • Claude Pro: if you use less than 19% of its weekly limit, Wokey pay-as-you-go costs less

What uses up your limit

  • Cache reads barely count: On Claude plans a cache-read token uses close to none of your limit. Most tokens in a long session are cache reads, so "tokens used" and "limit used" are very different numbers.
  • Cache writes ≈ uncached input: New context entering the cache costs about the same as uncached input. Starting fresh sessions or rewriting large context burns the limit fastest.
  • Output costs about 4–7× input: Within one model, each output token uses roughly 4–7 times the limit of an input token. Asking for long files or documents in one go drains it noticeably faster.
  • Opus 5.5 is cheaper on the limit: Per token, Opus 5.5 uses about 0.6× the limit of other Opus and Fable models. The same work on an older Opus or on Fable empties the week sooner.

From a regression on Claude Pro accounts’ limit changes, 2026-09-28 (R² 0.965). Codex meters differently and is not included.

Week over week

Remeasured every Monday. When a vendor changes its limits, these lines move; changes under about 10% in a single week are mostly sampling noise.

  • Claude Pro: 09-24 $125 → 10-01 $145 → 10-08 $162

Limit changes

  • 2026-09-13: The Claude Code summer promotion that raised weekly limits by 50% ended (r/ClaudeCode)
  • 2026-09-22: Opus 5.5 launched and Anthropic raised 5-hour limits on Pro, Max and Team; SemiAnalysis measured Opus 5.5 limits about 20% higher on Max and 50% higher on Pro (Claude on X)

How we measure

  • The data comes from limit changes on real subscription accounts behind the Wokey gateway, together with the traffic they served. When an account’s weekly usage rises by at least 10 percentage points, the requests in that span, divided by the rise, give a full week of traffic.
  • Each span needs at least 10 requests, with no more than 5% failed or boundary-crossing requests. Spans are first reduced to a median per account, then to a median across accounts, so every account counts once.
  • Traffic is priced at each model’s official API rates, including cache reads and 5-minute and 1-hour cache writes. The dollar figure means "what this traffic would cost on the official API"; it is not the unit the vendor meters in.
  • Every Monday after 04:00 UTC the past 7 days are remeasured. A plan is published once at least 5 accounts are measured. If a value moves more than 15% from the previous week, it is checked by hand before the page updates.
  • The limit is worth more or less depending on the model mix: the same limit spent on a different main model converts to a different API value. Each plan lists its model mix.

These are measured estimates, not figures published by the vendors. Vendors can change limits at any time, and use outside the gateway or delayed metering can shift the results.

FAQ

How many tokens does Claude Pro give per week?

A median account using the full week runs about 120M tokens, of which about 25.3M are not cache reads and 1.0M are output. Cache reads are 79% of the total and barely count against the limit, so the total swings with your cache hit rate.

How much Claude Pro usage do you get per day or per 5 hours?

The weekly limit holds ≈ 12 full 5-hour windows, or about $23 of API value a day on average. One full 5-hour window is worth about $14.

Is Claude Pro worth it?

If you use it fully: a week is worth about $162 of official API usage, 35× its price. If you use less than 19% of the limit, pay-as-you-go costs less.

Is Claude Pro unlimited?

No. Every tier has both a 5-hour window and a weekly cap; when either runs out you wait for the reset.

Why does my Claude limit drain so fast?

Usually cache misses (new sessions, rewriting large context), very long outputs, or models that weigh more on the limit (older Opus, Fable). Cache reads barely count, cache writes cost like uncached input, and output costs about 4–7× input.

How do the weekly limit and the 5-hour limit interact?

Both apply at once: the 5-hour window caps bursts and the weekly limit caps the 7-day total, and whichever runs out first stops you. Higher tiers have large 5-hour windows, so the weekly limit is usually the one you hit.