Luma Ray3.2 video-to-video costs 4.8x text-to-video at 540p

Luma's API pricing page lists Ray3.2 text- and image-to-video at $0.15 for 5 seconds at 540p, and video-to-video at $0.72 for the same length (Luma pricing, read 2026-10-09). Editing an existing clip costs 4.8 times generating one at 540p, and 1.8 times at 1080p. On Sume, an Omni edit bills the same per-second rate as generating.

What does Luma list for Ray3.2?

Why is editing the dearer path on Luma?

The page does not say. What the numbers show is that the premium shrinks with resolution: at 540p a 10-second edit is $1.08 against $0.45 to generate; at 1080p it is $4.32 against $3.60. Plan edit-heavy workflows at the lower resolutions and finish the keepers.

What does an edit cost on Sume?

Sume lists no Luma id (catalog read 2026-10-09). Its edit path is gemini-omni-flash-1.1 with video_url. The price is the provider list times 1.25 per output second by resolution, and the estimator reserves 8 output seconds when the request gives no length. At the default 720p that reserve is 8 x $0.125 = $1.00. The Video Router docs say the prompt gives the edit instructions and that resolution is optional.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: edit-001" \
  -d '{"model":"gemini-omni-flash-1.1","prompt":"Replace the bottle with an apple. Keep everything else the same.","video_url":"https://example.com/clip.mp4","resolution":"720p","mode":"async"}'

How do the two compare for a 5-second fix?

On Luma, 5 seconds at 720p is $1.44. On Sume, 5 output seconds at 720p is $0.625; an edit request carries no length, so the reserve is sized on 8 seconds ($1.00). The tools differ in what they edit and how: check a frame pair before you commit to either.