Estimate a Sume timeline render before paying: the unbilled plan call

POST /v1/timeline-1.0/plan compiles your document and returns duration, billable minutes and an estimate without creating a job or reserving credits.

4 min readSume
All posts

POST /v1/timeline-1.0/plan runs the same schema checks, Sume-host URL checks and compiler as a render, then returns the plan without creating a job or reserving credits. Use it to read billable_minutes and estimated_cost_usd_micros before you submit a long or multi-language render.

What the plan returns

The response has object: timeline_plan with the fields below. An Idempotency-Key is not required because nothing is created.

timeline_plan fields (read 2026-10-03)
FieldMeaning
duration_secondsOutput length
segment_countNumber of compiled segments
billable_minutesMinutes the render would bill, at $0.10 per ceil minute
estimated_cost_usd_microsEstimate in micro-dollars
filtergraph_summaryCompiled summary, no raw filters

Limits of a plan

A plan does not download media, so it cannot predict short-source pad or loop warnings. Those appear as soft warnings[] on the finished render, not as failures.

Use the plan result to fail early when a document is invalid: a missing media.sume.com URL, video[0].start not 0, or audio parts that sum to less than duration_seconds.

When it pays off

A 30-minute render is the cap (audio.duration_seconds up to 1,800) and bills 30 minutes. Plan each language version first, check the minutes match the spine you expect, then render. The check costs nothing and avoids a paid job with the wrong length.

Sources

Related posts

More in Media tools

All Media tools posts

Written by Sume