google/veo-3.1 style ids vs Sume: bare video model ids

Sume video models use bare catalog ids such as seedance-2, never an org/slug id like OpenRouter's google/veo-3.1 example. A prefixed id is not a valid Sume model, so look up the bare id in the catalog.

How do the two id styles differ?

OpenRouter's page gives google/veo-3.1 as its example model. Sume's differences table says its published contract never carries a provider-org prefix.

What is sume/auto then?

It is the one prefixed value in the docs: a Sume-only addition that lets Sume pick the family. It is not a provider prefix.

How do I find the right id?

List the catalog and read the id field of each entry. The example returns seedance-2 with name Seedance 2.0.

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

What if the model I want is not listed?

The docs' troubleshooting notes for a model-not-found error say to use the model list and to verify the id is a bare catalog id. For Veo, see Veo 3.1 access and catalog alternatives and the video docs.

What else changes when I port a request?

Base URL, key and id are the main edits. size, seed and non-empty provider.options are rejected, and the webhook envelope is Sume's, signed with x-sume-webhook-signature.

Auto routing is a Sume addition: model: "sume/auto" lets Sume pick the family, and the response echoes sume/auto.