Seedance 1.5 Pro retires Nov 11: pin a live Sume model id

The ElevenLabs changelog dated Sep 23, 2026 says ByteDance is retiring Seedance 1.5 Pro on November 11, 2026. The safest response is to stop hard-coding any model id and instead choose one from GET /v1/video-router/models, which lists what Sume currently serves. seedance-2.5 is listed and accepts 4 to 30 seconds.

Why pin from the catalog

Any integration that sends a fixed model id breaks when that id is withdrawn. Catalog ids on Sume are bare slugs such as seedance-2 and seedance-2.5, and each model advertises its own durations, resolutions and input types. Read those from the catalog rather than copying numbers from a blog post.

The Sume docs state these limits for the Seedance family:

A migration routine

The Sume docs do not mention a Seedance 1.5 id. If your code sent a 1.5 Pro id to another provider, map it to a catalog id here and re-test your prompts, because look and motion differ between model generations.

Keep the model id in configuration, not in code, and fail loudly when the catalog no longer lists it.

• List the catalog and filter for the id you use
• Compare supported_durations, resolutions and reference types with your requests
• Run one test job per prompt template on the new id
• Switch the configured id, then watch usage.cost on the first jobs

List the current catalog and confirm an id exists before each release:

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

curl https://api.sume.com/v1/video-router/models/seedance-2.5 \
  -H "Authorization: Bearer $SUME_API_KEY"