MiniMax H3 defaults to 2K at MiniMax; on Sume the default is 768p

MiniMax's own H3 announcement, dated July 31, 2026, says the model produces clips of up to 15 seconds with 2K as the default resolution, 768p also supported and native stereo sound. On Sume, minimax-h3 works differently by default: its public resolutions are native 480p and 768p, the product default is 768p, and Sume bills 2K or 4K upscales only if your request includes them. If you port a MiniMax call to Sume and leave resolution out, you get 768p, not 2K.

What each page says

The MiniMax page makes relative price claims against other models, which we do not repeat. It also says open weights are planned.

Sume's video guide says minimax-h3 accepts 5 to 15 seconds at native 480p or 768p, that 768p is first-class and not 720p, and that Sume bills 2K or 4K upscales if your request includes them. H3 Max is a separate Sume row for 480p, 768p and 1080p.

Pin the resolution explicitly

Never depend on a default when a model's default differs between providers. Set resolution in every request so the price and the output size are what you planned. A 10-second clip at 768p is $0.75 on Sume; the same clip at 480p is $0.63 after rounding up to the cent.

Steps:

• Decide the delivery size first: 768p is enough for most vertical social clips.
• Send resolution in the body, as 768p, never as 720p.
• Check the 2K and 4K rates in the catalog before you request them; they are priced higher.
• Keep minimax-h3-max in mind if you need 1080p.

{
  "model": "minimax-h3",
  "prompt": "A paper boat crosses a rain puddle, macro, shallow focus",
  "resolution": "768p",
  "duration": 10,
  "aspect_ratio": "9:16"
}

When a default matters

Defaults hide in two places: cost and size. A pipeline that expects 2K frames will break a crop or compositing step when it receives 768p files, and a budget built on a 768p rate will be wrong if someone later asks for an upscale. Write the resolution into your request template, and record which tier each batch used.

If you need native 1080p from the H3 family on Sume, the catalog row for minimax-h3-max lists 480p, 768p and 1080p, at $0.0625, $0.10 and $0.20 per second. Its 1080p is described in the docs as a latent refinement from 768p, so judge a sample before committing a batch.

Checking your own call

Fetch the row with GET /v1/video-router/models/minimax-h3 and read its capabilities before you hard-code anything. The row shows the resolutions and durations the API will accept, and an unsupported value returns an error rather than a silent downgrade.

What Sume does not do

Sume does not default to 2K for H3 and does not endorse the cost comparisons MiniMax makes against other models. Through Sume you pay the per-second rate above.