Omni reference-to-video with 3 clips of 3 s: a 10 s output is $1.25
Gemini Omni Flash 1.1 takes up to 10 reference images and 3 reference clips of 3 seconds each. A 10-second 720p output is 10 x $0.125 = $1.25 on Sume.

Gemini Omni Flash 1.1 (gemini-omni-flash-1.1) accepts up to 10 reference images and up to 3 reference video clips, each at most 3 seconds, so the most reference footage one request can carry is 9 seconds. The output is 3 to 10 seconds. A 10-second 720p result costs 10 x $0.125 = $1.25 on Sume, and the reference media are not a separate charge in the docs.
Request fields
On the Video Router you send reference_image_urls and reference_video_urls. In the prompt you point at them with 0-based tokens in list order, <IMAGE_REF_0>, <IMAGE_REF_1>, <VIDEO_REF_0>, and so on. The reference media are sent before the prompt.
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-r2v-001" \
-d '{
"model": "gemini-omni-flash-1.1",
"prompt": "<IMAGE_REF_0> walks into the room from <VIDEO_REF_0> and sits down",
"reference_image_urls": ["https://example.com/person.png"],
"reference_video_urls": ["https://example.com/room-3s.mp4"],
"resolution": "720p",
"duration": 10,
"aspect_ratio": "16:9",
"mode": "async"
}'Limits and price at each tier
The limits below come from the Video Router docs and the model's constraints. Price is for a 10-second output.
| Item | Value |
|---|---|
| Reference images | up to 10 |
| Reference clips | up to 3, each at most 3 s |
| Reference audio | not accepted |
| 360p, 10 s | 10 x $0.0375 = $0.375, shown as $0.38 |
| 720p, 10 s | 10 x $0.125 = $1.25 |
| 1080p, 10 s | 10 x $0.1875 = $1.875, shown as $1.88 |
| 4K, 10 s | 10 x $0.375 = $3.75 |
Pitfalls
Sending a lone reference image with no first or end frame is treated as reference-to-video. Sending a video_url is different: it selects edit mode, and you cannot combine it with image_url, end_image_url or any reference_*_urls. Native audio is always on and reference_audio_urls is not available, so a voice or soundtrack you want must come from the prompt, not an audio reference.
If a 3-second reference clip is a rough cut, trim it first. The video trim API costs $0.02 per job.
Choosing between images and clips
Use reference images when you need identity: a face, a product, a logo. Use reference clips when you need motion or a place. Each reference clip can be at most 3 seconds, so cut the best three seconds of a longer take first.
Because reference_audio_urls is not accepted, a voice sample cannot guide the audio. If a specific voice matters, generate on a row that takes audio references, such as Seedance 2.x, Wan 3.0 or MiniMax H3, whose docs list audio among their input reference types.
Sources
Related posts
More in Developers
- generation_limits missing from a Sume submit: send one, then re-read
The docs say the snapshot is included when Sume can compute it. A Python rule for waves when it is absent, full, or open, tested on three inputs.
- HappyHorse 1.1 [Image 1] tags vs Sume's <IMAGE_REF_0> in prompts
HappyHorse reference-to-video counts images from [Image 1]; Sume's Omni counts from <IMAGE_REF_0>. How to map a prompt without an off-by-one.
- 8 active and 15 queued on Startup: the new in-flight budget is zero
Sume's headroom is min(max(0, concurrency - active - queued), queue_capacity_remaining). A Startup example that returns 0, the docs example that returns 60.
- Hosted Sume MCP token hygiene: 5 rules for agent credentials
Five Sume credential rules: an OAuth token is not an API key, stays out of CLI config and prompts, never goes to other providers; rotate exposed keys.
Written by Sume