27-second continuous shot: Wan 3.0 $6.75 vs three 9 s Omni jobs $5.06

A 27-second shot at 1080p is $6.75 on Wan 3.0 and $38.38185 on Seedance 2.5, one job each. Gemini Omni Flash 1.1 stops at 10 s, so 27 s is three 9-second jobs at $5.0625, with two joins.

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.

Tiers for a single 27-second job

Only Wan 3.0 and Seedance 2.5 accept more than 15 s (up to 30 s). So a continuous 27 s shot is a choice between those two.

Why continuity costs

The cheaper Omni path is three clips with two cuts. If the cut is hidden by a scene change, that is the cheapest 1080p route per second in the set. If the camera must not cut, you need one job, and Wan 3.0 at $6.75 is a sixth of Seedance 2.5 at the same resolution, a ratio of 5.69.

The figure to watch is the leftover headroom: 27 s is 3 s under the 30 s maximum, so a re-roll costs the same 27 s again.

Scaling this plan up or down

As a yardstick, the plan above is built on Wan 3.0 at 1080p, $0.25 per second. Each extra 5 seconds adds $1.25, a further $10 of budget buys 40 more whole seconds, and the largest single job the model accepts (30 s) holds $7.50 at submit. The shortest one (2 s) holds $0.50.

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.25
• Per 5 s: $1.25
• Per 10 s: $2.50
• Per 30 s or the model maximum (30 s): $7.50

Check the model's fields first

After the first job completes, read usage.cost on the poll response and compare it with the figure in this post. They should agree, because both are the provider list price times 1.25. If your number differs, the usual cause is a different tier or duration than you planned, not a price change; the public catalog at https://api.sume.com/v1/catalog shows the current rates and needs no key.

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.