Video Router
Explicit pass-through video generation via the Video Router catalog, including Seedance.
We recommend that new integrations use Video generation
(POST /v1/videos) in place of this API. It has the same catalog and the same
jobs behind an OpenRouter-compatible wire. Video Router stays available and does
not change.
Video Router is the explicit model catalog of Sume for video generation.
You select a catalog model ID from GET /v1/video-router/models (for example
Seedance). Each model uses its own credits, and Sume returns the usual async
job envelope. The API rate card lists the
current credits.
For new integrations, we recommend Video Router Auto through
POST /v1/videos with model: "sume/auto". Sume will retire
Video 1.0 soon. Until then, it stays a compatibility alias for
the same Auto pipe. The Auto create controls have a default of 720p and 8s, with
3–10s clips at 16:9 or 9:16.
Primary invoke URL:
Catalog:
When to use
| Goal | Approach |
|---|---|
| Let Sume select the model | Use Video Router Auto + model: "sume/auto" |
| Pin a catalog model (for example, Seedance) | Video Router + model from the catalog |
Create a Video Router job
Limits are different for each model. seedance-2.5 accepts 4–30s at
480p/720p/1080p. wan-3.0 accepts 2–30s. higgsfield-genjutsu (Motion
Transfer: video_url plus 1–8 reference_image_urls, 480p/720p) accepts
4–30s. This model is in the catalog only when its provider is configured.
minimax-h3 accepts 5–15s at native 480p/768p (768p is
first-class, not 720p). Each other catalog model has a limit of 15s.
seedance-2 also has 1080p. minimax-h3-max (MiniMax H3 Max) is the faster
768p variant. It does text-to-video, start/end-frame image-to-video, and
reference-to-video (reference_*_urls) at 480p/768p/1080p (1080p is a latent
refinement from native 768p) for 5–15s. gemini-omni-flash-1.1 (Gemini Omni
Flash 1.1) is 3–10s at 360p/720p/1080p/4K, 16:9 or 9:16, and native synced
audio is always on.
vidu-q4 (Vidu v4) animates one first-frame image_url (the prompt is
optional, audio is always on, and the image sets the framing).
vidu-q4-reference (Vidu v4 Reference) takes 1–12 reference_image_urls and
up to 3 mp3 reference_audio_urls with a required prompt, in 16:9, 9:16, 4:3,
3:4, or 1:1. Both accept 3–16s at 540p/720p/1080p/2K/4K.
Read capabilities from GET /v1/video-router/models, because each model can
have a different envelope.
Gemini Omni Flash 1.1
gemini-omni-flash-1.1 is one catalog ID. Sume routes it by the shape of the
request, and you never select an endpoint:
| Capability | Send | Notes |
|---|---|---|
text_to_video | prompt | 3–10s, resolution 360p–4K, aspect_ratio 16:9 / 9:16 |
image_to_video | image_url (+ optional end_image_url) | The same envelope |
reference_to_video | reference_image_urls (≤10) and/or reference_video_urls (≤3, each ≤3s) | Refer to the media as <IMAGE_REF_0>, <VIDEO_REF_0> (0-based, in list order) |
video_to_video (edit) | video_url | The prompt gives the instructions for the edit. resolution is optional (default 720p). No aspect_ratio / duration |
Native audio is always on (the API rejects generate_audio: false). There is
no bitrate_mode and no reference_audio_urls. Credits scale with the output
seconds and the resolution.
Edit example:
video_url is the edit source, not a reference. You cannot send it with
image_url, end_image_url, or reference_*_urls.
For the full request schema and catalog fields, refer to the OpenAPI paths under Video Router in the API reference.