60 ten-second Wan 3.0 clips a week: waves and reserve by Sume plan

Sixty 10-second Wan 3.0 clips at 720p cost $75.00 a week on Sume ($1.25 each). Pro accepts 24 jobs at a time, so submit them in three waves of 24, 24 and 12; Startup takes two waves; Scale takes all 60 at once. Each submitted job reserves its estimated price immediately.

Waves by plan

Accepted jobs are concurrency plus queue: Pro 4 plus 20, Startup 8 plus 40, Scale 20 plus 100. A submit beyond that is rejected with 429 queue_full, so the next wave waits for jobs to finish.

Money while it runs

The first Pro wave reserves $30.00 at submit. That is under Pro's $40 of included usage, so it fits. A second wave in the same month would need the first to capture and the balance to cover it. If balance is short, the submit fails with 402 insufficient_credits before any work starts.

Monthly usage for four such weeks is $300.00: $300 on Pro, $280 on Startup, and $400 on Scale.

What to do

On Pro, script the waves: submit 24, wait for completions, submit the next. On Startup, do 48 then 12. Scale is the only plan that takes the whole week at once, at a higher cost per month for this workload. See 48 jobs on Startup for the same pattern, and how the reserve works.

One practical wrinkle is that a reserve is taken for every accepted job, including queued ones, so a full Pro wave holds $30.00 of balance even though only 4 jobs are running. If your balance is $35 and you submit a second wave while the first is still reserved, the later jobs can be refused with a 402. Waiting for completions frees capacity as well as balance, since a completed job captures its price.

Check the 10-second length against the model page before you script a batch. Wan 3.0 takes 2 to 30 seconds a job, so 10 seconds is inside the range, and a single job costs $1.25 at 720p, $0.63 at 480p and $2.50 at 1080p. Splitting the week across two days is also an option if you do not need everything at once, and it lowers the amount held in reserve at any moment.