An 80-cent cap per clip: longest Sume video each model and tier allows

With an 80-cent ceiling per clip, Wan 3.0 and MiniMax H3 at 480p reach 12 s, and Gemini Omni Flash 1.1 at 360p reaches its 10-second maximum for $0.375. Seedance 2.5 at 1080p cannot run at all: its 4-second minimum already costs more than $0.80. This page works out the longest clip each Sume video row allows under that cap.

The rule is simple. Sume reserves the full clip price at submit, so a per-clip cap is the same as a ceiling on rate times seconds. Take the cap, divide by the per-second rate, round down, then clip the result to the model's maximum. If the result is below the model's minimum, the row is out.

The table

All rates are USD per output second, provider list times 1.25, default options, read 2026-10-09. The longest clip is the smaller of the model maximum and the whole seconds that fit in $0.80. The bracket shows the resulting clip price.

Reading the gaps

Two things stand out. First, the cheap rows hit their duration ceilings before the cap: Omni at 360p stops at 10 s because that is its maximum, and the cap leaves $0.80 - $0.375 = $0.425 unspent. Second, a row can fit the cap and still fail the minimum: MiniMax H3 at 768p fits 10 s ($0.75), but Seedance 2.0 at 720p fits only 2 s, which is under its 4-second minimum, so the row reads none.

If your cap is a safety limit rather than a price target, remember the second guard: Sume answers 402 insufficient_credits when the workspace balance cannot cover the reservation, which is a separate check from any cap you impose in your own code.

Putting the cap in code

Enforce the cap before you submit. Look up the rate for the model and resolution in the catalog, multiply by the duration you intend to send, and refuse the call locally if the product is above the cap. The model's supported_durations field from GET /v1/videos/models tells you whether the duration you have left is legal.