Kandinsky 6.0 stops at 5 s: a 30 s ad as one job or six clips
Kandinsky 6.0 Video makes 5 s clips. A 30 s ad on Sume is one Wan 3.0 job at $3.75 or six clips stitched for $0.17 in assembly fees. What each route costs you.

A 30-second ad from Kandinsky 6.0 Video means six separate 5-second generations that you join yourself, because the repository lists 5 seconds as the clip length. On Sume the same 30 seconds can be one request: Wan 3.0 accepts 2 to 30 seconds and Seedance 2.5 accepts 4 to 30 seconds, per the docs. At the 720p Wan rate in Sume's pricing tests, one 30-second job is $3.75.
Kandinsky facts are from its GitHub repository, read 2026-10-11. Sume facts come from Video Generation, Timeline 1.0, Audio detach and Timeline audio. Sume does not list Kandinsky, so the stitch route below applies to clips you made elsewhere and import.
Route A: one long job
One request keeps a single continuous shot and one prompt. The catch is the limit: the docs say each other catalog model has a maximum of 15 seconds, and Gemini Omni Flash 1.1 tops out at 10. Only wan-3.0 and seedance-2.5 reach 30. Wan 3.0 at 720p bills $0.625 for 5 seconds in Sume's golden-amount test, which is $0.125 per second, so 30 seconds is 30 x $0.125 = $3.75 on a straight-line assumption.
Route B: six 5-second clips and Timeline
Stitching gives you six cuts, so plan for them as an edit rather than one shot. Timeline 1.0 takes one audio spine plus up to 200 ordered video slots and bills $0.10 per output minute, rounded up. A 30-second render is one billable minute. Because the render uses a single spine, native clip audio does not ride along by itself. The documented way to keep it is to pull each clip's audio with Audio detach ($0.01 per job), join the six files with Timeline audio concat ($0.01 flat, up to 20 parts), and pass that file as the spine.
| Step | Count | Rate | Subtotal |
|---|---|---|---|
| Audio detach, one per clip | 6 | $0.01 per job | $0.06 |
| Timeline audio concat | 1 | $0.01 flat | $0.01 |
| Timeline 1.0 render, 30 s | 1 | $0.10 per output minute | $0.10 |
| Total assembly | $0.17 |
Which route when
Both routes are valid; they answer different needs.
- One continuous move or a single subject across 30 seconds: Route A, because a stitch will show seams.
- Six distinct beats with different prompts: Route B fits, and the cuts are the design.
- Open weights and zero per-clip fee: Route B with clips from your own GPU, plus about $0.17 in Sume assembly fees. Local clips must be importable by URL first, since Sume's media tools refuse off-host files.
- Most predictable price: Route A. Six takes can also mean six retries, and each retry is a clip you re-render.
Caveats
The $3.75 figure assumes the rate scales linearly with seconds, which matches how the pricing tests describe a per-second SKU but is arithmetic here, not a quote. Confirm the live price with GET /v1/catalog, or run a Timeline plan call, which is unbilled and returns an estimate. Sound at the seams also needs checking by ear, since the concat is sample-exact but the music and ambience inside each clip were generated separately.
Sources
Related posts
More in Comparisons
- Kandinsky 6.0 Lite takes 406 s on an RTX 5090: local or hosted?
The Kandinsky repo times one 5 s Full HD clip per GPU: 406 s for Lite on an RTX 5090. Clips per hour by card, and when a hosted Sume job is simpler.
- OpenRouter lists 26 video ids: which have a Sume id (Oct 2026)
Of 26 video ids on OpenRouter's listing, 11 map to a Sume catalog id and 15 do not. The full id-by-id table, read 2026-10-11, and what Sume lists instead.
- OpusClip API alternative: what Sume can cut and what it cannot
Sume has no highlight-finding API like OpusClip's. It trims, captions and assembles clips you pick; the source must be on media.sume.com first.
- PiAPI's $0.50 start credit and resetting bonus vs a Sume USD balance
PiAPI gives new accounts $0.50 plus bonus credits that reset each cycle. Sume bills a USD balance at published model rates and sets concurrency by plan.
Written by Sume