Eight shots, 2 to 11 s: how each Sume video model bends the plan

A storyboard with shots of 2, 3, 4, 5, 6, 7, 9 and 11 s is 47 s on Wan 3.0 ($5.88 at 720p) but 50 s on Seedance 2.5 and 11 s is out for Omni.

5 min readSume
All posts

A storyboard with shots of 2, 3, 4, 5, 6, 7, 9 and 11 seconds is 47 seconds. Wan 3.0 takes every shot as written, $5.875 at 720p. Seedance 2.5 raises the 2 s and 3 s shots to its 4 s minimum, 50 s in total, $28.89. Gemini Omni Flash 1.1 raises 2 s to 3 s and has no way to make the 11 s shot in one 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.

Clamping each shot to the model's range

Each model has a valid duration range: Wan 3.0 2 to 30 s, Seedance 2.5 4 to 30 s, Omni 3 to 10 s, MiniMax H3 Max 5 to 15 s. The table moves every shot to the nearest value inside the range (the 11 s shot on Omni becomes 10 s, which changes the edit, so treat that row as the plan you would have to rewrite).

Clamped durations and 720p price (768p for H3 Max), read 2026-10-08
ModelSeconds per shot after clampingTotal secondsPrice
Wan 3.02, 3, 4, 5, 6, 7, 9, 1147$5.875
Seedance 2.54, 4, 4, 5, 6, 7, 9, 1150$28.89
Gemini Omni Flash 1.13, 3, 4, 5, 6, 7, 9, 1047$5.875
MiniMax H3 Max5, 5, 5, 5, 6, 7, 9, 1153$5.30

Editing the plan, not the model

The clamp adds seconds on the short shots and removes them on the long. A model with a 4 s floor makes a fast-cut storyboard cost more per shot of that length; a model with a 10 s ceiling makes a long shot shorter than you wrote it. Both are cheap to fix on paper and expensive after rendering.

A practical order: list shot lengths, pick the model whose range holds them all (Wan 3.0 here), then choose the resolution. Trimming a longer clip down is available at $0.02 per job when a shot has to be shorter than the model allows.

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

Before a run, ask GET /v1/videos/models for the model and compare three fields with your plan: supported_durations (every clip length must be listed), supported_resolutions (the tier must be listed, since MiniMax H3 has 768p and no 1080p, and Omni has 360p and 4K) and supported_aspect_ratios. A request outside those lists fails at validation, so the failure costs nothing, but a plan built on a wrong assumption costs a rewrite.

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.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume