30-second video ad on Sume: one clip or two joined, priced

For a 30-second video ad on Sume, a single 30 s clip is the most expensive route. Seedance 2.5 at 720p 9:16 costs $17.334 for 30 seconds; two 15-second Seedance 2 Fast clips joined with Timeline cost $9.172; Wan 3.0 at 720p does 30 seconds in one clip for $3.75. Seedance 2.5 and Wan 3.0 are the two models that accept 30 seconds in one request.

Four routes compared

Per-second figures are the provider list rate times the 1.25 Sume margin that the docs describe, as of 2026-10-08. Read capabilities from GET /v1/video-router/models before you bill a batch, because rates and envelopes can change.

What the join costs

Timeline 1.0 charges $0.10 per ceil(output minute), so a 30-second result is one minute and costs $0.10. The plan endpoint does not bill, so you can validate the segment list first. The default output is 1080x1920; set output width and height to even values between 256 and 2160 if you need a different frame.

• Up to 12 segments: a single render strategy is accepted.
• Auto strategy chunks the render when you go past 12 segments.
• fps: set output.fps to 24, 25, 30 or 60 to avoid a resample warning.

When one clip is worth it

Pay for the single clip when the shot must not cut: a pour, a continuous camera move, a talking head. Two 15-second halves add a cut at 15 seconds, so write the second prompt to start on that cut. For product-on-white ads that already cut every 3 to 5 seconds the join is invisible, and the saving against Seedance 2.5 is $17.334 - $9.172 = $8.16, at the price of a different model.

Where a 30-second clip lands in a plan

Thirty seconds is the upper end of what Google and the social feeds use for product ads, and most buyers want it in 9:16. Wan 3.0 is the cheapest single-call route at 2 to 30 seconds. Seedance 2.5 reaches 30 seconds as well and offers 480p, 720p and 1080p.

At Seedance 2.5 1080p the rate is $0.0234 per 1000 tokens before the 1.25 margin, so the 9:16 figure is about $1.42 per second, or roughly $42.65 for 30 seconds. That is why a 30-second 1080p job can fail with insufficient credits on a small balance: the reserve is taken at submit.

• Quote the job before you send it, or read the reserve from the response.
• Keep a balance above the reserve for the whole wave.