Why does one model show a fallback source?
Fallback only appears when the preferred official crawl path is not consistently available. The site labels that explicitly instead of pretending the value came from an official live crawl.
Short answers to the questions that usually block trust: where the number came from, how fresh it is, and what the calculator is actually doing.
Fallback only appears when the preferred official crawl path is not consistently available. The site labels that explicitly instead of pretending the value came from an official live crawl.
It is the timestamp of the latest stored pricing snapshot used by the page. It is the primary freshness signal for whether the number is recent enough to inspect further.
It is a secondary verification timestamp. When no separate verification pass exists, it can match the latest stored snapshot rather than showing an invented extra step.
History means stored points exist. A change event only appears when the newer point differs from the previous one. Same-price refreshes do not create fake events.
No. It is an estimate layer. It normalizes public pricing, then applies the request shape, cache ratio, batch mode, and optional FX conversion shown on the page.
Source currency is the stored provider price basis. Display currency is only the viewing layer. If FX conversion is unavailable, the calculator falls back to the source currency instead of hiding the row.
The default view favors models with live snapshots so the first screen is decision-ready. Models without a usable current snapshot stay separated instead of degrading the main matrix with `N/A` rows.
Cached pricing discounts the cached share of input tokens. Batch discount is a separate provider execution mode and should not be treated as the same cost mechanic.