Luma modify video price: $0.60 vs $1.75 for a 720p 5-second clip

Luma's Modify Video page prices output by pixels: ray-2 costs $0.01582 per million pixels and ray-flash-2 costs $0.00544 per million pixels. Its example, a 5-second 720p 16:9 video, is $1.75 on ray-2 and $0.60 on ray-flash-2. Sume prices a video job in dollars per second by resolution and bills provider list times 1.25.

Luma's numbers

Luma gives the rates and one example. The ratio of the two prices, about 2.9, matches the ratio of the two examples. Working back from the example, $1.75 at $0.01582 per million pixels is about 110.6 million pixels, which is 120 frames of 1280 by 720. That frame count is my arithmetic from the page, not a figure the page states.

How Sume quotes it

Sume's video catalog returns pricing_skus per model, and a completed job returns usage.cost, the Sume billable amount. The workspace balance is reserved on submit, captured as actual cost on success and refunded on failure. For gemini-omni-flash-1.1, the Video Router docs say billing is provider list times 1.25 per output second by resolution.

Comparing like for like

To compare, price the same clip both ways. For Luma, take the pixel count of your clip, multiply by the rate and divide by a million. For Sume, read the pricing_skus on the model you pin, multiply by the seconds, and apply the times 1.25 rule if the catalog shows list price. Keep resolution fixed in both, or the comparison is meaningless.

• Fix the resolution and duration first.
• Price from the catalog, not from a blog post, including this one.
• Compare the captured usage.cost, not the reserved amount.
• Re-check both pages before a large run; vendor prices change.

Why the units differ

A per-pixel price scales with resolution and length together, so a long 1080p source costs much more than a short 720p one. A per-second price scales with length and the resolution tier.