LLMSwaps

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

Why naming the version on the price list matters

One app prints the model name and version next to each per-second rate: Wan 3.0 at three resolutions plus two MiniMax H3 tiers, with Wan 3.0 at 480P as the default a new project gets. As of 2026-09-12.

What a named version on a price list gives a buyer that a tier name does notA comparison of a named version against an unnamed quality tier. A named version can be looked up against its maker's announcements, can be recognised in a retirement notice, and can be quoted in a record of what produced a file. A tier name supports none of the three, because the thing it points at can be replaced silently.A named versionAn unnamed tierCan you look it upYes, against the maker's own pagesThere is nothing to look upDoes a notice reach youThe name in the notice matches the nameyou boughtThe notice names something you never sawCan you record what made a fileYes, by name and versionOnly the tier, which may have changedBoth appear on price lists in this register
Fig. 1 Naming the version is what makes a retirement notice mean anything to the buyer. Without it there is nothing on the invoice to match the announcement against.
What naming a version on the priced page does for a reader watching for retirements. Recorded 2026-09-12.
EntryWhat is publishedDetail
Named model and versionRetirement visible in advanceWan 3.0, MiniMax H3
Unnamed house tierNot visible from the pageA change shows up in the output
Default tierWan 3.0 at 480PWhat a project uses without a choice

Inclusion rule. Apps whose priced pages name the underlying model. An app selling tiers without naming what runs them cannot be placed against a model calendar at all. Order. From named to unnamed.

1A named version is what makes this register possible at all

If an app sells fast and pro tiers without saying what sits underneath, there is nothing to match against a model maker's announcement. The app might be affected by a retirement and a reader has no way to tell.

That is why the register reads priced pages rather than marketing copy: the price list is where a version name, if it appears anywhere, tends to appear.

2The default tier carries more work than any other

Whatever a new project gets without anyone touching a selector is what most output is generated on. A change to that one tier reaches more work than a change to any other, which is why it is recorded separately rather than as one row among five.

This is a fact about exposure, not a quality judgement. The default is the cheapest tier here and the register makes no claim about whether it should be.

3What being able to see a retirement does not buy you

Visibility is not notice. Knowing which model sits behind a tier means a reader can connect an announcement to a product; it does not mean anyone will tell them, or that the app will keep the tier running to the model's end date.

Nothing published by this app states how much warning a tier change carries. That row is empty here and empty for every other application in the register, and the only filled versions of it belong to platforms that sell to developers rather than to productions.

  • Models carried
    Wan 3.0 at 480P, 720P and 1080P, plus MiniMax H3 and H3 Fastnamed per tierSceneMixer, price list / recorded 2026-09-12
  • Default tier
    Wan 3.0 at 480Pwhat a new project getsSceneMixer, 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: Blank dates, Who names a successor, After the date.