Sume Auto video defaults: 8 seconds, 720p, 3 to 10 second range

sume/auto lets Sume pick the video family. Defaults are 720p and 8 s, with 3 to 10 s clips at 16:9 or 9:16. The legacy Video 1.0 URL rejects 4K.

5 min readSume
All posts

sume/auto is the Sume model that picks the video family for you. Its create controls default to 720p and 8 seconds, with clips of 3 to 10 seconds at 16:9 or 9:16, per the Sume Video Router docs as of 2026-10-08. Sume does not disclose which family served a request, and an idempotent replay gets the same price and the same route.

Send it on POST /v1/videos as model: "sume/auto". The poll response reports sume/auto, not the family that ran.

Auto and Video 1.0 limits from the Sume docs (as of 2026-10-08)
SettingValue
Default resolution720p
Default duration8 s
Clip range in Auto create controls3 to 10 s
Aspect ratios in Auto create controls16:9 or 9:16
Video 1.0 legacy URL resolutions720p (default) and 1080p; 4k rejected
Video 1.0 generate_audiodo not send; the Auto family always generates audio
Video 1.0 bitrate_moderejected
routing_preset (cost, speed, quality, grok, kling)deprecated; ignored; all use Auto

What stays pinned in the request

Because resolution is a pure function of the normalized request and the catalog version, the same body gets the same price and route on a replay. Send an Idempotency-Key; a replay returns the original job. For 4K you must use POST /v1/videos with sume/auto: the legacy /v1/video-1.0/generate URL rejects 4k.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: auto-001" \
  -d '{"model":"sume/auto","prompt":"A vertical UGC-style product clip on a desk, natural light","aspect_ratio":"9:16","duration":5}'

Auto or a pinned model

Pin a model when you need a specific envelope: 30 seconds (Seedance 2.5 or Wan 3.0), 21:9 (Seedance or MiniMax), a 2-second clip (Wan 3.0), or an edit (Gemini Omni Flash 1.1). Use Auto when a 3 to 10 second vertical or horizontal clip is all you need and you do not care which family makes it.

A pinned model also gives a price you can compute in advance. For a 5-second clip at 720p: Wan 3.0 $0.625, Gemini Omni $0.625, Seedance 2.0 Fast $1.512. The price of an Auto request is set by the resolved family and the Sume catalog, and is not shown as a family.

Pitfalls

If a request needs to land on a given family, do not use Auto. Auto is a convenience route and its family is not exposed, so no test of Auto can tell you which model ran.

  • Do not send generate_audio on the Video 1.0 route; the current Auto family always generates audio.
  • Do not rely on routing_preset; Sume accepts the retired values and ignores them.
  • Do not parse artifact URLs for provider or family identifiers; they are opaque.
  • Expect usage.cost to be the billable amount, with Sume reserving provider list times 1.25 at submit.

Migration note

Video 1.0 (sume/video-1.0) is a compatibility alias for Video Router Auto and Sume will retire it. The legacy URLs keep their request shape, but they use the same Auto selection and prices. New integrations should use POST /v1/videos.

  • Replace /v1/video-1.0/generate with /v1/videos.
  • Replace image_url with a first_frame entry in frame_images.
  • Drop routing_preset, bitrate_mode and generate_audio.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume