Live events & highlights

Temporary promos/throttles with countdowns, plus the big stuff: model upgrades, price moves, new plans. The exhaustive per-limit log lives in Changelog.

Sortable list By provider By price

Current snapshot

Latest published limits

One row per plan, native units as published. Group by provider or by price tier. We do not invent message counts where providers only give token budgets or multipliers. ? means honestly unpublished. Best value per $ ->

How to read this

Confidence — official provider page · announced blog/exec post · community 3rd-party measured · crowdsourced user reports

Sources — values with a dotted underline are quotes: hover to read the exact source sentence, click to pin it. Every row also links its src.

Units — messages, tokens, and requests are absolute caps. 5× Pro is a relative multiplier with no published absolute. $20 usage is a monthly dollar credit, not a throughput cap.

Windows — /3h /4h /5h /day /wk /mo is the refresh period. ? means the provider hasn't published a number.

Compare value

Which plan gives more per dollar

Two lenses: hard same-unit value (no assumptions), and a normalized cross-provider estimate (with adjustable assumptions). We never silently equate a message to a token.

Value per $ — hard caps, same unit only

Throughput per $ if you used the whole limit every window: a ceiling, not typical use. Multiplier-only plans (no published absolute) can't be valued here.

Cross-provider estimate — normalized to tokens / day / $

The closest head-to-head, but it has assumptions: message caps become tokens, dollar credits convert at a token price. Estimated rows are labelled, not passed off as hard facts.

Tune the assumptions below. The ranking updates live, and the table labels estimated rows instead of pretending they are hard facts.

tokens per message: 700 credit $ / million tokens: 5

Provider / Plan	$/mo	est. tokens / day / $

Real measured usage

What plans actually delivered (observed, not caps)

Real readings, not published numbers: what a subscription let you do before it throttled, and what a maxed account actually consumed. The only way to see caps that no API exposes. crowdsourced

Submit a reading →

Drift tracker

Price history

Each plan's published price across every snapshot we have. Backfilled from the Wayback Machine, so the line grows as history accumulates. Hover a sparkline for the dated points.

Drift tracker

Limit changelog

Derived by diffing snapshots. This is the part nobody else tracks: when limits silently move.

Provenance

Why you can trust this

Every number carries a confidence tier and a link to its source. Hover any dotted limit to read the exact source sentence.
We store only as-published facts. Per-day / $-value / cross-provider math is derived in your browser, never baked into the data.
Raw dated snapshots are public and version-controlled. The git history is the audit trail.

official provider page announced blog/exec post community 3rd-party measured crowdsourced user reports

AI usage limits, with receiptsLimitWatch