Luma Ray 3.2 features and the Sume endpoint for each one

Sume does not run Luma Ray 3.2: it is not in the Sume video catalog, so you cannot call it here. If you came for what Ray 3.2 does, the closest Sume equivalents are first and last frames on catalog models, clip chaining, the Timeline API for multi-shot assembly, and video filter and trim for reframing and cuts.

This page maps each Ray 3.2 feature that Luma lists to the Sume surface that covers part of it, and says where there is no match. Ray 3.2 facts come from Luma's launch page; Sume facts come from the Sume docs.

What Luma lists for Ray 3.2

Luma's launch page for Ray 3.2 (dated 2026-06-09) lists up to 16 keyframes per clip, 1080p, clips up to 20 seconds, native HDR with 16-bit EXR export, facial performance tracking for up to 8 faces, a Reframe feature, and a full control surface through its API.

None of that is a statement about Sume. It is the checklist we use below.

Feature map

Keyframes: two frame types, plus chaining

On POST /v1/videos, the frame_images array takes entries with a frame_type of first_frame or last_frame. Whether a model accepts them is listed in supported_frame_images on GET /v1/videos/models. That gives you a start and an end image for one clip.

To go beyond two anchors, generate clip one, extract its final still with video frames, and send that still as the first_frame of clip two. Each link is a separate job, so every hop is a separate bill.

Length and resolution

Limits differ by model. The docs state that seedance-2.5 accepts 4-30 seconds at 480p, 720p and 1080p, wan-3.0 accepts 2-30 seconds, and each other catalog model has a ceiling of 15 seconds. Gemini Omni Flash 1.1 (gemini-omni-flash-1.1) is 3-10 seconds at 360p, 720p, 1080p or 4K. So a 20-second single take exists on Sume only on the 30-second models.

Reframe, assembly and edits

For a 16:9 to 9:16 change, video filter takes a crop as fractions of the frame (x, y, width, height), and the Timeline API places the result in a 1080x1920 canvas with cover, contain, stretch or blur fit. Timeline also joins up to 200 video slots into one MP4. For a prompt-driven edit of an existing clip, Gemini Omni Flash 1.1 accepts a video_url through the Video Router.

None of those steps invents a model. Each runs ffmpeg on a Sume worker or a catalog model you pin by id.

What to tell a client who asked for Ray 3.2

Say plainly that Sume does not run it, then offer the Sume path: pick a catalog id, anchor the first and last frame, chain for length, assemble in Timeline, and deliver MP4. If the brief needs HDR or EXR delivery, Sume's docs do not describe either, so treat that part as out of scope here.

Check the catalog before you plan

Catalogs change, so do not rely on this page for the live list. GET /v1/videos/models returns every video model with its supported_durations, supported_resolutions, supported_aspect_ratios, supported_frame_images, supported_input_references and generate_audio. If a name you want is not in that list, Sume does not run it. Ray 3.2 is not in it.

Pricing follows one rule across the catalog: Sume bills the provider list times 1.25, reserves it at submit, and reports the billable amount as usage.cost on the poll response. The docs do not publish a flat price for each model on the page, so read pricing_skus per model instead of quoting a number from memory.