SOURCES, DATES & EVIDENCE

How a notice earns
its place here.

ModelClock tracks AI model releases, deprecations and shutdowns from official provider pages. Every published notice links back to the source and includes the provider’s own words.

  1. Find the official source

    Discovery uses model catalogs, provider documentation, release notes and web searches. Community suggestions help fill the gaps. A catalog entry or search result is a lead; it does not establish a release or retirement on its own.

    Known providers keep their verified identity. New domains need evidence of first-party ownership, such as a branded homepage and linked documentation. Public reachability, redirects and page relevance are checked before a source can join monitoring.

  2. Read the evidence

    Structured tables are parsed directly. AI helps extract claims from prose, which must be grounded in the fetched page. Publication checks look for the model identifier, the lifecycle change, the date and the scope supported by the source. A submitted model name or date is never evidence by itself.

  3. Keep dates and platforms precise

    A model’s announcement date, deprecation date and shutdown date mean different things. A model on an original provider’s API can also have a different retirement schedule on a cloud platform. Notices keep the affected platform, region, version and deployment scope where the provider specifies them.

  4. Recheck and record changes

    Collection is scheduled every six hours; source suggestions are reviewed on a two-hour schedule. Temporary failures can delay checks, so each source shows its latest successful read. Changes to published notices retain revision history. Incomplete extraction and unavailable sources remain visible in Sources & coverage on the overview.

What the dates mean

Deprecated
The provider recommends moving away from the model. It may still accept requests; an exact removal date might not exist.
Shutdown scheduled
The provider has published a cutoff. Timed alert reminders use unambiguous, exact official shutdown dates.
No earlier than
A lower bound. The model may remain available longer; this is not an exact shutdown appointment.
Available until at least
A minimum lifetime commitment for an active model. It is kept as an availability guarantee, separate from deprecation notices.
Date has arrived
The provider’s published cutoff has passed. ModelClock does not independently test whether authenticated API requests still work.

Coverage has limits

The public tracker starts on January 1, 2026. It includes announcements in this window and lifecycle deadlines in this window that were announced earlier. Importing an older announcement does not make it a new release. Undated or unsupported claims stay out of the public notice timeline.

Early signals are separate from official notices and never enter subscription alerts. An absent notice means we haven’t published evidence for it; it is not a guarantee that a model is supported. Check the provider’s current documentation before planning a migration.

Suggestions and corrections

Suggest a missing model or official page and save the tracking link to follow its verification status. Checks are automatic and can end with a request for additional evidence. Accepting a source queues collection; publishing a notice still requires the usual evidence checks.

If something is incorrect, use “Report an issue” in the More menu or contact the maintainer with the model identifier, official link and the detail that needs correcting.