LLMSwaps

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

A precise price list with nothing about the work

The price list is specific about engines and silent about material. Every tier names a model and version, which makes a change detectable, and nothing on that page says whether a project keeps the model it was started on or what becomes of work already generated under it. As of 2026-09-22.

What the price list settles about work already made, and what it does not. Recorded 2026-09-22.
What the page is askedWhat SceneMixer publishesWhat that leaves open
Is disposal of material addressedNot addressed on the price listWhich is the page this register reads
Does a project keep its modelNothing states that it doesSo a swap mid-series is not ruled out
Can a change be identified laterYes, tiers name a model and a versionTwo dated readings show what moved
Is a notice period statedNothing published about warningRecorded in the notice period column too

Inclusion rule. Read from the public price list. Account or terms documents reached from elsewhere on the site are not part of this column. Order. The absence first, then what the page names instead.

1Specific about the engine, quiet about the consequences

Naming the model and version beside each rate is the most useful disclosure in the register for detecting a change. It says nothing about what a change does to a project that is already half finished.

Those are two different disclosures and only the first is here. A reader who values the first should not read it as evidence of the second, which is the mistake a specific page invites.

2Mid-series is where this column matters

A single clip does not care. A season established under one model and continued under another reads as two productions, and the question of whether an in-progress project keeps its engine is the one that decides whether that happens.

No page in this register answers it for any entry. Recording the absence per entry rather than once is deliberate: a reader arriving at a particular product should find the question asked of that product.

3What the naming does buy

It connects an announcement made by a maker to a line on a bill. When a maker publishes a date, a customer here can tell whether it applies to the tier they use, which is the link most entries break.

That is worth having and it is detection, not protection. The notice reading for this entry sets out why the two are not interchangeable.

Naming the engine connects an announcement to a billWhen a maker publishes a date, a customer on a named tier can tell whether it applies to the line they buy. Where tiers carry house labels the same announcement cannot be matched to anything, and the change arrives as output that looks different.A maker publishesA date for a namedmodel and version, onits own page.Travels downA named tierThe same model andversion appear besidea rate here.So it matchesA customerCan tell whether thedate lands on thetier they use.Where a house tier name breaks the chainNothing on the price list says a project keeps the model it was started on, which is theseparate question.
Fig. 1 Detection, which is worth having, and not protection, which is a different disclosure entirely.
  • Models carried
    Wan 3.0 at 480P, 720P and 1080P, plus MiniMax H3 and H3 Fastnamed per tierSceneMixer, price list / 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

Read from the price list on scenemixer.com, 2026-09-22. The whole entry is on SceneMixer, and the column it sits in is on Stored work. Same column, other entries: Sora, Microsoft Foundry.