A price list where nothing runs unasked
Models are priced individually rather than bundled into a plan, and a call names the model it wants. So there is no default to publish: nothing runs unless somebody named it. The column records that as an absence of the concept rather than as an unanswered question. As of 2026-09-22.
| What the page is asked | What fal publishes | What that leaves open |
|---|---|---|
| Is a starting tier stated | Not applicable, each call names a model | Nothing generates without being asked |
| How are the models priced | Individually, per second or per video | So no bundle implies a starting line |
| Could a plan default appear later | Nothing on the page describes a plan | The unit is the model, not a subscription |
| What replaces the default risk | Whatever your own code names | Which is a pin you control, or an alias |
Inclusion rule. Filled when the entry's own public page says which model a new project starts on, or when a single-model menu makes the answer follow from the list having one line. Order. What does not apply first, then what stands in its place.
1The concept does not survive per-model pricing
A default exists because a product has to do something when nobody chooses. Where every call names a model and every model carries its own price, there is no such moment, so the question dissolves rather than going unanswered.
Recording that distinctly matters. A reader comparing blank cells across this column would otherwise treat the clearest arrangement as one more silence.
2The risk moves into the caller's own code
Whatever string a production puts in its requests is its effective default, and it will keep using it until somebody edits it. That is a pin the customer controls, which is stronger than any arrangement a page could offer.
It is also a responsibility. A hard-coded identifier that stops being served fails on the maker's date, and nobody will change it on the production's behalf.
3Per-model prices make the bookkeeping fall out for free
Because each model bills separately, the invoice already records which engine produced what. That is the record this register keeps recommending, and here it is a by-product of how the meter works.
Most entries make the same connection impossible to reconstruct. The stored work reading for this entry describes the other side of the same arrangement.
- How the meter worksVideo models are billed by output unit, per second or per video depending on the modelquoted from the page
4Sources
Read from the pricing page on fal.ai, 2026-09-22. The whole entry is on fal, and the column it sits in is on Default tier. Same column, other entries: Microsoft Foundry, Amazon Bedrock.