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.
| Reached through an endpoint | Reached without one |
|---|---|
| The capability, on the seller's schedule | The capability, on hardware you run |
| A version the seller chooses to serve | Whichever weights you downloaded |
| Rate limits, quotas and regions | Whatever your own hardware allows |
| A retirement date, if one is published | No 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.
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.
4A pipeline across model versions
Model end dates touch “Endpoint”; SceneMixer's guides describe how its pipeline treats the models it runs:
The Seedance 2.0 tiers render segments up to 15 seconds; use a Seedance 2.5 or Wan tier for 30-second takes.
SceneMixer, Seedance 2.0 Fast — “Does Fast render 30-second takes?” (read 2026-10-13)
Voices and ambience are in the clip, and in the composited episode, with the episode’s score unless you turned the Music switch off.
SceneMixer, Dialogue and Sound in One Generation — “Does the downloaded file include the sound?” (read 2026-10-13)