MiniMax H3 regeneration to 2K re-bills the original inputs

On MiniMax's pay-as-you-go page, regenerating a 768P H3 video into 2K is billed per second of the regenerated output, and the input materials from the original 768P task are billed again. A 2K upgrade is therefore a second charge, not a free re-render. On Sume, minimax-h3 is native 480p/768p and the docs say 2K/4K upscales are priced if requested.

What does MiniMax charge for a 768P to 2K regeneration?

The page lists a MiniMax-H3-Regeneration row for 768P to 2K, plus three input rows that repeat the original task's materials.

Why do the original inputs count twice?

The page states that the input materials used in the original 768P generation task will be billed again. If the first render used a long reference video or many reference images, the 2K pass repeats those lines. Add them to your estimate before you regenerate.

What does a 2K request reserve on Sume?

Sume does not expose a separate regeneration product in the sources read here. The video docs say minimax-h3 accepts 5-15 seconds at native 480p/768p and that 2K/4K upscales are priced if requested. Billing is the workspace USD balance, reserved on submit at provider list x 1.25, minimax-h3-max included. The Video Router page says the same: Sume bills list x 1.25 on every model.

Read the reserved amount from the job rather than computing it by hand, and see MiniMax H3 2K video API for the resolution options.

What happens if the job fails?

Sume's generation admission page says failed jobs and failed queue admission release or refund the reservation where applicable. Compare that with do failed AI video jobs cost money before relying on it for a specific case.