MiniMax H3 vs H3 Max on Sume: clip price by length, 480p and 768p

MiniMax H3 (minimax-h3) and MiniMax H3 Max (minimax-h3-max, the faster 768p variant) both bill by the second on Sume at a rate set by resolution. The table gives both prices at 480p and 768p for every clip length these posts priced.

Worked example: MiniMax H3 vs H3 Max for a 10-second clip: 480p and 768p

For a 10-second clip, MiniMax H3 (minimax-h3) costs $0.6250 at 480p and $0.75 at 768p on Sume, and MiniMax H3 Max (minimax-h3-max, the faster 768p variant) costs $0.6250 at 480p and $1.00 at 768p.

Both accept 5 to 15 seconds. Their envelopes come from the video generation docs, read 2026-10-06: H3 is native 480p/768p (768p is first-class, not 720p), and H3 Max adds a 1080p option that is a latent refinement from native 768p.

How do the two compare at this length?

Prices are the provider list price times 1.25, computed from the rate card.

When is the cheaper one enough?

Use the cheaper model for storyboard passes and pick one for the final. Both do text-to-video; H3 Max also does first/last-frame image-to-video and reference-to-video with image, video and audio references.

curl -X POST "https://api.sume.com/v1/videos" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: clip-minimax-h3-max-10s-001" \
  -d '{
    "model": "minimax-h3-max",
    "prompt": "A product on a desk, slow push-in, natural light",
    "duration": 10,
    "resolution": "768p",
    "aspect_ratio": "9:16"
  }'

Every clip length in one table

This page replaces 8 posts that asked the same question with different numbers. Each row is one of them, with the answer it gave when it was published.