LLMSwaps

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

An aggregator inherits somebody else's calendar

Two apps here carry models made by other companies: one aggregates six makers, the other mixes two house generations with licensed Veo. Every licensed line on those menus runs on a schedule the app does not control. As of 2026-09-12.

Where the retirement dates behind one aggregated menu actually come fromSeveral model makers feeding one app menu. Each licensed line on the menu runs on a schedule set by the company that makes it, not by the app. A house generation is the only line whose calendar the app itself controls, so mixing the two splits the exposure rather than removing it.Licensed lineAnother makerTheir scheduleYou learn from their pageLicensed lineAnother makerTheir scheduleYou learn from their pageHouse lineThe app itselfIts own scheduleThe app can tell youdirectlyOne menu the buyer seesWhere a withdrawal would be announced
Fig. 1 One menu, several calendars. Every line an app licenses rather than makes is a date somebody else gets to choose.
Whose retirement calendar each app is exposed to. Recorded 2026-09-12.
EntryWhat is publishedDetail
invideo AISix makers aggregatedVeo, Sora 2, Kling, Wan, Pixverse and others
LTX StudioTwo house plus licensedLTX-2.5 and 2.3 in house, Veo 3.1 licensed
Single-maker appsOne scheduleHouse models only

Inclusion rule. Apps are read from the page naming what they carry. A model named on a priced page counts; a model shown in a launch post does not. Order. By how many makers' schedules the app carries.

1Six makers is six calendars and none of them is yours

An app carrying one house model has one schedule and controls it. An app aggregating six has six, controls none, and will usually learn about a retirement at roughly the same time its customers do. Neither arrangement is better; they fail differently and they should be planned for differently.

The aggregator's advantage is real too: when one maker retires a model, five others are still there. A single-model app has nothing to fall back to.

2Sora 2 is still on one of these menus

The one model in this register with an announced end date appears on an aggregator's list. That is not an error on anyone's part: the API runs until its end date and the app is entitled to sell access to it until then.

It is the clearest illustration of why this register keeps app menus and model dates on separate pages. They go out of step by design, and the gap between them is exactly what a production needs to see.

3Mixing house and licensed models splits the exposure

One app here does both: models it makes and a model it licenses. The house lines carry the app's own schedule, the licensed line carries somebody else's, and nothing on the page marks which is which for a reader who does not already know.

This register records the composition because that distinction determines who a production would have to ask when a line disappears.

  • Models carried
    Google Veo 3.1, Sora 2, Kling AI, Wan AI, Pixverse AI and Hailuo AIaggregatedinvideo AI, model list / recorded 2026-09-12
  • Models carried
    LTX-2.5 and LTX-2.3 in house, plus Veo 3.1 in three variants and Kling 2.6 Pro and 3.0 Prolicensed models includedLTX Studio, pricing / recorded 2026-09-12

4Sources

Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: One or many, Naming versions, Blank dates.