Daily record · 21 Nov 2026

Model Ledger

How a row gets into the ledger.

Model Ledger keeps an append-only daily record so a reader in ten years can see what was available, where, at what price, and when it was retired — and how widely used open-weight models moved around those changes.

Append-only

Events are inserted. Application code has no update or delete path for events, snapshots, snapshot items, or metrics. A mistake is a new correction event that points at the old id. Operational tables — the mail queue, pageview counters, the sponsor of the week — are not the historical record and can change.

What “observed” means

Rows marked Transcribed were copied by hand from the cited page on 21 Nov 2026. Their event_date is the date in the source. Their observed_at is the source’s publication date when that date is explicit, and the transcription day when it is not. They are not live collector captures.

The daily job at 11:00 UTC writes a snapshot, then diffs it with the previous snapshot. New listings, removals, and base-price changes become events with observed_live: true. The first snapshot of a source lists everything, because there was no prior day to diff. Deprecation pages are parsed only when a repeated table names both a model and a shutdown or retirement column and yields at least three rows. Otherwise the snapshot is stored and a candidate is queued for a person.

Sources and licenses

Our compilation

The event feed and JSON are © Model Ledger contributors and licensed CC BY 4.0. Upstream pages keep their own licenses. Attribute “Model Ledger” and link the record.

Corrections

Use the submission form. A person approves it by appending an event. The old event stays.

Google’s Gemini page publishes earliest shutdown dates, not always a separate announcement date. Those rows say so. Vertex’s 16 Oct 2026 Gemini 2.5 retirement is the date in the 2 Apr 2026 release notes, recorded as a schedule rather than a confirmed outage.