40 micro-drama episodes of 60 seconds on Wan 3.0: $150 at 480p

Forty 60-second micro-drama episodes are two 30-second Wan 3.0 jobs each: $150.00 at 480p, $300.00 at 720p and $600.00 at 1080p on Sume.

5 min readSume
All posts

Forty 60-second micro-drama episodes cost $150.00 at 480p, $300.00 at 720p and $600.00 at 1080p on Wan 3.0, because a minute is two 30-second jobs. That is 80 jobs and 2,400 seconds of generation.

Season cost

Sume bills the provider list rate multiplied by 1.25 on every video model (Video Router). The figures here come from the price estimators in Sume's repository, run on 2026-10-07, and are rounded to the cent. The live numbers for your workspace are in the catalog response and on the API pricing page.

YouTube's Shorts series help page says episodes can be up to 180 seconds, vertical or square (YouTube Help, read 2026-10-07), so 60-second episodes are comfortably inside the limit.

60-second episodes on Wan 3.0 on Sume (read 2026-10-07)
ResolutionOne episode (2 jobs)40 episodesJobs
480p$3.75$150.0080
720p$7.50$300.0080
1080p$15.00$600.0080

What the plan misses

The figures are generation only. Voice, captions and the join are separate line items on the API pricing page; captions are a flat charge per video up to 60 seconds, so a 60-second episode fits in one. Add them to your per-episode cost before you quote a season.

Allow retakes. With one episode in four needing a rerun of one 30-second half, 40 episodes cost about $168.75 at 480p.

  • Use the same character reference across all 80 jobs.
  • Submit one episode as a pair, then check the seam, before queueing the season.
  • Keep the aspect ratio at 9:16 for the whole season.

Waves and holds

Sume reserves the estimated amount when it accepts a job, captures it on success, and refunds the reservation if the job fails or is cancelled before capture (Usage, Generation admission). So the balance you need on hand at submit time is the price of everything in flight, not only the final total.

A Pro workspace runs 4 jobs at once, Startup 8 and Scale 20 (the plans page lists the ladder), so a big batch drains in waves rather than all at once.

Set a cap before you start: from MCP, a paid tool takes dry_run=true and max_spend_usd (MCP tools and gates). Send a distinct Idempotency-Key per job so a retry replays the original job instead of charging again.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume