Methodology

How we verify

Most directories publish a price once and never look again. This page describes exactly what we do instead, including what we get wrong.

Where each number comes from

• Model pricing, context windows, cutoffs and retirement dates come from the OpenRouter API — a real, versioned interface.
• Provider status comes from each provider's own statuspage feed.
• Consumer subscription prices are read from the provider's public pricing page. There is no API for these, so this is the least reliable tier and is fenced accordingly.

The four guards on a scraped price

A scraped value is published only when it clears all four. Otherwise the previously verified value stays, and the page says it is being held.

1. Anchor proximity. The number must appear within 240 characters of the plan name. A price elsewhere on the page is ignored.
2. Sanity bounds. Every plan declares a plausible range. ChatGPT Plus accepts $5–$60, so a $1,500 promo banner is discarded.
3. Delta cap. A move of more than 40% against the current value is refused even if it repeats. Real price changes are small; 10× moves are collection bugs.
4. Two-run confirmation. A new value must appear on two consecutive daily runs before it goes live. A one-day blip never reaches this site.

What happens when a source breaks

Nothing is published. The last verified value stays on the page and is marked as held. The collector never publishes a blank, a zero, or a guess. This means a stale-but-correct number is preferred over a fresh-but-wrong one, always.

What this means for you

A price here can lag a real change by one day by design. Status reflects what a provider reports about itself, which can trail reality. Before you buy anything, confirm on the provider's own page. Every row links to it.

Corrections

If a number here is wrong, it is worth telling us — a wrong bound or a moved anchor is a five-minute fix, and the correction is recorded in the changeloglike everything else.