MiniMax H3 Max on Luma: credits per second in dollars

Luma's pricing page lists MiniMax H3 Max at 18 credits per second at 480p, 28 at 768p and 56 at 1080p. A credit has no fixed dollar value; it depends on the plan, so the dollar figure is plan price divided by included credits. On Sume the unit is already dollars: $0.100 per second at 768p.

Luma numbers are from its pricing page, read 2026-10-01. Sume's billing rule is from the video generation docs.

What do 18, 28 and 56 credits per second come to in dollars?

The page shows three individual plans: Plus at $30 a month for 10,000 credits, Pro at $90 for 40,000 and Ultra at $300 for 150,000. Dividing price by credits gives a per-credit dollar rate for each, and multiplying by the credits per second gives the rows below. This is my arithmetic on the listed numbers, not a Luma quote; it ignores yearly billing and any extra credit packs.

What does Luma say about reference images?

The H3 Max row reads "Reference images: first 2-4 free, then ~7-13 credits each". The page does not say which count applies to which input, so check it before budgeting an image-heavy clip. The Sume side of that question is covered in MiniMax H3 extra reference images vs Sume reference types.

How does Sume bill the same clip?

Video jobs on Sume are charged from the workspace USD balance, reserved on submit at provider list times 1.25, and the docs say this holds for every model, minimax-h3-max included. usage.cost on the job is the Sume billable amount, so the number you see is dollars rather than credits to convert. The per-second figures in the table apply that multiplier to the list rate in code.

How do I check what a model supports before pricing it?

Call the catalog endpoint. The docs say it reports which resolutions, aspect ratios and durations each model supports, and each entry carries pricing_skus. For minimax-h3-max the docs list 480p, 768p and 1080p at 5 to 15 seconds, where 1080p is a latent refinement from native 768p. Multiply the per-second rate by the length you actually need, then compare it with your own plan arithmetic.