sume/auto video defaults: 720p, 8 seconds, 3 to 10 s at 16:9 or 9:16

Leave resolution and duration off a sume/auto video request and Sume uses 720p and 8 seconds. The Auto envelope is 3 to 10 seconds at 16:9 or 9:16.

3 min readSume
All posts

A sume/auto video request that omits resolution and duration runs at 720p and 8 seconds. The Video Router page states the Auto create controls: 3 to 10 second clips at 16:9 or 9:16.

What are the Auto controls?

These come straight from the Video Router page.

Auto create controls, read 2026-09-30. Source: https://docs.sume.com/models/video-router
ControlValue
Default resolution720p
Default duration8 s
Duration range3 to 10 s
Aspect ratios16:9 or 9:16

How do I send an Auto request?

Set model to sume/auto. The example asks for a 9:16 clip at 5 seconds and leaves resolution at its default.

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}'

What will the receipt say?

The poll response reports model: "sume/auto". Sume does not disclose the family that served it, and resolution is a pure function of the normalized request and the catalog version, so an idempotent replay routes and prices identically.

When should I pin instead?

Pin a catalog id when you need more than 10 seconds or a specific resolution: seedance-2.5 accepts 4 to 30 seconds. See the video docs and Auto or pinned.

How do I follow the job?

Video generation is asynchronous: submit, receive a job id and polling URL, poll until completed, then download from the content URL. The docs suggest a polling interval of about 30 seconds and say generation typically takes 30 seconds to several minutes depending on the model and parameters.

The same job is also visible at GET /v1/jobs/{id}/status and /result, so an agent can use either vocabulary.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume