The stored snapshot came from the active official public pricing page for that provider, which remains the preferred path across the site.
AI pricing data sources and coverage
Use this page for support queries like where AI API prices come from, what verified fallback means, and which providers currently have live coverage. It explains trust policy and coverage, not formulas or glossary terms.
Use this page when the support query is about official sources, verified fallback, baseline usage, or provider-level coverage status.
Methodology is the right page for calculation mechanics, while glossary is the right page for term definitions.
Once trust policy is clear, move into provider coverage, live model rows, or recent changes to inspect the market itself.
Source policy
Official public pricing sources are preferred first. If that path is unstable, the site labels verified fallback or baseline usage instead of silently mixing source quality.
Freshness policy
Every public number should resolve to a stored snapshot time. Freshness is shown directly instead of implied by page render time.
Trust policy
Traceability wins over pretending coverage is complete. Missing or fallback states stay visible on the page.
Provider coverage
Use this table to understand current provider-level coverage, not to assume every provider has identical source quality, crawl depth, or listed batch pricing coverage.
| Provider | Status | Models | Cached | Batch listed | Latest snapshot |
|---|---|---|---|---|---|
|
Anthropic
Official website
|
Live snapshot | 4 | 4 | 0 | Updated Jul 13, 22:05 |
|
Gemini
Official website
|
Live snapshot | 3 | 3 | 3 | Updated Mar 30, 02:54 |
|
OpenAI
Official website
|
Live snapshot | 9 | 9 | 0 | Updated Jul 8, 22:05 |
Batch counts on this page mean models with a normalized batch pricing field currently listed. They do not claim every model under a provider supports batch execution.
What this page answers well
Which providers are live now, how much model-level pricing depth exists, and how source labels should be interpreted at a policy level.
What still needs more data
A deeper provider-by-provider crawl health timeline, model-level source-quality distribution, and more granular freshness diagnostics would require additional data support, not just better wording.
Where to go next
Open provider pages for ecosystem detail, methodology for data flow, and FAQ if you only need a shorter trust explanation.
Use provider pages when source interpretation is clear and you want ecosystem-level coverage next.
Browse providersUse model pages once source policy is clear and you want the latest normalized prices, history, and detail-level trust signals.
Browse modelsUse changes when you want to see which providers or models actually moved after understanding the source policy.
Open changes