Skip to main content
BenchLM
Public usage-policy ledger

Claude usage limits without a made-up timer

Checked
2026-08-11
Public rules
4
Primary sources
3

Public Claude usage-limit mechanics, the shared-product pool, and source changes without pretending to know an individual account’s timer. It records what Anthropic publishes and where the account-specific answer begins.

Your Claude allowance lives in your account

This ledger does not show your remaining messages, credits, or reset clock. Open Settings > Usage in Claude for account-specific usage and spend details.

The public rules worth checking

When do paid-plan session limits reset?

Anthropic’s paid-plan usage-credit guidance says included session limits reset every five hours once reached. Plan and regional details can change, so check the source before relying on a future session.

Claude Help: Manage usage credits for paid Claude plans

Does the same rule apply to Claude Code with an API key?

No. Anthropic distinguishes an Enterprise seat with a rolling included-usage window from API-key use, which is billed pay-as-you-go by the connected Console or cloud account.

Claude Help: Models, usage, and limits in Claude Code

Claude plans, prices and what the same money buys on the API

Prices and included usage are copied from Anthropic's pages with the date we read them. The provider publishes multiples and message estimates, not a token or dollar cap, so the rows keep the provider's wording and no cap is invented.

Claude plans: price, included usage and extra usage with the source and read date.
PlanPriceIncluded usageExtra usageSource
Free$0/monthUsage limits that reset on a rolling five-hour session; the page describes Free as covering everyday questions.NoClaude pricing Read 2026-09-14
Pro$20/month ($17/month billed annually)At least 5x more usage per five-hour session than Free, plus a weekly limit on paid plans.Yes, at standard API rates; up to $2,000 redeemed a dayClaude pricing Read 2026-09-14
Max 5x$100/month5x more usage per five-hour session than Pro, higher output limits, priority access during high-traffic periods, and a weekly limit across all models.Yes, at standard API rates; up to $2,000 redeemed a dayClaude Help: What is the Max plan Read 2026-09-14
Max 20x$200/month20x more usage per five-hour session than Pro, higher output limits, priority access during high-traffic periods, and a weekly limit across all models.Yes, at standard API rates; up to $2,000 redeemed a dayClaude Help: What is the Max plan Read 2026-09-14
Team, standard seat$25 per seat/month ($20 per seat/month billed annually)More usage than Pro per seat, with central billing, SSO, enterprise search and admin controls.Not statedClaude pricing Read 2026-09-14
Team, premium seat$125 per seat/month ($100 per seat/month billed annually)5x more usage than a standard seat.Not statedClaude pricing Read 2026-09-14
Enterprise$20 per seat/month, billed annually onlySeat price plus usage billed at API rates; user and organisation spend limits.Yes, at API ratesClaude pricing Read 2026-09-14

What the Pro price buys at API list rates: $20 is 10 million input tokens or 2 million output tokens of Claude Sonnet 5 ($2 and $10 per million, registry updated September 25, 2026). Arithmetic on published rates, not a statement of the plan's allowance; past the plan's own limit, extra usage is what the provider's page says it is.

Plan price beside the API list cost of a workload

Pick a plan, a Claude model and a workload. The API side is list rates times the tokens you enter, the same arithmetic as the pricing calculator. The plan side is its published price; its cap is not published.

Pro price
$20.00/month
Included usage: At least 5x more usage per five-hour session than Free, plus a weekly limit on paid plans.
Same tokens on the API, list rates
$12.00/month
2,000,000 input and 800,000 output tokens a month on Claude Sonnet 5.
Does the plan cover it?
Unavailable
The plan does not publish its included usage in credits or dollars; no equivalent can be computed. At this workload the API bill is below the plan price; whether the plan would also cover it depends on the unpublished cap.

Keep these assumptions with the decision. The estimate above is today’s list rates against the workload you typed; both move. Save it as a Radar cost scenario and the next review starts from the same numbers, with the source of every rate attached.

Estimate only, at list rates from the pricing registry. It excludes reasoning tokens billed as output, batch discounts, taxes and provider minimums. Confirm the exact model identifier in the model ID directory and the rate on the Claude API pricing hub.

A published reset rule is not your reset clock

Product limits can depend on plan, location, workspace controls, prior use, feature availability, and the exact work requested. A useful public page preserves that distinction rather than turning a provider article into a fake personal dashboard.

Radar watches

  • Published plan, usage-credit, reset-rule, and model-availability changes.
  • Public Claude documentation and release changes with a source link for review.

Radar does not read

  • Your remaining Claude usage, private reset time, conversations, projects, or bill.
  • Usage that is metered through a private API, Bedrock, Vertex, or Foundry account.