Flow video edit costs 40 credits a try; Sume bills per second

Google Flow charges a flat 40 credits for each video edit made with Gemini Omni Flash, whatever the clip length. Sume's gemini-omni-flash-1.1 edit mode takes a video_url and bills per second of output at 720p $0.125 a second by default, so a 5-second edit reserves $0.625 and a 10-second edit $1.25.

Flow's price comes from the Flow credits page; the model's input limits from the Omni Flash API page; both read 2026-10-02. Sume's edit contract is in the Video Router docs.

What is Flow's edit price?

The credits page lists video editing at 40 credits per edit. Google does not say on that page whether a failed or retried edit is refunded, so do not assume it. The page also says daily credits do not roll over, which matters if you plan to iterate: each retry is another 40.

On the model side, Google's Omni page says an uploaded video for editing or extending must be 10 seconds or less, and that editing or extending uploaded videos is not available in the EEA, Switzerland or the UK. Our post on the EEA, UK and Switzerland edit limit covers that rule on its own.

How does a Sume edit work and what does it cost?

In Sume's Video Router an edit is a normal request with video_url and a prompt that describes the change. Output length follows the source clip, so duration and aspect_ratio are not accepted. resolution is optional and defaults to 720p. Native audio stays on, and video_url cannot be combined with image_url, end_image_url or the reference fields.

Because there is no duration input on edits, Sume's docs let you pass duration only as a reserve hint for admission; it is never forwarded to the model. That keeps the reserve honest when the clip length is unknown. The final charge follows the output seconds.

Which one suits a few polished edits versus many small ones?

A flat fee rewards long clips and punishes short ones. Short edits cost less per call on Sume, because you pay for the seconds in the clip. A 10-second edit on Sume is the closest to a flat-fee workload, and you can only compare it with Flow's 40 credits once you know what a credit costs on your Google plan, which I did not fetch.

For a one-off change in a browser, Flow's editor and conversation flow are the simpler path. For repeated product swaps across many files, an API call per clip with an idempotency key is easier to script and to retry safely.

What does the request look like?

This is the edit call from Sume's docs, with a fresh idempotency key. Poll the returned job as described in Jobs and results.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: omni-edit-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Replace the bottle with an apple. Keep everything else the same.",
    "video_url": "https://example.com/clip.mp4",
    "resolution": "720p",
    "mode": "async"
  }'

How do you control the cost of retries?

Flow's flat fee makes retries easy to count: three tries is 120 credits. On Sume, the cost of each try is a function of source length, so shorten the source before you edit. If only two seconds of a clip need the change, trim to that window first and edit the short piece; the edit then reserves two seconds at the 720p rate, or $0.25, and you splice the result back.

Sume's catalog also includes trim and timeline tools for the cut and splice steps, which keeps the whole chain inside one API and one balance. None of that is needed for a single edit in Flow's browser editor.

What does Sume not do here?

Sume does not offer Flow's conversational, multi-turn editing with previous_interaction_id; each edit is its own job on the original or a result URL you pass back in. Flow's editor, agent and custom tools are separate products with no Sume equivalent.