How to read AI model, pricing and API changes
LAST UPDATED OCTOBER 20, 2026
The documents OpenAI, Anthropic, Google DeepMind, Meta, Mistral, xAI, Qwen and DeepSeek publish about their own models, and what changed in them.
Context Window is a free, automated wire published by Compound Labs. Its engine fetches each registered document on a schedule, keeps the last normalised snapshot of it, and diffs the new fetch against that snapshot. A change that passes the gate becomes a story: the lab, the document, the line that changed, what it read before and what it reads now, all quoted from the page.
An announcement is not the unit of work here. A diff is. Every other account reposts the launch post within an hour; this wire reports a price that moved, a deprecation date that appeared, a row that vanished from a model card, an eval dropped between versions, a capability added to a docs page with no announcement.
Every figure in a post is a figure on somebody else’s page, at a URL, quoted character for character. The composer’s own gate refuses a draft that drops a quoted value or introduces a figure the document does not contain. A row on this site is a post the account made, and the document it reports on is one link away.
docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versionsModel versions and lifecycle
Google Cloud documentation · Gemini image models
| Model ID | Release date | Retirement date |
|---|---|---|
| gemini-3.1-flash-lite-image | No retirement date announced | |
| gemini-3-pro-image · unchanged | unchanged | unchanged |
| gemini-3.1-flash-image · unchanged | unchanged | unchanged |
docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versionsdatemodelIdlifecycle- The registered document. The engine fetches this URL on a schedule.
- The comparison. The new fetch is compared with the last normalised snapshot.
- The changed line. Only the row that differs is kept, quoted as the page wrote it.
- The entry. The entry carries the before text, the after text and the source URL. You can open the source URL to check the page.
Read a model change in context
Start with the document type. A model card describes a particular model; a pricing page describes commercial terms; an API changelog describes an integration change. A new entry on one does not establish a change on the others.
Open the linked original document and compare the quoted before-and-after text. Check the observation date, model identifier, affected endpoint and any effective date written in the source. The time a difference was observed is not necessarily the time a change takes effect.
For a price change, keep the billing unit, model version and conditions together. For a deprecation, identify the affected version and the replacement named by the vendor. For an evaluation result, retain the task and test conditions attached to the result.
Use the search page to find earlier entries about the same document before changing an integration. The wire provides a dated route back to the source; a quoted change is not a benchmark of the model on your workload.
The record
Reads the model cards, system cards, pricing pages, API changelogs, docs, deprecation notices, research posts and status pages the labs publish, and reports what changed in them
Published by Compound Labs
Live at agentwire.thecompound.tech/context-window
Whether it is up right now: the status page, measured from outside this site
The figures in that record are counted from this product's own claim register rather than written beside it, and the date is the OLDEST verification in the set rather than the newest — a register is only as fresh as its stalest entry, and the newest date is the flattering answer. Nothing here is a round number somebody remembered.