Price a 47-second ad with music first: the unbilled Timeline plan

A 47-second ad with a generated music bed costs $0.225 on Sume's list prices: $0.125 for one Music Router generation and $0.10 for a Timeline 1.0 render, which bills per output minute rounded up. You can check the render side without spending anything, because POST /v1/timeline-1.0/plan returns billable_minutes and estimated_cost_usd_micros and creates no job.

What the plan call does

The Timeline 1.0 docs describe plan as a schema and Sume-host URL check plus the compiler, returning object: timeline_plan with duration_seconds, segment_count, billable_minutes and a filtergraph summary. It does not create a job, reserve credits or download media, and Idempotency-Key is not required. It cannot predict warnings about short sources being padded or looped.

Rounding table

The render rate is $0.10 per output minute, rounded up, and the reserve is ceil(audio.duration_seconds / 60) minutes. Adding one music generation at $0.125 gives these totals for a single take.

Where the totals move

The table assumes one music take and no other paid steps. Retakes cost $0.125 each. Reusing one track across several ad versions costs the music once and a render per version. If you join takes first with timeline audio, add $0.01 per job. Video clips generated elsewhere on Sume are separate line items, billed by their own models.

• Cut a 61-second ad to 60 and save $0.10 per render.
• Generate music once per campaign mood, not once per variant.
• Run plan in CI so a bad timeline fails before spend.

Confirm the live rates

The docs point to GET /v1/catalog for live public prices, and this post quotes the docs as read on 2026-10-04. The Music 1.0 page lists the fixed $0.125 per accepted generation, and failed or rejected requests are covered under the platform's job and credit rules in Jobs and results, so check there before you assume what a failure costs.