Runway lists 18 video model ids: which nine does Sume have?
Of the 18 video ids on Runway's models page, nine match a Sume id: four Seedance rows, MiniMax H3 and Max, Wan 3.0, Grok Imagine, Gemini Omni Flash 1.1.
Nine of them. Runway's models page lists 18 video generation ids, and nine correspond to a model in Sume's OpenAPI catalog enum: four Seedance rows, MiniMax H3, MiniMax H3 Max, Wan 3.0, Grok Imagine Video 1.5 and Gemini Omni Flash 1.1. The other nine, including Gen-4.5, Aleph 2.0, Veo 3.1 and Act-Two, have no Sume id. Sume also lists three ids that Runway's video table does not: kling-3, h3-max-recast and higgsfield-genjutsu.
Runway's list is from its models page, read 2026-10-02. Sume's ids are from the OpenAPI model enum and Video Router. Matching is by model name, not by behavior: a shared name does not mean identical limits or prices.
Which Runway video ids match a Sume id?
The table pairs each Runway display name and id with the Sume catalog id for the same named model, where one exists. Where Runway has two tiers and Sume has one id, the table says so rather than guessing a match.
Sume's separate minimax-h3-max and gemini-omni-flash-1.1 ids line up with Runway's h3_max and gemini_omni_flash_1.1; Runway's older gemini_omni_flash has no separate Sume id.
| Runway name | Runway id | Sume id |
|---|---|---|
| Seedance 2.5 | seedance2_5 | seedance-2.5 |
| Seedance 2.0 | seedance2 | seedance-2 |
| Seedance 2.0 Fast | seedance2_fast | seedance-2-fast |
| Seedance 2.0 Mini | seedance2_mini | seedance-2-mini |
| MiniMax H3 | hailuo3 | minimax-h3 |
| MiniMax H3 Max | h3_max | minimax-h3-max |
| WAN 3.0 | wan3 | wan-3.0 |
| Grok Imagine Video 1.5 | grok_imagine_1_5 | grok-imagine-video-1.5 |
| Gemini Omni Flash 1.1 | gemini_omni_flash_1.1 | gemini-omni-flash-1.1 |
| Aleph 2.0, Gen-4.5, Gen-4 Turbo | aleph2, gen4.5, gen4_turbo | None |
| WAN 3.0 Prime | wan3_prime | None; one wan-3.0 id |
| HappyHorse 1.0, Veo 3.1, Veo 3.1 Fast | happyhorse_1_0, veo3.1, veo3.1_fast | None |
| Gemini Omni Flash, Act-Two | gemini_omni_flash, act_two | None |
What does a missing id mean for my code?
Sume rejects ids that are not in GET /v1/video-router/models. A request with gen4.5 or veo3.1 therefore fails validation instead of falling through to a similar model. If you want Sume to choose, send model: "sume/auto"; the family that served the job is not disclosed in the response.
Id spelling also differs. Runway uses underscores and short names (seedance2_5); Sume uses bare catalog ids with dots and hyphens (seedance-2.5), and its /v1/videos route has no org/slug prefix.
How do I list Sume's current ids?
Ask the catalog rather than copying this table. The command prints every video id your key can see; higgsfield-genjutsu appears only when its provider is configured.
curl -s https://api.sume.com/v1/video-router/models \
-H "Authorization: Bearer $SUME_API_KEY" \
| jq -r '.data.models[].id'Sources
Related posts
More in Comparisons
- Runway Characters voice clone: 10 s to 5 min, 10 MB; the Sume route
Runway clones a Character voice from a 10-second to 5-minute sample up to 10 MB. Sume avatar video documents text scenes, and Fabric takes your own audio_url.
- Runway Characters knowledge base: 50,000 tokens per avatar vs Sume
Runway attaches up to 50,000 tokens of text or Markdown knowledge to a Character. Sume avatars have no knowledge base; the script you send is the whole content.
- Runway Characters session cap is 5 minutes; what Sume Avatar 1.0 caps
Runway Characters docs list a 5-minute session, 10,000-character personality and 2,000-character start script. Sume Avatar 1.0 renders 4-60 second clips.
- Runway Enhance Frame Rate 59.94 fps vs Sume's 60 fps output
Runway lists 59.94 fps among its Enhance Frame Rate targets. Sume's Timeline output.fps takes 24, 25, 30 or 60, so there is no 59.94 and no 120 fps.
Written by Sume