Which entries are model cards, not products
Two entries in this register are model cards for open weights rather than product pages. They publish what the released model does: exact pixel sizes, frame counts, frame rates and divisibility rules. They publish no price, no tier and no shape. As of 2026-09-22.
| Item | What is published | Detail |
|---|---|---|
| What they do publish | Pixels, frames, rates, divisors | The quantities someone running inference budgets |
| What they do not publish | Price, tiers, shapes | The columns a buyer usually reads first |
| Where they sit in this register | Two of fifteen entries | Both fill the frame rate column |
Inclusion rule. Entries read from a model card published by the organisation that released the weights. A hosted service reselling the same weights would be a separate entry read from its own page. Order. What is published first, then what is not.
1A card answers an operator's questions, not a buyer's
Frames divisible by eight plus one, resolutions divisible by thirty-two, eight frames a second, forty-nine frames: these are the numbers that matter to someone fitting a job into memory on their own hardware.
A media buyer reads none of them first. What a buyer wants is a length in seconds, a shape, a tier and a price, and a card supplies the first only by arithmetic and the other three not at all.
2The cards fill the column no product page does
Both model cards publish a frame rate, and the only other entry that does is a vendor user guide. No rate card and no API reference in this register mentions one.
That is because a rate is not billed and is rarely a parameter. On a card it is unavoidable, because the frame count is the quantity being described, and the rate is how that count becomes a duration.
3Neither card should be read as a product limit
Hosted services run these weights with their own parameters, quotas and prices. An entry in this register records the page it names, so a card's figures describe the released model and not every service built on it.
Where a hosted version publishes its own page, it would be its own entry with its own check date. The register does not merge the two, because a card and a rate card are not making the same kind of promise.
- Frame rate8 frames per secondfrom the model card table
- Shapes and lengths the model acceptsResolutions that are divisible by 32 and number of frames that are divisible by 8 + 1
- Inference resolution720 x 480, no support for other resolutionsfrom the model card table
4From brief to placement
For ad work around “Cards, not products”, SceneMixer's pages explain how its ad projects are produced:
The final cut ends on an end card: your main image plus four lines — Brand, Product name, Tagline, Call to action. The first two are read from your photo and your brief; the tagline and call to action are written with the script.
SceneMixer, The End Card (read 2026-10-13)
Episode 1 opens on the conflict within 5 seconds, establishes the lead's situation and what she wants, and ends on an identity hook.
SceneMixer, Vertical Short Drama Script Format (2026): Episode Length, Word Counts, Hook Structure and AI-Generation Constraints — “What has to happen in the first three episodes?” (read 2026-10-13)
5Sources
Format requirements come from Google Ads Help, read 2026-09-12, and tool limits from each vendor page listed on published limits, read 2026-09-22. The rule against mixing the two is on method. Nearby: Thirty seconds in calls, Who publishes a minimum, Ad lengths.