H3 Max 1080p, 10 seconds: $1.84 before the margin change, $2.00 now

MiniMax H3 Max on Sume used to carry a smaller margin than the rest of the catalog, and no longer does: every row, minimax-h3-max included, now bills provider list times 1.25. A 10-second 1080p clip therefore costs $2.00 rather than the $1.84 the old times-1.15 rule would give. The catalog says so on the H3 Max entry, noting it sells at list times 1.25 like every row and that it was times 1.15 before the house margin was unified. The video generation docs repeat the rule in their billing row.

What did the change do to each price?

The table recomputes the three H3 Max resolutions both ways for a 10-second clip, from the catalog's list rates: $0.05 per second at 480p, $0.08 at 768p and $0.16 at 1080p.

Why was H3 Max different?

The catalog comment on the margin constant calls the house times-1.25 a rule on every row, and says H3 Max was the exception under an earlier decision. The effect for a buyer is that H3 Max stops being the model with a separate multiplier. You can compare it with Wan 3.0, Kling 3 or Omni on list price alone, because the same factor applies to all of them.

That matters for the 1080p comparison. At list, H3 Max is $0.16 per second and Wan 3.0 is $0.20, so the Sume ratio between them stays 0.8 whichever model you pick, and a 10-second 1080p clip is $2.00 on H3 Max against $2.50 on Wan.

What else did the catalog note change?

Two details from the H3 Max entry help you budget. The list rate in the catalog is dated 2026-09-08 and excludes a temporary launch promotion, so the figure you pay is the standard list, not a promotional rate. And reference-to-video on H3 Max is billed as output seconds at list times 1.25, with fal's reference-token overage not reserved, which means the reserve at submit is the simple per-second figure.

How do the three H3 Max tiers rank against the rest?

At 10 seconds and the current multiplier, H3 Max is $0.63 at 480p, $1.00 at 768p and $2.00 at 1080p. Against other Sume rows at the same length and 1080p, Kling 3 with audio off is $1.40, Gemini Omni Flash 1.1 is $1.88, Kling 3 with audio on is $2.10 and Wan 3.0 is $2.50.

So H3 Max at 1080p sits in the middle of the group, and its extra weight is in what it accepts: 9 reference images, 3 reference videos and 3 reference audio files, 21:9 framing and always-on stereo sound.

Does the change affect lip sync or Recast?

This post is about the Video Router row minimax-h3-max. The pricing code also has a separate H3 Max lip-sync table with the same per-second list rates, $0.05 at 480p, $0.08 at 768p and $0.16 at 1080p, and a separate H3 Max Recast row. Those are different catalog rows with their own docs, so read the entry for the id you call rather than assuming the Video Router figure carries over.

The house margin of 1.25 is stated in the Video Router docs as applying to every model in that catalog. If you run H3 Max in a batch, the number to track is the sum of per-clip rounded-up cents, because each clip is rounded on its own. Ten clips of 10 seconds at 1080p are $20.00 in total, ten times the per-clip price.

Do I need to change anything in my code?

No request field changed. Budgets that hard-code the old 1.15 factor are the only thing to fix, and the safest source is the catalog itself: each row carries billable_margin and a billable_formula string of the form list x 1.25 -> ceil usd cents. Read the margin from the row instead of storing a number, and compute ceil(list x margin x seconds) in cents for the clip.