A 24-second Reel as three 8-second sume/auto jobs: $3.00
sume/auto is Gemini Omni Flash 1.1 at 3 to 10 s and 9:16. Three 8-second jobs cost $3.00 at 720p, chained by passing each last frame as the next first_frame.
sume/auto resolves to gemini-omni-flash-1.1: 3 to 10 seconds, 360p to 4K (720p default), 16:9 or 9:16, with native audio always on. The default duration is 8 seconds. A 24-second Reel therefore takes three jobs, and 8 seconds is the default, so you do not have to set it.
Cost
At 720p the rate is $0.125 per second: 8 s is $1.00 and three jobs are $3.00. Compare with a single 24-second Wan 3.0 job at the same $0.125 per second, also $3.00. The difference is that three Auto jobs give you three chances to fix a shot.
| Plan | Jobs | Total |
|---|---|---|
| sume/auto, 8 s x 3 | 3 | $3.00 |
| wan-3.0, 24 s x 1 | 1 | $3.00 |
| seedance-2.5, 24 s x 1 | 1 | $13.87 |
Chaining the three jobs
For continuity, grab the last frame of job one with video frames, upload it, and send it as frame_images with frame_type first_frame on job two. The same applies from job two to job three. Check that your model row lists first_frame in supported_frame_images, as shown in the video catalog.
Seams
Audio is generated inside each job, so the sound can change at the seams. Listen to the joins on your own footage before you publish.
Sources
Related posts
More in Developers
- 402 on a 30-second 1080p Wan 3.0 job: your balance must cover $7.50
A 30-second Wan 3.0 job at 1080p reserves $7.50 on Sume. If the balance is lower you get 402 insufficient_credits. Reserve table and handler.
- A 429 from the Sume API: read budget, write budget or queue_full?
Three different 429s share a status. Read error.code and error.details.scope to tell read, write and queue_full apart, then retry each the right way.
- A lost response on a 30 s Kling motion control submit: reuse the key
If a network timeout hides the reply to a 30-second Kling motion control submit, a new Idempotency-Key reserves $4.725 again. Reuse the key. Python retry loop.
- Use your ad variant id as the Idempotency-Key on Sume
Name each ad variant once and send that name as the Idempotency-Key. Retries do not double-bill, and the receipt echoes it back so results map to your ad names.
Written by Sume