Edit a finished Omni clip with video_url instead of re-rolling it

To change one thing in a clip you already have, send it as video_url to gemini-omni-flash-1.1 with a prompt that states the edit. On Sume that request is routed as a video-to-video edit. resolution is optional and defaults to 720p, and you must not send aspect_ratio or duration, since the edit keeps the clip's own shape and length (Sume docs: Video Router, read 2026-10-05).

The request

The clip has to be a Sume-hosted artifact URL, such as the output of an earlier job. The prompt describes the change, not the whole scene again.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Idempotency-Key: edit-shot3-raincoat-v1" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Change the mustard raincoat to dark green. Keep the motion and the street unchanged.",
    "video_url": "https://media.sume.com/artifacts/artf_demo/shot3.mp4"
  }'

Edit or re-roll

Google describes Omni 1.1 Flash as supporting video references and extension; it does not describe a price for edits (Google, read 2026-10-05). Sume bills the provider list times 1.25 for each output second at the chosen resolution, so an edit of a 10-second clip is billed like a 10-second output. Check the catalog and the pricing page for the live rate.

Habits that keep edits cheap

If the edited clip is the one you will ship, finish it at the resolution you need as the last step, then join it with the other shots in a timeline.

One more rule: the edit needs a Sume-hosted clip, so if the footage came from elsewhere you first need it on Sume's media host. Generate-then-edit within the same workspace is the simple path, because every finished job returns a durable artifact URL you can pass straight on.

Keep both versions. The original clip is your fallback if the edit changes something you did not ask for, and the pair also tells you, in a side-by-side, whether the edit did what the prompt said. Delete nothing until the final is approved.

If the edit is part of a longer piece, do it before the timeline join, not after. The timeline takes finished clips and does not regenerate anything, so a fix made earlier flows into the render without extra work.

Write the prompt as an instruction with a boundary: say what changes and what must stay. Phrases such as keep the motion and the street unchanged give the model a reason to leave the rest alone. A vague prompt such as make it better invites changes you did not want, and you pay for each attempt.

• Edit the draft, not the final, when you are still testing the instruction. Send resolution: 360p on the edit to keep the pass small.
• Edit one thing per request. A prompt that changes colour, time of day and a prop at once is a coin flip.
• Read the result before you chain another edit. Edits stack their errors.
• Use an Idempotency-Key that names the shot and the edit, so a retry replays the same job and a changed body is refused with a 409.