Are flat Sume timeline, trim and filter prices ceilings or fixed fees?
Flat prices for Sume timeline, compose, trim, filter and audio detach are reserved up front and captured at actual compute, never above the reservation.

Is a flat price on a Sume ffmpeg tool a fixed fee?
Treat it as a reserve ceiling. Sume's API contract describes these tools as reserved at the listed price and captured at the pass's own Modal compute (list price times 1.25 plus the platform fee), never above the reservation.
So the listed figure is the most the job takes. It is not a promise that every job lands exactly on that number, and Sume's docs do not publish a lower typical figure, so budget with the listed price.
What are the flat prices?
From the rate card.
| Tool | Listed price | Notes |
|---|---|---|
| Timeline render | $0.10 per output minute, rounded up | At most 1800 s, so $3.00 |
| Timeline compose | $0.02 | 300 s ceiling |
| Timeline audio | $0.01 | Flat |
| Video filter | $0.02 | 300 s source cap |
| Video trim | $0.02 | Flat |
| Audio detach | $0.01 | Flat |
| Standalone captions | $0.20 | Videos up to 60 s |
Which related calls cost nothing?
Several preflight calls are unbilled: the video-filter check, timeline plan, video-frames, the reference-ingest manifest and the Hypit probe, boundaries, tile and cut calls. Use them to confirm the job before you pay for it. The timeline plan post and the filter check post show how.
How should I budget with ceilings?
Add the listed price for each step. A pipeline of one trim, one filter and one 3-minute timeline render budgets at $0.02 + $0.02 + $0.30, or $0.34. Your real charge can be lower, but you cannot rely on that, and Sume's docs do not state by how much.
Read the final figure from the usage summary after the job, using the debited amount.
Does Sume refund the difference between reserve and capture?
The capture happens at actual compute and never above the reservation, so the balance you see after completion reflects the captured amount. Failed or pre-generation-canceled jobs are refunded. See the timeline docs for the render limits.
What does a pipeline budget look like?
A shop makes a 30-second ad from phone clips. It trims two clips at $0.02 each, runs one filter at $0.02, composes at $0.02 and renders a 1-minute timeline at $0.10. The ceiling total is $0.18.
Add captions at $0.20 and the pipeline budget is $0.38. Those are reserve ceilings, so the real total can only be lower or equal on the flat ffmpeg steps, though Sume's docs do not say by how much.
Run the free checks first, since a bad filter or plan costs nothing to find out, while a wasted render still costs its reserve.
Sources
Related posts
More in Pricing
- Veo 3.1 in Flow credits vs the Gemini API: cost of an 8-second clip
Flow charges 10, 20 or 100 credits for an 8-second Veo 3.1 Lite, Fast or Quality clip; the Gemini API lists $0.40 to $3.20. Sume does not list Veo.
- Veo 3.1 Fast 20 credits vs Quality 100 in Flow: a draft ladder
Flow charges 100 credits for Veo 3.1 Quality and 20 for Fast. Draft count per final, why the free daily credits cannot buy a Quality clip, and the Sume way.
- Veo 3.1 Lite in Flow: 10 credits, 5 on Ultra. How many drafts?
Flow's credits page prices Veo 3.1 Lite at 10 credits, or 5 for Ultra. What that buys per plan, and a cheap draft step before you spend on a final.
- FLUX.2 klein API price: $0.014 plus per megapixel, and Sume
BFL's page lists FLUX.2 klein 4B at $0.014 + $0.001 per MP and 9B at $0.015 + $0.002 per MP. Sume's catalog lists FLUX.2 pro and flex, not klein.
Written by Sume