Ray 3.2 API aspect ratios and resolutions, and Sume's lists

Per Luma's model guide, Ray 3.2 video accepts six aspect ratios (9:16, 3:4, 1:1, 4:3, 16:9, 21:9) at 540p, 720p or 1080p, for 5s or 10s. Sume does not publish one list for every model: each video model advertises its own subset in supported_aspect_ratios and supported_resolutions, so read the catalog entry before you send a ratio.

What does Luma list for Ray 3.2?

Why not one list for everything?

Luma's guide says aspect ratios are model-and-type-dependent: the shared enum has twelve members, but no single (model, type) pair accepts all twelve. Ray 3.2 video takes six. The same applies on Sume, where the video docs name nine documented ratios, including 21:9 "Ultra-wide", then add that "each model advertises the subset it accepts in supported_aspect_ratios".

How do I size a Sume video request?

Use resolution plus aspect_ratio. Resolution values in the docs run from 480p to 4K, again limited per model by supported_resolutions. Do not send size: every v1 model reports supported_sizes: null, so size returns 400 unsupported_parameter.

curl -X POST "https://api.sume.com/v1/videos" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"seedance-2","prompt":"A slow dolly shot through a misty greenhouse","resolution":"720p","aspect_ratio":"21:9"}'

What should I check before sending a ratio?

Read the model's supported_aspect_ratios from the catalog, and treat a ratio listed in the general docs as a vocabulary, not a promise for that model. For Luma's own clip-length limits against Sume's catalog, see Ray 3.2 20-second 1080p.