Sume video 404 model_not_found: valid model ids for /v1/videos

POST /v1/videos with a model that Sume does not know returns 404 model_not_found. The status is deliberate: Sume's API docs say it matches OpenRouter and every other place the platform reports an unknown model, so a client that handles one 404 handles all of them. The rule is that model must be a catalog id, a catalog alias, or sume/auto; anything else is not found.

Most 404s are a model that sounds real but is not in the catalog, not a typo. If you were expecting a vendor's newest name, check that it ships before you debug your code.

Which ids work today?

These are the catalog ids from the Video Router, which GET /v1/videos/models returns live. Copy them exactly, including the dot in wan-3.0 and gemini-omni-flash-1.1, and the hyphens in the others.

What are the common causes?

Four patterns account for most of them.

• A vendor-name or version that is not in the catalog, such as a model Sume does not list; Does Sume have Veo 3.1? covers one.
• Dropping the dot or hyphen: wan-3, wan3.0, minimax_h3 and gemini-omni-flash all fail.
• Using the human name from a UI, such as "Kling Video v3 Pro", as the id.
• Asking for higgsfield-genjutsu on an environment where its provider is not configured, so the row is not listed.

How do I check before I submit?

Fetch the list once and test membership, or ask for the single row at GET /v1/video-router/models/{model_id}, which also returns 404 for an unknown id. Cache the list for the life of your process; it changes when Sume ships a model, not per request.

Do not retry a 404. It will not start working, and unlike a 5xx it carries no balance hold, so there is nothing to clean up.