Which Sume video models take a source video_url? Edit, transfer
Only three Video Router rows accept a video_url source: gemini-omni-flash-1.1 (edit), higgsfield-genjutsu (motion transfer) and h3-max-recast (person swap).

Three Video Router rows take a video_url source clip: gemini-omni-flash-1.1 for prompt-based edits, higgsfield-genjutsu for motion transfer, and h3-max-recast for swapping the people in a clip. No other row does, and sume/auto never routes to the last two.
Everything else, from Seedance 2.5 to Kling 3, generates a new clip from text, a frame or references. If you want to change an existing video, this is the whole list.
The three rows
The Video Router doc spells out the contract. video_url is the source of an edit, a motion-transfer or a recast job, and it cannot be combined with image_url, end_image_url or reference_*_urls. To condition a new generation on a clip, use reference_video_urls instead.
| Row | What video_url is | Other inputs | Duration |
|---|---|---|---|
| gemini-omni-flash-1.1 | Edit source (video_to_video) | Prompt; resolution up to 4K; no aspect_ratio | Follows the source clip |
| higgsfield-genjutsu | Motion Transfer source | 1 to 8 reference_image_urls; 480p or 720p | 4 to 30 seconds, the input length rounded up |
| h3-max-recast | Recast source (person swap) | 1 to 4 reference_image_urls; optional prompt; 768p or 1080p | 5 to 30 seconds, no shot over 15 |
Edit with Gemini Omni Flash 1.1
The edit request sends a prompt and the source clip. The API sends no aspect ratio on this path and returns a 400 if you give one, and generate_audio: false is also rejected because the model always produces synced audio. If you send a duration with video_url it is only a reserve hint (the default hint is 8 seconds); the source clip sets the output.
{
"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"
}Why Genjutsu may be missing
higgsfield-genjutsu appears in GET /v1/video-router/models only when its provider is configured for the environment. If your catalog call does not list it, that is expected, not a bug in your client.
Where this surface lives
video_url is a Video Router field. The OpenRouter-shaped POST /v1/videos body does not carry the edit mode, so use POST /v1/video-router/generate for these three. The legacy surface creates the same jobs and the same billing, at provider list times 1.25.
- Edit:
gemini-omni-flash-1.1, source length sets the output. - Motion transfer:
higgsfield-genjutsu, needs reference images, no text-only mode. - Recast:
h3-max-recast, one photo per new person, the output keeps the source motion, camera, cuts and sound.
Sources
Related posts
More in Models
- Which Sume video models accept an audio reference (audio_url)?
Seedance 2.x, Wan 3.0, MiniMax H3 and H3 Max take audio and video references on Sume. Gemini Omni Flash 1.1 and Recast do not. Rates and limits.
- Which Sume video models take an audio_url reference, which do not
Sume video rows list supported_input_references per model. The docs show seedance-2 with audio_url, H3 Max with audio, and Gemini Omni Flash 1.1 without it.
- Which video models does Sume list in October 2026? Twelve ids
Sume's video catalog has twelve ids, from seedance-2.5 at 30 seconds to gemini-omni-flash-1.1 at 4K. Length and resolution for each; Veo 3.1 is not listed.
- YouTube Shorts max out at 1080p, so don't generate at 4K
YouTube's Shorts help page caps uploads at 1080p. Sume's Gemini Omni Flash 1.1 offers 360p to 4K in 9:16, so request resolution 1080p and skip the higher tier.
Written by Sume