Edit an existing video with Gemini Omni Flash 1.1 over an API
Send video_url and an instruction to gemini-omni-flash-1.1 on Sume to edit a clip: no duration or aspect ratio, resolution optional, native audio on.

To edit a clip with Gemini Omni Flash 1.1 on Sume, send video_url and an instruction as prompt to POST /v1/video-router/generate with model: "gemini-omni-flash-1.1". The prompt carries the edit, resolution is optional and defaults to 720p, and you send no aspect_ratio or duration.
This is from the Video Router docs (read 2026-10-06). Edit mode bills output seconds, using your duration hint if you send one and 8 seconds otherwise, at the provider list price times 1.25.
What does the request look like?
The source goes in video_url, which is an edit source and not a reference, so it cannot travel with image_url, end_image_url or reference_*_urls.
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: video-router-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"
}'What does an 8-second edit cost?
Without a duration hint Sume bills 8 seconds. Computed from the rate card on 2026-10-06:
| Resolution | 8-second edit |
|---|---|
| 360p | $0.30 |
| 720p | $1.00 |
| 1080p | $1.50 |
| 4K | $3.00 |
What are the limits?
Edit mode shares the model's envelope.
- Native audio is always on; the API rejects
generate_audio: false. - There is no
reference_audio_urlsand nobitrate_mode. - The clip source must be a public HTTPS URL that Sume can fetch.
Sources
Related posts
More in Models
- Gemini Omni scene extension: app, Flow, API or Sume?
Google's launch post lists four places Omni 1.1 Flash runs. Scene extension is not in all of them, and Sume's router does not expose it. Where to go instead.
- gpt-image-1 retires December 1: scan your repo, move to gpt-image-2.5
OpenAI's deprecations page lists gpt-image-1, 1.5 and 1-mini for December 1, 2026. A Python scan finds the ids, and Sume serves openai/gpt-image-2.5.
- Tokens in a 1280x720 GPT Image 2.5 image: 106 to 3,787
A 1280x720 GPT Image 2.5 output is 106 tokens at low and 3,787 at max. Token count, dollars at $30 per 1M, and images per million tokens.
- 1792x1008 on GPT Image 2.5: the exact 16:9 size between 720p and 1440p
1792x1008 is a legal exact 16:9 size for GPT Image 2.5. About $0.0052 at low to $0.1850 at max on Sume, with the full quality table.
Written by Sume