Wallet reserve for a full queue of Seedance 2.5 clips, by plan

Sume reserves the estimated cost of each paid generation when it accepts the request, and returns 402 insufficient_credits if the balance cannot cover it. For 5-second Seedance 2.5 clips at 720p 9:16 ($2.889 each) a full accepted queue reserves $17.33 on Free (6 jobs), $69.34 on Pro (24), $138.67 on Startup (48) and $346.68 on Scale (120).

Reserve by plan

Per-second figures are the provider list rate times the 1.25 Sume margin that the docs describe, as of 2026-10-08. Read capabilities from GET /v1/video-router/models before you bill a batch, because rates and envelopes can change.

Arithmetic

Seedance 2.5 at 720p 9:16 is 21,600 tokens per second. Five seconds is 108,000 tokens. At $0.0214 per 1000 tokens that is $2.3112 list, and x 1.25 gives $2.889.

• Failed jobs and failed queue admission release the reservation.
• Success captures it.
• The reserve is an estimate; read usage.cost on the result for the billed amount.

What to do

Keep a balance equal to the reserve for the wave, not the whole catalog. A 1,200-clip catalog on Scale at $2.889 would total $3,466.80, but only 120 jobs are accepted at once, so the reserve at any time is $346.68.

A balance check

Before a run, compute wave size x per-job price and compare with your balance. For a Pro wave of 18 at $2.889, that is $52.00. If the balance is $50, the last jobs will return 402 insufficient_credits, and the earlier ones remain accepted.

Top up through your plan's included Gen$ or submit cheaper requests; the docs say not to invent prepaid top-ups.

• 18 x $2.889 = $52.00.
• Failed admissions release the reservation.
• Re-submit with the same Idempotency-Key after the balance is fixed.

Before you scale

These figures are reserves, not charges. On success the reserved usage is captured, and on failure it is released, so the balance you need is the largest outstanding wave, not the sum of the catalog. For a 1,200-clip run on Pro, that means $69.34 at a time rather than the $3,466.80 total, as long as you submit in waves and let earlier jobs finish.