LLMSwaps

Which model each app runs today, and when it last changed

Tier gating: losing a model without a retirement

Tier gating names models per plan tier, so what a project can reach follows from the subscription. It makes the mapping readable before paying, and it creates a second way to lose a model: the tier moves, the model continues to exist, and no lifecycle page is involved. As of 2026-09-22.

Two ways to lose access, and which one a tracker sees. Recorded 2026-09-22.
A retirementA tier change
Decided byThe maker
Announced inA lifecycle notice, sometimes
The model afterwardsGone
Appears on a calendarSometimes

Inclusion rule. Read from the published plan comparison of the one entry in this register that names partner models against tiers. Order. Paired, with the retirement column first.

1Publishing the mapping is what makes it legible

Naming which model sits in which plan is more detail than most entries give, and it is the reason this mechanism can be described at all. A reader can see exactly which subscription reaches which engine before paying anything.

It is a snapshot of a commercial arrangement rather than a commitment. Nothing says a model stays in the tier it is named in, and the mapping is the element most likely to move.

2The effect is identical and the paperwork is not

From a production's side, losing an engine because the tier moved and losing it because it was retired are the same event. A retirement tends to produce a dated notice somewhere; a restructure produces a new pricing page.

No retirement tracker watches pricing pages, including this one. The register records the mapping and the date it was read, which is the only handle available.

Two ways to lose an engine, and which one a tracker seesFrom a production's side, losing an engine because the tier moved and losing it because it was retired are the same event. A retirement tends to produce a dated notice; a restructure produces a new pricing page.The model your plan named is no longer available to you. Why?The maker retired itA retirementThere may be a dated notice somewhereupstream to read.The tier mapping movedA pricing eventNo notice, no date, and the model stillexists one plan up.A gate is also a kind of stability: the reachable set is fixed at purchase
Fig. 1 No retirement tracker watches pricing pages, including this one.

3A gate is also a kind of stability

Because the reachable set is fixed at purchase, it does not drift between sessions. That is more durable than an unstated default setting, which most entries in this register have instead.

The gate read against a single-line menu sets out what each arrangement fixes and who can move it.

A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on the reading on that mechanism. Nearby terms: Default engine, Announced date, Blank cell.