Season finale of 3 minutes: six Wan 3.0 jobs and a timeline, $22.80
A 3-minute finale is six 30-second Wan 3.0 jobs at 720p ($3.75 each) plus a $0.30 Timeline render: $22.80 before audio work. Here is the plan and the seams.

A three-minute season finale on Wan 3.0 is six 30-second jobs, because Wan 3.0 accepts 2 to 30 seconds per job. At 720p Sume bills $0.125 a second, so each job is $3.75, six jobs are $22.50, and a three-minute Timeline 1.0 render adds $0.30, for $22.80 before any audio extraction. Treat the cuts between jobs as scene changes you plan, not seams you hide.
The arithmetic
The Wan 3.0 rates are the fal list prices of $0.05, $0.10 and $0.20 per second at 480p, 720p and 1080p, multiplied by Sume's 1.25 house margin. The Timeline fee is $0.10 per output minute, and a 180-second output is exactly three minutes.
All numbers here come from the Wan 3.0 list rates of $0.05, $0.10 and $0.20 per second at 480p, 720p and 1080p, multiplied by Sume's 1.25 factor, plus the $0.10 per output minute Timeline fee. Retries and failed jobs are not included.
| Resolution | Billed per second | One 30 s job | Six jobs | Plus 3 min timeline |
|---|---|---|---|---|
| 480p | $0.0625 | $1.88 (rounded up from $1.875) | $11.28 | $11.58 |
| 720p | $0.125 | $3.75 | $22.50 | $22.80 |
| 1080p | $0.25 | $7.50 | $45.00 | $45.30 |
Plan the scene breaks before you write
Six independent jobs cannot share a single continuous shot. Write the finale as six scenes that each end on a natural cut: a door closes, a phone rings, a character walks out of frame. Give every job the same reference images and the same style sentence so the cast looks alike, and open each scene with the first frame you want by sending it as first_frame in frame_images.
Wan 3.0 also accepts reference images, videos and audio, so a recurring voice or face can ride along in every request. Read supported_input_references from GET /v1/videos/models to confirm what the model accepts today.
Sound across six clips
Timeline 1.0 joins picture to one audio spine. If the sound of each Wan job is part of the finale, extract it with audio detach and give the files to the timeline as audio.parts (up to 20 gapless slices). If you would rather score the finale with one music bed, send it as the soundtrack with a duck_db and keep dialogue on the spine.
Run order and retries
Submit the six jobs with distinct Idempotency-Key values, such as the season, the episode and the scene number, and poll or take a webhook for each. If scene 4 is wrong, regenerate only scene 4 at 720p ($3.75) and re-run the $0.30 timeline. Draft at 480p first if you are still changing the script: the same six scenes cost $11.28 at 480p, and a replaced scene is only a quarter of that.
Sources
Related posts
More in Use cases
- Seedance 2.5 Draft mode on Runway: 480p proofs, and 480p on Sume
Runway's Oct 2 changelog adds Seedance 2.5 Draft mode for 480p drafts. Sume's seedance-2.5 also renders at 480p through its API; here is how they differ.
- How do I make a self-guided walking tour audio with TTS?
A six-stop walking tour at 700 characters a stop is six TTS jobs of 4 cents each, 24 cents on Sume, about 0.9 MB per stop as default mp3.
- Seven vertical AI videos a week: a stdlib Python batch with keys
A short Python script that submits seven 9:16 video jobs to Sume with Idempotency-Keys, so a rerun never bills a second job. Standard library only.
- Shorts-only YouTube playlists can't be reordered: render in order
YouTube's playlist help says reordering is unavailable for Shorts-only playlists. Fix episode order before upload and render in order with fixed keys.
Written by Sume