Sume auto or a pinned video model: what changes past 10 seconds
Auto video defaults to 720p and 8 seconds with 3 to 10 second clips. For 12, 15 or 30 seconds, 1080p or 21:9, pin a model id. How to decide on Sume.

Use sume/auto when a 3 to 10 second clip at 16:9 or 9:16 is enough, and pin a model id when you need more. The docs describe Auto's create controls as defaulting to 720p and 8 seconds, with 3 to 10 second clips at 16:9 or 9:16. A 15 or 30 second clip, a 21:9 frame or a specific reference setup is a reason to pin.
What Auto gives up
Auto's responses echo sume/auto and Sume does not disclose which family ran, so you cannot build a workflow that depends on one model's look. That is the point for a quick clip and a drawback for a series that needs consistency.
When to pin
The rest of the catalog is explicit pass-through: you choose the id, Sume validates the request against that model's envelope, and the receipt names the model.
| You need | Pin |
|---|---|
| 30 seconds in one clip | seedance-2.5 or wan-3.0 |
| 2-second clip | wan-3.0 |
| 4K output | gemini-omni-flash-1.1 |
| Edit an existing video with a prompt | gemini-omni-flash-1.1 with video_url |
| Reference audio | seedance-2.5, wan-3.0 or minimax-h3 |
| Always-on stereo audio, 1080p | minimax-h3-max |
Migrating
Auto is a model value on POST /v1/videos, so moving from Auto to a pinned model is one field. Keep your Idempotency-Key scheme per request so a retried submit returns the original job.
Sources
Related posts
More in Models
- Sume Image API n: 1 to 10 per call, lower per-model ceilings
The n parameter asks for 1 to 10 images in one POST /v1/images, but each model's catalog entry can set a lower ceiling. Cost is per image times n.
- Is Sume's kling-3 Kling VIDEO 3.0 or Omni 3.0? Read the catalog row
Sume's catalog names kling-3 'Kling Video v3 Pro' and lists no reference inputs. Kling describes Omni 3.0 as reference-driven, so match by capability.
- Sume Voices page lists 16 languages, Sonic 44: which list applies?
The Sume Voices page offers 16 languages when you create a voice; Cartesia states 44 for Sonic. The TTS request language field is a BCP-47 code you set per job.
- Tamil, Telugu, Kannada, Malayalam TTS API: language codes on Sume
Sonic 3.6 lists bn, ta, te, kn, ml, mr, gu and pa beyond Hindi. How to send each on Sume TTS, what the Hinglish note does not cover, and the cost per script.
Written by Sume