LimitWatch: AI plan limits, tracked over time

Latest published limits

Native units, as published. We do not invent message counts where providers only give token budgets or multipliers. ? means honestly unpublished.

Provider / Plan	$/mo	Limit	Window	Model	Source

Value per dollar (theoretical ceiling)

Throughput per $ if you used the whole limit every window. A ceiling, not typical use. Compared only within the same unit. We never silently equate a message to a token. Multiplier-only plans (no published absolute) show as relative and can't be valued.

Cross-provider estimate

The only honest way to line up messages vs tokens: pick how many tokens a message is worth. This knob is the assumption, so drag it.

tokens per message: 700

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

Measured usage (real accounts)

What included usage actually delivered on real maxed-out accounts, for plans that publish only a dollar credit. This is observed consumption in one billing month, not a cap. It's how we turn an opaque $X usage credit into real tokens. crowdsourced

Limit changelog

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

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.