OpenRouter lists 26 video ids: which have a Sume id (Oct 2026)

Eleven of the 26 video ids on OpenRouter's video listing have a matching Sume catalog id, and 15 do not. The match is by model, not by spelling: Sume uses bare ids such as seedance-2.5, while OpenRouter prefixes a vendor, as in bytedance/seedance-2.5.

The OpenRouter side of this page comes from its video models listing, read on 2026-10-11. The Sume side comes from the Video Generation and Video Router docs and the video catalog code on the main branch. Sume's /v1/videos route follows the OpenRouter wire, so a client written for one needs a new base URL and key; the catalog is what differs.

Which of the 26 ids map to a Sume id?

The table lists every id on the listing, in the order a reader would scan it by vendor. The third column is the Sume id from the catalog code; "none" means the catalog has no row for that model.

Which mapped ids are not always listed?

Three of the eleven carry a condition in the code. The Veo rows are created through Google Cloud, and the route file says a Veo id is listed and accepted only where that key is set and the route serves it. The HeyGen Video 1 row is served through OpenRouter itself and is listed only where the OpenRouter switch names it. The Tencent-routed rows have the same pattern.

So the table says what the catalog code can serve, not what your key sees today. Read GET /v1/videos/models with your own key before you plan around a row; a model missing from that response is not available to you, whatever this table says.

curl https://api.sume.com/v1/videos/models \
  -H "Authorization: Bearer $SUME_API_KEY" \
  | jq -r '.data[].id'

What does Sume list that OpenRouter's listing does not?

Going the other way, several Sume ids have no counterpart in the 26. seedance-2-fast and veo-3.1 are absent from the listing as read. gemini-omni-flash-1.1, h3-max-recast and higgsfield-genjutsu are the other three, and the last two are not text-to-video at all: Recast swaps the people in a source video for the people in 1 to 4 photos, and Genjutsu moves a source video's motion onto 1 to 8 reference images.

Gemini Omni Flash 1.1 is the one most buyers want. It takes 3 to 10 seconds, native synced audio is always on, and it is the only Sume row with a video-edit mode through video_url.

How to use the table when a request fails

If you send an OpenRouter id to Sume, the docs say Sume never uses a provider-org prefix, so bytedance/seedance-2.5 is the wrong string and seedance-2.5 is the right one. Rows marked "none" fail for a different reason: there is nothing to rename. Pick the nearest row by capability instead, for example kling-3 where you used a Kling tier, or wan-3.0 where you used Wan 3.0 Prime, and test one short clip before moving traffic.

Duration and resolution limits differ per model on both sides, so a mapped id can still reject a request that its twin accepted. The companion post Same video id, different limits puts ten of the mapped ids side by side.