MonoMind monogramModelScale

Models / Lifecycle radar

Model lifecycle & route expiry radar

Track provider-reported route expiry with source evidence in view. A route expiry is separate from model retirement, endpoint availability, and successor guidance.

Routes with reported expiry
Unavailable
Next route expiry
Not reported
As of UTC
2026-09-14

Published lifecycle evidence is unavailable. Missing records do not establish indefinite availability.

01 / expiry watch

Provider route expiry watch

Review reported dates in decision cards or a compact table.

Lifecycle evidence unavailable

No published route expiry evidence is available.

Missing notices do not imply indefinite availability. The 60 and 90 day horizons include today and upcoming dates; All also shows past and distant dates.

Release timeline

No source-backed model release timeline is published in this catalog. Provider expiry dates and directory observations are not model launch dates.

Evidence boundary

A passed expiry date does not prove an endpoint is offline. A far-future date remains the provider’s reported value; no sentinel meaning is assumed. Check the linked provider documentation before a migration.

Open model workbench →Read practical guides →
Lifecycle publication provenance

Catalog revision: Not reported

Published: Not reported

Page date is used only to calculate days remaining. It does not refresh the underlying source observations.