Video 1.0 4k resolution error: only 720p and 1080p on that URL

POST /v1/video-1.0/generate accepts 720p (the default) and 1080p, and it rejects 4k. For 4K, the docs say to use POST /v1/videos with sume/auto.

What resolutions does Video 1.0 take?

The field is validated against the Auto serving family, using the legacy vocabulary.

How do I request 4K?

Send sume/auto to /v1/videos with a resolution the model list advertises.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: auto-4k-001" \
  -d '{"model":"sume/auto","prompt":"A slow aerial over a city at dusk","resolution":"4K","aspect_ratio":"16:9"}'

Which pinned model lists 4K?

The docs list gemini-omni-flash-1.1 at 360p, 720p, 1080p and 4K in 16:9 or 9:16 for 3 to 10 seconds. Read supported_resolutions before you submit.

Why does the enum list 1K, 2K and 4K?

The video docs enumerate 480p, 720p, 768p, 1080p, 1K, 2K and 4K, and say each model advertises the subset it accepts. Details are in the video docs.

What does 4K cost to try?

Billing is reserved on submit at provider list times 1.25, and the poll response reports usage.cost as the Sume billable amount. Sending an Idempotency-Key makes retries safe, because a replay returns the original job.

The docs note that higher resolutions take longer to generate and cost more, and advise choosing the resolution that fits your use case.