Runway API model list vs the Sume video catalog: what overlaps

Runway's model guide lists third-party video models next to its own: Seedance 2.5 and 2.0 (with Fast and Mini variants), MiniMax H3, Wan 3.0, Grok Imagine Video 1.5, Veo 3.1 and Gemini Omni Flash. Of those, Sume carries Seedance 2.5, Seedance 2 and its Fast and Mini variants, MiniMax H3, Wan 3.0, Grok Imagine Video 1.5 and Gemini Omni Flash 1.1; it does not carry Veo 3.1 or Runway's own Gen-4.5, Gen-4 Turbo, Aleph or Act-Two.

Side by side (read 2026-10-04)

Names are matched by model family, not by identical settings. Resolution lists, durations and prices differ between the two platforms.

What changes if you move a call

Model ids on Sume are bare strings such as wan-3.0. Request fields follow the OpenRouter video wire, not Runway's. Sume rejects size, seed and provider.options with a 400 unsupported_parameter rather than ignoring them, so remove those fields.

• Auth is a bearer API key.
• The job is asynchronous: submit, then poll polling_url or use a webhook.
• Billing is provider list times 1.25, reserved at submit.

Ask the catalog, not the table

The table above is a snapshot. The live source is the listing, which returns each model's resolutions, aspect ratios, durations and inputs.

curl "https://api.sume.com/v1/videos/models" \
  -H "Authorization: Bearer $SUME_API_KEY"

Pricing and billing differ

Runway bills credits at $0.01 per credit. Sume reserves a USD balance at submit, at provider list times 1.25 rounded up to the cent. A 402 insufficient_credits means the balance could not cover the reservation, and a 429 means queue_full or rate_limited.