Runway's API lists 19 video ids: which ones have a Sume id?

Nine of the 19 video ids on Runway's API pricing page map cleanly to a Sume id, eight have no Sume equivalent, and two (h3_max, hailuo3) I cannot confirm from Runway's page alone. If you are porting a Runway script, this table tells you which model strings you can swap and which you must replace.

Runway's list is read from its pricing page on 2026-10-10. Sume's ids come from the API registry and the Video Generation docs.

The mapping

Runway lists these ids: wan3, wan3_prime, seedance2_5, grok_imagine_1_5, grok_imagine_1_5_lite, seedance2, seedance2_fast, seedance2_mini, h3_max, hailuo3, aleph2, gen4.5, gen4_turbo, act_two, veo3.1, veo3.1_fast, happyhorse_1_0, gemini_omni_flash and gemini_omni_flash_1.1 (read 2026-10-10).

Sume's registry carries the Seedance family, Wan 3.0, the 1.5 Grok row, Gemini Omni Flash 1.1, Kling 3, MiniMax H3 and H3 Max, and, where switched on, the Veo 3.1 rows.

What changes when you swap an id

Matching ids do not mean matching requests. Sume's POST /v1/videos takes model, prompt, duration, resolution and aspect_ratio, plus frame_images and input_references. Per the Video Generation docs, size, seed and non-empty provider.options return a 400 unsupported_parameter, so strip them from a ported script.

The Grok row needs an image: the schema requires one of image_url, first_frame_url or one reference image, and rejects aspect_ratio, end frames and reference video or audio. Runway's page also lists a 1-credit start-image surcharge on its Lite row, so confirm which inputs your script sends before you compare totals.

Billing differs by design

Runway bills in credits at $0.01 each. Sume bills the workspace USD balance, reserving provider list price times 1.25 at submit, and usage.cost reports the billable amount. A matching id therefore does not mean a matching bill.

For example, Runway's Seedance 2.5 line is 20, 30 and 68 credits per output second at 480p, 720p and 1080p, which is $0.20, $0.30 and $0.68 per second, plus input seconds. Running the estimator in Sume's pricing package for a 16:9, 5-second request at 720p gives a billed $2.889, or about $0.58 per second, because Seedance is priced per video token. Compare your real clip, not the label.

A porting checklist

Work through a ported script in this order. First, replace the model string with the Sume id from the table, and call GET /v1/videos/models to confirm it is returned for your workspace. Second, delete size, seed and provider.options. Third, check the duration against the row's supported_durations: Omni takes 3 to 10 seconds, Seedance 2.5 and Wan 3.0 take up to 30. Fourth, add an Idempotency-Key header to every submit, because a replay returns the original job instead of billing twice.

Finally, read usage.cost on the completed job and compare it with your Runway credit spend for a few real clips. Do this before you move volume, since the rate cards are built differently.

Ids Sume does not have

For Aleph, Gen-4.5 and Act Two there is no Sume id, so no model string replaces them. For video editing on Sume, the docs list Gemini Omni Flash 1.1 (through video_url) and H3 Max Recast. Look at the linked posts for HappyHorse and Veo, which Sume handles differently.