A priced page and a reference promise differently
Specification figures come from documents written for different readers. A priced page exists to answer what something costs. A reference exists to answer what a field will take. The columns each one fills follow from that, and so do the gaps. As of 2026-09-12.
| Kind of page | The question it answers | What it reliably omits |
|---|---|---|
| A priced page | What does a request cost | Anything that does not change the rate |
| An API reference | What will this field accept | What any of it costs |
| A usage limits page | What will be refused | What is offered inside the limits |
| A model card | What do these weights produce | Price, tiers and shapes |
Inclusion rule. Kinds of source page a specification figure is commonly read from. A blog post or launch announcement is not a specification page and is not listed. Order. Most commonly cited kind first.
1A rate card prints what varies with the rate
Resolution is almost always on a priced page, because each step usually carries a different charge. Length is sometimes there and shape almost never, because neither reliably changes what a request costs.
So a rate card can leave a buyer able to price a request and unable to schedule one. That is not an oversight; it is the page doing its job, and a register has to record which job the page was doing.
2A reference prints the conditions as well as the values
Because a reference describes fields, it also describes what makes a field behave differently: a model identifier, a version string, a tier that unlocks or blocks a value. Those conditions rarely appear on priced pages at all.
The conditions are often the more useful half. A range with a precondition is a different fact from a plain range, and only the document that exists to describe fields tends to mention it.
3Neither document type is more trustworthy
The instinct to prefer one is a mistake. A priced page is what a buyer is held to when an invoice arrives; a reference is what a request is held to when it is submitted. Both are binding on the thing they describe.
What matters is not mixing them inside one cell. A length from a reference and a rate from a priced page can sit in the same row as long as each says where it came from, and they cannot be averaged into a single verdict about the vendor.
A craft note, not a spec. Nothing here is taken from a platform or a vendor, and nothing here should be quoted as a requirement. The sourced material is on published limits. Related: Rounding up a call count, Pairs and ratio names.
4Making the ad itself
For ad work around “Rate cards and references”, SceneMixer's pages explain how its ad projects are produced:
The script is written from the photos and the one-line description. In step-by-step mode you can rewrite it before anything is shot.
SceneMixer, How to Make an Ad from One Photo — “Do I need a script?” (read 2026-10-13)
The music runs across the end card and comes to an end with the film.
SceneMixer, Where the Music in an Ad Video Comes From — “Does the end card have music?” (read 2026-10-13)