How many 10-second 1080p jobs can a $37 balance submit on Sume?

A $37 balance can submit 2 Seedance 2.5, 4 Seedance 2.0, 14 Wan 3.0, 18 MiniMax H3 Max or 19 Gemini Omni Flash 1.1 jobs of 10 seconds at 1080p before the next submit would fail the balance check. The docs say that at submit Sume reserves provider list × 1.25, so a job holds its full price from the moment you send it.

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 count

The count is the whole number of jobs whose combined price is at most $37, with each job at 10 s × the 1080p rate.

What it means in practice

The reserve means a fan-out of many jobs needs the balance for all of them up front, not only for the ones that finish. If the sixth Wan 3.0 job is a re-roll, it still needs $2.50 free at submit.

MiniMax H3 (no 1080p tier) is left out, since its top native tier is 768p. Mixed queues can be sized the same way: add the per-job prices of the jobs you intend to hold at once.

• Seedance 2.5, 2 jobs: 2 × $14.2155 = $28.431; a third would hold $42.6465.
• Wan 3.0, 14 jobs: 14 × $2.50 = $35.00; a fifteenth would hold $37.50.

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

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. Send an Idempotency-Key so a retry of a timed-out submit returns the original job instead of holding the price twice.