7 hooks in 9:16 and 16:9, 6 s each: 84 seconds of video by model

Seven hooks, each 6 seconds in 9:16 and 16:9, are 14 clips and 84 seconds. At 720p that is $10.50 on Wan 3.0, $10.50 on Gemini Omni Flash 1.1 and $48.5352 on Seedance 2.5.

Prices on this page are Sume list prices as of 2026-10-08: the provider list price times 1.25, computed from Sume's pricing package and billed per output second, linear in duration inside each model's valid range. The model ids, ranges and input types come from the Video generation docs and the Video Router docs; the per-second numbers can be cross-checked in the public catalog.

Which models take both ratios

Gemini Omni Flash 1.1 accepts exactly two ratios, 16:9 and 9:16, so it covers this plan with no cropping. Seedance 2.0 lists 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. For any other model read supported_aspect_ratios before you budget, because a model that rejects a ratio forces a crop or a model switch.

A hook rendered separately in each ratio is a new composition, not a crop, which is the point of paying for 14 clips rather than 7.

Testing before the full run

Hooks are tested in public before they are scaled, so there is a case for two passes: draft all 14 at the lowest tier, then re-render the winners. Seven winners rendered again at 1080p on Omni in 9:16 only cost $7.875 (42 s × $0.1875), on top of the $3.15 for the 360p drafts.

Scaling this plan up or down

As a yardstick, the plan above is built on Gemini Omni Flash 1.1 at 720p, $0.125 per second. Each extra 5 seconds adds $0.625, a further $10 of budget buys 80 more whole seconds, and the largest single job the model accepts (10 s) holds $1.25 at submit. The shortest one (3 s) holds $0.375.

Those three numbers are enough to rescale the plan without a new table. If the plan doubles, double the totals; if a clip is shortened, subtract the seconds multiplied by the rate; and if the tier changes, swap the rate for the one in the tables above.

• Per second: $0.125
• Per 5 s: $0.625
• Per 10 s: $1.25
• Per 30 s or the model maximum (10 s): $1.25

Check the model's fields first

Put the price table in your own config and compute the total before you call the API. The price is linear in seconds inside a model's range, so a function of rate and duration is enough, and it lets you refuse a batch that goes over a ceiling. Re-read the catalog when you plan a large run, because list prices are what Sume bills from, and they can change.

Submitting

Submit through POST /v1/videos with model, prompt, duration in whole seconds and resolution; read GET /v1/videos/models first, because supported_durations and supported_resolutions differ per model. Sume reserves the price at submit and usage.cost on the poll response is the billable amount, so the figures here are what leaves the balance. Pass aspect_ratio as 9:16 or 16:9.