37 Wan 3.0 clips of 17 s: $39.31 at 480p, $157.25 at 1080p

Thirty-seven Wan 3.0 clips of 17 seconds each cost $39.3125 at 480p, $78.625 at 720p and $157.25 at 1080p on Sume. That is 37 x 17 = 629 output seconds multiplied by the per-second rate. The rates are fixed per second, so the total moves in a straight line with both clip count and clip length.

The numbers below use the Sume list rates for wan-3.0 as of 2026-10-09 and the 2-30 second duration window documented on the Video API page. A 17-second clip sits inside that window, so no rounding or padding applies. If you change the clip length, rerun the multiplication: 20-second clips would put the same batch at 740 seconds.

The price ladder

Each row multiplies the per-second rate by 17 for one clip, then by 37 for the batch.

Draft cheap, finalize the winners

Resolution is the only lever in the table, and the 480p to 1080p gap is a factor of four. A common plan is to generate every concept at 480p, pick the ones worth keeping, and regenerate only those at 1080p. With 37 drafts at 480p ($39.3125) and 5 finals at 1080p (5 x 17 x $0.25 = $21.25), the project costs $60.5625 instead of $157.25 for 37 clips at 1080p.

This only works if a regenerated clip resembles the draft closely enough to judge from it. The video API does not accept a seed for any v1 model, so a second run is a new sample, not a re-render of the first. Treat the 480p pass as a screen for prompts, not as a preview of the exact final frames.

What the wallet must hold

At submit Sume reserves the estimated cost of each accepted job, and a successful completion captures it. If the balance cannot cover the reservation, the submit fails with 402 insufficient_credits before provider work starts. For a batch, the balance has to cover every job that is accepted and not yet finished, not only the first.

Concurrency adds a second ceiling. Accepted job capacity is the processing limit plus the queue: 6 on Free, 24 on Pro, 48 on Startup and 120 on Scale. A 37-job batch fits in one submit pass on Startup or Scale. On Pro it needs two waves (24, then 13), and on Free it needs seven. A job past capacity gets 429 queue_full, which is not a charge.

• 480p reservation per 17 s clip: $1.0625
• 720p reservation per 17 s clip: $2.125
• 1080p reservation per 17 s clip: $4.25
• Pro, 24 jobs at 1080p in flight: 24 x $4.25 = $102.00 held at once

Where to confirm the rate

The live per-model numbers come from GET /v1/videos/models and from the public catalog, so check the response before you budget a large batch. Rates on this page were read on 2026-10-09 and can change; the structure (per-second, linear inside the duration window) is what the docs commit to.

Reading the total as a unit cost

Dividing the batch back down gives the figure to quote to a client: $1.0625 a clip at 480p, $2.125 at 720p, $4.25 at 1080p. Add the number of attempts you expect per accepted clip. If two takes in three are discarded, the effective cost per kept 1080p clip is 3 x $4.25 / 2, or $6.375, and the 37-clip order really consumes about 55 generated clips. The ledger records every attempt, so the figure to track is debited_usd_micros for the project, not the price of the final cut alone.