Swap the product in a UGC clip with Gemini Omni Flash 1.1 video edit
Keep a UGC clip that works and change only the product: Sume's video router edit mode for gemini-omni-flash-1.1 takes a video_url and a one-line prompt.

To reuse a creator clip for a new product, send the clip as video_url to POST /v1/video-router/generate with model: gemini-omni-flash-1.1 and a prompt that describes the change, such as replacing one item with another and keeping everything else. This is the model's video_to_video edit mode, and it is meant for small changes inside a clip you already have.
What does the edit mode accept?
| Capability | What to send | Notes |
|---|---|---|
| video_to_video (edit) | video_url | Prompt describes the edit; resolution optional, default 720p; no aspect_ratio or duration |
| reference_to_video | reference_image_urls up to 10, reference_video_urls up to 3 of 3 s or less | Address media as <IMAGE_REF_0>, <VIDEO_REF_0> |
| image_to_video | image_url, optional end_image_url | 3 to 10 s |
| text_to_video | prompt | 3 to 10 s, 16:9 or 9:16 |
What does a call look like?
Native audio is always on for this model. video_url is the edit source, not a reference, so it cannot be combined with image_url, end_image_url or the reference_*_urls fields. Billing is provider list times 1.25 per output second by resolution.
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: swap-product-001" \
-d '{
"model": "gemini-omni-flash-1.1",
"prompt": "Replace the bottle in her hand with a red gift box. Keep everything else the same.",
"video_url": "https://example.com/ugc-clip.mp4",
"resolution": "720p",
"mode": "async"
}'Why can I not add a reference image of the new product?
Because the edit source cannot be combined with image or reference inputs. The new product has to be described in words. If the product's look matters, such as a label or a specific shape, use the other route: generate a new clip with reference_image_urls of the product, or run a catalog Format that starts from your packshot.
When should I regenerate instead of edit?
Edit when the creator, the room and the movement are the part you like, and the product is a small object in the frame. Regenerate when the product is the star of the shot, because a prompt cannot show a specific label. For a fresh clip built from your packshot, the catalog Formats start from an attached image of the real product.
Either way, test on one clip before you edit a set. An edit is a paid job, so a retry with a new Idempotency-Key is charged again, while a retry with the same key and body returns the original job. A good habit is to name keys after the clip and the prompt version, so you can tell which edit you are looking at later.
What are the limits?
- Read
capabilitiesinGET /v1/video-router/modelsbefore you build on the edit mode. - Words describe the swap, so labels and logos on the new item are not guaranteed to match your product. Check them frame by frame.
- Audio is always generated; you cannot turn it off with
generate_audio: false. - You need rights to the source clip, and a person who appears in it still appears in the edit.
- The edit changes what is shown, so check that the result does not make a claim the original did not make.
Sources
Related posts
More in Models
- SynthID audio and MP3: does the mark survive Sume's 128 kbps detach?
Google says SynthID audio marks resist noise, MP3 compression and speed changes. Sume audio detach can output 128 kbps MP3; only some sources carry a mark.
- SynthID text watermark: a Gemini script in a Sume avatar video
Google says SynthID marks Gemini app text. If it becomes a Sume avatar script, the video is a new render, and no docs say the mark carries over.
- A 12-headline text rendering test for any image model
FLUX 3 and Ideogram 4.5 both claim better text. Run your own 12 headlines through the models Sume lists and review the outputs by eye, not by launch post.
- Veo 3.1 and Veo 3.1 Fast previews end October 22: what replaces them
Google's deprecations page sets October 22, 2026 as the shutdown date for the Veo 3.1 and 3.1 Fast previews. Dates, the replacement id and what Sume lists.
Written by Sume