Why sume/auto returns 400 for 21:9, not a Seedance route
sume/auto accepts 3 to 10 s in 16:9 or 9:16. Ask for 21:9 or 15 s and you get 400 unsupported_capability, not a quiet reroute to Seedance.

A common surprise: you send model: "sume/auto" with aspect_ratio: "21:9" and get a 400, even though Seedance on Sume accepts 21:9. This is deliberate. Sume's contract says sume/auto has its own capability envelope and fails closed instead of changing models behind your back.
What auto accepts
| Field | Accepted | Rejected with 400 |
|---|---|---|
| duration | 3 to 10 s (default 8) | 2 s, 11 s, 15 s |
| resolution | 360p, 720p, 1080p, 4K (default 720p) | 480p, 768p |
| aspect_ratio | 16:9, 9:16 | 21:9, 1:1, 4:3 |
| generate_audio | true or omitted | false |
Why it fails closed
The resolution of sume/auto is a pure function of the request and the catalog version. There is no load balancing and no A/B, so an idempotent replay gets the same route and the same price. If it quietly picked Seedance for 21:9, the price would change under you: a 10-second 720p Seedance 2.5 clip is $5.78 on Sume, and the price of an auto clip is not that number.
What to send instead
- For 21:9 or any length from 11 to 30 seconds, name the model:
seedance-2.5takes 4 to 30 s and 21:9. - For up to 10 seconds in 16:9 or 9:16, keep
sume/auto. - The error names
sume/auto, not the resolved model, and itssupportedlist shows the values that are accepted.
{
"model": "seedance-2.5",
"prompt": "A wide shot of a coastal road at dusk",
"duration": 12,
"resolution": "720p",
"aspect_ratio": "21:9"
}
Sources
Related posts
More in Developers
- sume/auto vs a pinned video model: three jobs where each wins
sume/auto is right for an 8-second 720p clip at $1.00. A 12-second or 20-second clip needs a pinned id, because auto resolves to Omni with a 10-second cap.
- Sume CLI avatar-videos batch: plan, create, watch, result
The Sume CLI batches avatar videos in four steps against local state files. What each step does, and why the per-item idempotency key makes reruns safe.
- Sume CLI quickstart: create an avatar video, follow it with jobs
Install the Sume CLI, log in, create a paid avatar video, and follow the job with sume jobs status, result and events. Why Image and Video have no CLI command.
- Map the Sume error envelope to RFC 9457 problem details in 15 lines
RFC 9457 defines type, status, title, detail and instance. Sume's error.code, message and request_id map onto them; keep the retry fields as extensions.
Written by Sume