23-second hero shot: the 720p to 1080p step costs $2.88 or $19.41

Raising a 23-second hero shot from 720p to 1080p adds $2.875 on Wan 3.0 ($2.875 to $5.75) and $19.40625 on Seedance 2.5 ($13.2894 to $32.69565). Both models accept 23 s in a single job.

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 three tiers

Twenty-three seconds is long for a shot, so the resolution step is multiplied by many seconds. The table shows all three tiers; the step columns are the extra paid for each move up.

Deciding on the step

The step is paid for the whole clip, even if only part of it is a close-up. If only 6 seconds need 1080p, it is cheaper to generate the 23 s at 720p and a separate 6 s close-up at 1080p: on Wan 3.0 $4.375 in total, against $5.75 for all 1080p. On Seedance 2.5 the same split is $21.8187 against $32.69565.

The caveat is consistency: two renders of one scene differ, so a split suits shots where the close-up is a different angle.

Scaling this plan up or down

As a yardstick, the plan above is built on Seedance 2.5 at 1080p, $1.42155 per second. Each extra 5 seconds adds $7.10775, a further $10 of budget buys 7 more whole seconds, and the largest single job the model accepts (30 s) holds $42.6465 at submit. The shortest one (4 s) holds $5.6862.

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: $1.42155
• Per 5 s: $7.10775
• Per 10 s: $14.2155
• Per 30 s or the model maximum (30 s): $42.6465

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.