Naming a model every time against having one

Neither entry has a default and the reasons are opposite. On one, every call names a model from a list where each line carries its own price, so nothing runs unasked. On the other, one house model appears on every plan, so there is nothing to choose between. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

Why neither entry has a default, and what that means. Recorded 2026-09-22.
On this point	fal	Pika
Number of purchasable models	Several, each with its own price	One, across every plan
What a request names	The model, every time	Nothing; there is one engine
Where variation lives	In the choice of model	In resolution and features
What a version change reaches	Only callers naming that model	Every plan simultaneously
Is the engine identifiable later	Yes, from the invoice	By name, though not by version

Inclusion rule. Both cells on a row come from the entry's own priced pages. A model named in marketing but absent from every priced page does not count. Order. Number of models first, then what varies instead.

1Two kinds of nothing to default to

One entry has no default because choice is compulsory. The other has none because choice is impossible. A reader scanning for empty cells would treat those as the same finding, and they produce completely different exposures.

Compulsory choice spreads risk across whichever models a production named. No choice concentrates it on one line that everybody shares.

Fig. 1 Compulsory choice spreads risk across the models a production named; no choice concentrates it on one shared line.

2Per-model billing records what a bundle hides

Where each model carries its own price, the invoice already says which engine produced what. On a single-model plan the engine is known by name and not by version, so a silent update leaves no trace on any document.

That makes the first entry easier to audit after the fact. The register keeps recommending exactly that record, and here it falls out of the billing arrangement.

3Blast radius differs by an order

A version change on a per-model list affects the callers who named that model. On a single-line menu it affects everybody on the same day, and there is no older generation listed to finish a season on.

Both entries publish no date and no successor. The succession reading for the single-line entry sets out what having nothing behind it means.

4The same question, put to a third entry

What SceneMixer publishes on this column, beside fal and Pika. Recorded 2026-10-13.
On this point	SceneMixer	Source
The default tier	Wan 3.0 at 480P	SceneMixer, price list
When a tier is withdrawn	When a tier is withdrawn, text and image work falls back to the default tier and video to the tier the episode last used if it is still listed, otherwise the default; the price shown is the tier that will run	SceneMixer, withdrawn tier guide

Inclusion rule. SceneMixer's own statements that bear on the column this pair was chosen for. Order. The statement closest to the column first.

All of its readings are on the SceneMixer entry.

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
Pika 2.5 onlyin house onlyPika, pricing / recorded 2026-09-12

5Sources

Both readings come from the pages the entries publish themselves: fal and Pika, read 2026-09-22. The column being compared is Default tier. Other pairs: Runway and SceneMixer, Runway and Luma.