The two-system boundary
The website and the synchronization system are deliberately separate. The synchronizer collects and validates provider data outside the web runtime. A publication step writes the validated snapshot undersite/public/data. The Next.js site reads only that snapshot.
A future MySQL database belongs to the synchronization system, not to the public page render. The front-end has no direct database credentials and no live provider connection. This keeps deployment, caching and publishing predictable.
Snapshot schema 1.5 · script 2.2 · generated 2026-11-20
1. Collect a public observation
Prices come from public provider endpoints or pricing pages. The provider record keeps the exact evidence_urlused for the offer. If a provider requires an account or does not expose a public price, the offer is not presented as a verified tariff.
2. Normalize to one unit
Every price is converted to USD per 1M tokens. Input and output remain separate because a workload is rarely symmetric. The “total” figure is input + output from one complete offer, never the sum of minima collected from different sellers.
A zero from the source represents a free public tier; an unknown value remains blank. Currency conversions are documented by the collection pipeline rather than guessed at render time.
3. Benchmarks and model evidence
Benchmark enrichment uses the public OpenRouter models API. It is matched first to the exact OpenRouter id already present in the catalog, then to an exact canonical slug, and only as a fallback to an unambiguous normalized Hugging Face id. Enrichment never creates a new canonical model.
Artificial Analysis intelligence, coding and agentic indices, together with Design Arena Elo, win rate and rank, are displayed only when the API publishes them. A missing metric is shown as Not published; it is not estimated, averaged with a different metric or inferred from a similar model. Aggregate pages keep language, embedding, reranker, image, video and audio offers separate.
The measurement definitions remain owned by the benchmark publishers: Artificial Analysis methodologyand Design Arena. Each model sheet records the source URL and UTC collection date. If the OpenRouter response does not provide a license, the sheet says so rather than guessing a license from a model name.
4. Match the model, keep the raw id
Providers often use different names for the same model. The publication pipeline maps confident matches to a canonical manufacturer/model pair and preserves the provider’s raw API id for integration. An uncertain match goes to Other / Unattributed instead of being guessed into a brand page.
Twice-daily refresh and freshness
The synchronization plan schedules each provider twice per day, at 00:00 and 12:00 UTC. Each provider job records its own last attempt, last successful list, last successful price observation and any error. The publication step then assembles one static snapshot and carries those receipts into the public data.
A successful provider refresh replaces that provider’s model list. If a model was present in the previous accepted list and is absent from the new successful list, its offer is withdrawn from that provider and is no longer displayed as available there. A failed, unauthorised, truncated or unreachable response never triggers deletion: it marks the provider as failed or stale and leaves its last accepted data visible with a warning.
Verification status and display
- Priced: at least one public offer has a usable price.
- Specs: context and capability fields are shown only when a source documents them.
- Fresh: the provider’s latest scheduled refresh completed successfully.
- Partial: some providers could not be reached during the latest refresh. The status line shows how many providers were verified; the others keep their last accepted catalog.
- Out of date: the status line turns into a warning only when no provider has been refreshed successfully for more than 14 hours.
- Unavailable: account-only and unreachable prices are not synthesized from another provider’s price or a catalog estimate.
Corrections
If a provider changes a price, an API id or a context window, send the model URL, provider and a public evidence URL through the contact page. A correction is applied to the next snapshot after verification; the live website remains a read-only publication of the last accepted snapshot.
Commercial links are governed by the affiliation disclosure.