LLMSwaps

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

Who reserves the right to change the menu

One application's pricing page reserves the right to update, modify or change the models it offers. It is the only such clause among the applications here, and not one of them publishes how much notice a change would carry. As of 2026-09-12.

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 entryWhat is publishedLTX StudioLTX Studio — What is published: A published clauseEvery other appEvery other app — What is published: No clause publishedNotice periodNotice period — What is published: Published by nobody
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What each app publishes about its right to change the models it carries. Recorded 2026-09-12.
EntryWhat is publishedDetail
LTX StudioA published clauseReserves the right to update or change models
Every other appNo clause publishedSilent on whether the menu can change
Notice periodPublished by nobodyNo app states how much warning it would give

Inclusion rule. Clauses appearing on the pages a buyer reads before paying. Terms of service are not read for this register. Order. Apps publishing a clause first.

1A clause that says the menu can change is more honest than silence

Every app here can change what it carries; one of them says so on the page where it takes money. That is not a worse position than the silent ones, it is a disclosed version of the same position, and a reader who treats the clause as a red flag has the comparison backwards.

This register records it as published rather than as good or bad. What it buys the reader is a sentence to point at when asking what the notice period would be.

2Nobody publishes the number that would make the clause useful

Reserving the right to change is one half. How much warning comes with the change is the other, and not one application in this register publishes it. The clause and the silence together describe a right with no stated constraint on how it is exercised. Platforms selling the same models to developers do state a constraint, which is covered on the notice period field page.

The one vendor-side retirement observed here gave about five months. That is a model maker's behaviour rather than an app's commitment, and nothing connects the two.

3What a production can do with this today

Ask, in writing, before committing a series. The published material supports exactly one question with a clear answer, which is whether the app claims the right to change; everything after that has to come from the vendor directly.

That is a thin result and it is the accurate one. A register that implied more would be manufacturing reassurance out of a single clause.

  • Published notice
    The pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any specific modelthe only one of its kind hereLTX Studio, pricing / recorded 2026-09-12
  • Notice before a tier changes
    No date announced (as of 2026-09-12)nothing publishedSceneMixer, price list / 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: Aggregators, One or many, Naming versions.