How we verify pricing
PlanPulse is built around one rule: every number on this site links to an official source, a last-checked date, and a confidence level. Here's how we apply that rule in practice.
Three signals on every row
Every API and product row in the PlanPulse explorer shows:
- Source link — the official pricing page (provider.com, azure.microsoft.com, aws.amazon.com, anthropic.com, etc.). We never use marketing blog posts or third-party resellers as the source.
- Last checked — the date a human or automated pass confirmed the price still matches the source. The site-wide verification is 2026-06-17; per-row dates are updated whenever a row is reviewed.
- Confidence — High (verified by hand from the official page), Medium (auto from a structured feed), Needs Review (flagged for next pass — never relied on as the primary figure).
What "verified" means
A row is marked High confidence only when a reviewer has opened the official pricing page, located the exact tier or model in the current pricing structure, and transcribed the input/output/cached figures into the table. The screenshot, date, and reviewer are recorded in the data layer.
Medium rows come from the provider's own structured feed (for example, the JSON feed published alongside their pricing docs). We re-render these into our schema and re-check weekly.
Needs Review rows are kept visible because removing them would hide useful context — but they are never the headline figure and always display a "Needs review" label so users know to confirm with the source before billing decisions.
How often we re-verify
Flagship models are reviewed weekly; secondary models and image/video models every two weeks. The Recent changes page lists every pricing update, addition, or correction.
What we deliberately don't do
- We don't show prices that we can't trace to an official source.
- We don't show "discounted" or "negotiated" enterprise rates — those are between the customer and the provider.
- We don't merge channels into a single average; AWS Bedrock pricing depends on model, region, and commitment, so a Bedrock row stays as Needs Review until those variables are pinned down.
How to cite PlanPulse
If you're using our data in an article or research, please cite the per-row source URL and the per-row last-checked date. For a single aggregate citation, use:
PlanPulse, "AI Pricing Comparison", verified 2026-06-17, https://planpulse.online/methodology
Reporting an error
Spotted a wrong price or stale source? Email hello@planpulse.online or use the contact form. We update within 24 hours for confirmed errors and credit the reporter.