sume/auto or a pinned model for 30-second video on Sume
sume/auto defaults to 8 s clips of 3 to 10 s, so a 30-second job needs a pinned id: seedance-2.5 or wan-3.0. How the two paths differ.

Use a pinned model id for 30-second video. sume/auto has an Auto create range of 3 to 10 seconds with a default of 720p and 8 seconds, per the Video Router docs.
Auto is meant to hide the family choice; it never discloses which one ran. That makes it a good default for short clips and the wrong tool when you need 30 seconds or a specific model's behavior.
Side by side
| sume/auto | seedance-2.5 or wan-3.0 | |
|---|---|---|
| Duration | 3 to 10 s | 30 s possible |
| Defaults | 720p, 8 s | you choose |
| Who picks the model | Sume | you |
| Model shown in poll | sume/auto | the pinned id |
Pinning
Pinning costs nothing extra in code: change the model string. The docs recommend /v1/videos for new work over the older Video Router path.
{"model": "wan-3.0", "prompt": "Product spin on a white table", "duration": 30}What Auto does
Auto resolves from the normalized request and the catalog version, so an idempotent replay gets the same price and the same route. It never discloses the family, and the docs warn against inferring it from output traits.
That predictability is the strength; the limitation is length and control.
A routing habit that works
Use Auto for quick, short clips where any good model will do. Pin wan-3.0 for cheap long drafts and seedance-2.5 for the final long take.
Log the model alongside each job so you can compare cost and quality over time.
- Pinned: you control price per second.
- Auto: you save the decision.
- Both: same endpoint and polling flow.
Sources
Related posts
More in Developers
- SUME_API_AUTH_MODE: make the Sume CLI send Bearer instead of x-api-key
The Sume CLI sends x-api-key by default. Set SUME_API_AUTH_MODE=bearer when your client or network layer expects Authorization: Bearer. Never send both.
- Lost a 30-second video job after SSH died? Sume CLI recovery
There is no sume video subcommand, but the Sume CLI recovers any job you made through the API: jobs status, watch, result and download. Never resubmit.
- Sume Images API has no b64_json: turn data[].url into base64
POST /v1/images returns a Sume-hosted data[].url, not b64_json. Fetch the URL and encode it yourself; 202 means poll the job. Python example inside.
- No progress percent in Sume job events: what to log and show instead
Sume's job events are a public timeline of eight named events, not a progress feed. What each means, what to log, and what to show a user while a video renders.
Written by Sume