LLMSwaps

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

Endpoint: the door that can be closed

An endpoint is the address a request is sent to. It matters here because everything a retirement can remove arrives through one: the capability, the version, and often the library. A copy of the weights held on a production's own hardware sits outside that entirely. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryReached without oneReached withoutoneThe capability, on the seller's scheduleThe capability, on the seller's schedule — Reached without one: The capability, on hardware you runA version the seller chooses to serveA version the seller chooses to serve — Reached without one: Whichever weights you downloadedRate limits, quotas and regionsRate limits, quotas and regions — Reached without one: Whatever your own hardware allowsA retirement date, if one is publishedA retirement date, if one is published — Reached without one: No date; only a listing that may come down
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What depends on an endpoint, and what does not. Recorded 2026-09-22.
Reached through an endpointReached without one
The capability, on the seller's scheduleThe capability, on hardware you run
A version the seller chooses to serveWhichever weights you downloaded
Rate limits, quotas and regionsWhatever your own hardware allows
A retirement date, if one is publishedNo date; only a listing that may come down

Inclusion rule. Distinctions drawn from the two kinds of access in this register: hosted interfaces and published weights. Order. Hosted access first, then the alternative.

1A door is a single point of failure by design

Concentrating access behind one address is what makes a service maintainable, and it is also what makes a retirement complete. When the door closes, nothing behind it is reachable, in any region and at any price.

One platform in this register states that removal is global rather than regional, which closes the escape route multi-region customers instinctively reach for.

A door is a single point of failure by designConcentrating access behind one address is what makes a service maintainable, and it is also what makes a retirement complete. When the door closes, nothing behind it is reachable, in any region and at any price.The door closes. What is still reachable?The capabilityGoneIn every region, on theseller's date, at anyprice.Files already deliveredUntouchedUnless the product alsokept a library for you.Weights you downloadedOutside the doorA listing coming downreaches no copy alreadytaken.One entry names the exact response after its date; the rest describe nothing
Fig. 2 Output already returned sits outside the door, which is a smaller loss than it first appears and a larger one for a series.

2The status after closure is worth publishing

One entry names the exact response a request receives after its date. That lets software tell a retirement apart from a transient fault, which is the only automated warning available anywhere in this register.

Everywhere else the first evidence is a failure with no explanation, and a production learns about a date from its own output stopping.

3What the door never held

Output already returned is wherever the customer put it. So on most entries a retirement removes the ability to make more and reaches no existing file, which is a smaller loss than it first appears and a larger one for a series.

The exception is a product that kept a library. The one documented shutdown here deleted material after an export window, which the stored work column records.

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 published weights term. Nearby terms: Published weights, Inference, 410 Gone.