17 two-second cutaways: Wan 3.0 $4.25 vs Seedance 2.5 $39.29

Seventeen 2-second cutaways at 720p cost $4.25 on Wan 3.0 and $39.2904 on Seedance 2.5. Wan 3.0 accepts 2 to 30 seconds. Seedance 2.5 starts at 4 seconds, so each cutaway has to be requested at 4 s: you pay for 68 seconds, not 34, at a rate 4.62 times higher.

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.

The arithmetic

Wan 3.0 at 720p: 17 × 2 s = 34 s; 34 s × $0.125 = $4.25.

Seedance 2.5 at 720p: 17 × 4 s = 68 s; 68 s × $0.5778 = $39.2904.

The gap is $35.0404. Of the 9.24-fold difference in total, a factor of 2 is the floor (68 s against 34 s) and a factor of 4.62 is the rate ($0.5778 against $0.125).

When the floor is acceptable

A cutaway rarely needs a model that starts at 4 s. If you want Seedance 2.5 for its look, generate one 4 s clip and cut several cutaways out of it in the editor, or trim with the video trim job at $0.02 per job. Seventeen cutaways from nine 4 s Seedance 2.5 clips (two cutaways per clip, one spare) would cost $20.8008 plus trims, not $39.2904.

Gemini Omni Flash 1.1 is the middle case. Its floor is 3 s, so 17 cutaways are 51 s at $0.125, $6.375, with native audio on.

Scaling this plan up or down

As a yardstick, the plan above is built on Wan 3.0 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 (30 s) holds $3.75 at submit. The shortest one (2 s) holds $0.25.

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 (30 s): $3.75

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. On Wan 3.0 send duration: 2.