MiniMax H3 or H3 Max: same 5 to 15 s, different 768p price

Pick minimax-h3 for the lower 768p price ($0.075 per second against $0.10) and minimax-h3-max when you need 1080p. Both take 5 to 15 seconds on Sume. Docs describe H3 Max as the faster 768p variant.

Side by side

Prices are per 10-second clip.

Decision rule

• Under 768p and price-led: minimax-h3.
• Need 1080p without a separate upscale step: minimax-h3-max.
• Both accept image, video and audio references, so references do not decide it.
• Need 2K or 4K: minimax-h3, with the upscale billed.

Switching

The request is identical apart from model, so you can run one prompt through both and compare.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: h3-compare-max" \
  -d '{
    "model": "minimax-h3-max",
    "prompt": "A barista pours latte art, slow push-in, warm window light",
    "duration": 5,
    "resolution": "768p"
  }'

What the price gap adds up to

At 768p, a 15-second clip is $1.13 on H3 and $1.50 on H3 Max. Across a hundred such clips that is $112.50 against $150.00.

The docs call H3 Max the faster 768p variant. If turnaround matters to your workflow, that can be worth the difference; if it does not, the lower price wins.

Sume reserves the full price at submit, so the number in the table is also the amount that must be free in the balance when you send the request. If it is not, the call fails with 402 insufficient_credits before any provider work starts.