LLMSwaps

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

Where each model carries its own price

Three entries attach a price to each named model rather than bundling them into a plan: one prices per output unit, one converts credits per model, and one prices seconds per named tier. On all three, the bill records which engine produced what. As of 2026-09-12.

Where a price attaches to a named model rather than to a plan. Recorded 2026-09-12.
EntryWhat is publishedDetail
falA price per model, per second or per clipNothing runs unless a call names it
RunwayCredits converted per modelA rate and a retirement look alike on the page
SceneMixerSeconds priced per named tierEach tier naming a model and a version
Adobe FireflyPartner models named per plan tierA tier price, not a per-model one
Every other entryA plan covering several modelsNo per-model figure published

Inclusion rule. An entry appears when its own priced page attaches a figure to a named model or a named tier carrying one. A plan price covering several unnamed models does not count. Order. Entries pricing per model first, then per tier, then the rest.

1Per-model pricing produces the record for free

Every explainer on this site ends by recommending a per-file note of which model produced what. Where each model carries its own price, the invoice already says it, and the habit becomes unnecessary.

On a bundled subscription the same connection cannot be reconstructed afterwards. That is the single most useful practical difference between these arrangements.

The per-file record, produced by the billingEvery explainer on this site recommends noting which model produced which file. Where each model carries its own price, the invoice already says it, and on a bundled subscription the same connection cannot be reconstructed.Per modelA price attaches to anamed engine. Theinvoice records it.So laterPer creditA conversion attachesto a named engine,and a credit is theunit.OrPer planSeveral engines, oneprice, and nothingrecording which ran.From the most legible arrangement to the leastNaming the engine and identifying the starting one are two separate disclosures.
Fig. 1 The single most useful practical difference between these pricing arrangements.

2A credit sits between the customer and the model

Where the unit is a credit, a change to what it buys and a change to which models exist look similar on the page. That is convenient commercially and it blurs the distinction this register cares about.

A production there has to record both the model name and the conversion rate, because either one moving invalidates a plan built on the other.

3Naming the engine is separate from naming the price

An entry can publish a complete price list and still not say which engine an untouched project runs on. Two things are being disclosed and having one is not evidence about the other.

The default reading for the credit table sets out exactly that combination: every model named, and none identified as the starting one.

  • How the meter works
    Video models are billed by output unit, per second or per video depending on the modelquoted from the pagefal, pricing page / recorded 2026-09-22
  • Models carried
    Wan 2.5, Kling 2.5 Turbo Pro, Veo 3 and Ovi, each priced individuallypriced per model rather than per planfal, pricing page / recorded 2026-09-22
  • Models carried
    Gen-4.5 and Aleph 2.0 in house, plus Kling 3.0 and three Seedance variantsnamed beside credit conversionsRunway, pricing page / recorded 2026-09-22
  • Models carried
    Wan 3.0 at 480P, 720P and 1080P, plus MiniMax H3 and H3 Fastnamed per tierSceneMixer, 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: House against licensed, Downloadable weights, Tier and model.