Deprecations
Deprecated models and endpoints, with recommended replacements and shut-down dates. As we ship better compaction models we occasionally retire older ones; this is the single place those changes are tracked.
Overview
As we ship safer and more capable compaction models, we occasionally retire older ones. This page lists every deprecation with its recommended replacement and shut-down date, it is the single place those changes are tracked. Accounts actively using an affected model or endpoint are always notified by email and here in the docs, with a blog post and changelog entry for larger changes.
One thing that keeps this list short: the public model ids are stable
aliases. helene-1 and
adeline-1 keep pointing at the current
best engine while internal versions move underneath, so most upgrades
happen transparently and never need a deprecation at all.
Terminology
| Term | Meaning |
|---|---|
| Deprecated | Announced for retirement, with a set shut-down date. Still works until then. |
| Legacy | Still available but no longer receiving updates, a signal to migrate before it is eventually deprecated. |
| Sunset / shut down | Used interchangeably to mean the model or endpoint is no longer accessible. |
Notice periods
We give advance notice before retiring anything customers actively depend on, so there is time to evaluate a replacement, test behavior, and migrate:
| Tier | Minimum notice before shut down |
|---|---|
Generally-available models (e.g. helene-1,
adeline-1)
|
At least 6 months. |
| Dated snapshots pinned behind an alias | At least 3 months. |
| Preview / beta models (identified as such) | As little as 2 weeks. Not recommended for business-critical workloads unless you can migrate on short notice. |
If a safety or compliance concern forces a faster timeline, we give as much notice as is reasonably possible. Need continued access past a shut-down date? Talk to us about dedicated capacity.
Upcoming deprecations
Announcements are listed here most-recent first, each with the models or endpoints it covers and their recommended replacements.
helene-1 and
adeline-1 are current and fully supported,
and every endpoint on the
API reference is live.
For reference, when a deprecation is announced it appears in this shape, grouped under the announcement date:
Migrating
Because model selection is per-request (the
model field on
/v1/compress), migrating off a deprecated model is usually a one-line change to
the model id. If you let the proxy pick the default, migrations are
handled for you.