13-second clip: MiniMax H3 768p $0.98, H3 Max $1.30 or $2.60 at 1080p

A 13-second clip costs $0.975 on MiniMax H3 at 768p, $1.30 on H3 Max at 768p and $2.60 on H3 Max at 1080p. Thirteen seconds is inside both models' 5 to 15 s range.

Prices on this page are Sume list prices as of 2026-10-08: the provider list price times 1.25, computed from Sume's pricing package and billed per output second, linear in duration inside each model's valid range. The model ids, ranges and input types come from the Video generation docs and the Video Router docs; the per-second numbers can be cross-checked in the public catalog.

Arithmetic

13 s × $0.0625 = $0.8125 at 480p on H3; 13 s × $0.075 = $0.975 at 768p on H3.

On H3 Max: 13 s × $0.0625 = $0.8125, 13 s × $0.10 = $1.30 and 13 s × $0.20 = $2.60.

What the extra money buys

The docs call H3 Max the faster 768p variant. It adds text-to-video, first/last-frame image-to-video and reference-to-video with image, video and audio references, and 1080p, which they describe as a latent refinement from native 768p, not a native 1080p render. H3 runs native 480p and 768p; 768p is first-class and not 720p.

For a 13 s clip the 768p premium of H3 Max over H3 is $0.325 ($0.325). If you need an end frame, the docs name H3 Max for start/end frames; for H3, check supported_frame_images on GET /v1/videos/models.

Scaling this plan up or down

As a yardstick, the plan above is built on MiniMax H3 Max at 1080p, $0.20 per second. Each extra 5 seconds adds $1.00, a further $10 of budget buys 50 more whole seconds, and the largest single job the model accepts (15 s) holds $3.00 at submit. The shortest one (5 s) holds $1.00.

Those three numbers are enough to rescale the plan without a new table. If the plan doubles, double the totals; if a clip is shortened, subtract the seconds multiplied by the rate; and if the tier changes, swap the rate for the one in the tables above.

• Per second: $0.20
• Per 5 s: $1.00
• Per 10 s: $2.00
• Per 30 s or the model maximum (15 s): $3.00

Check the model's fields first

Before a run, ask GET /v1/videos/models for the model and compare three fields with your plan: supported_durations (every clip length must be listed), supported_resolutions (the tier must be listed, since MiniMax H3 has 768p and no 1080p, and Omni has 360p and 4K) and supported_aspect_ratios. A request outside those lists fails at validation, so the failure costs nothing, but a plan built on a wrong assumption costs a rewrite.

Submitting

Submit through POST /v1/videos with model, prompt, duration in whole seconds and resolution; read GET /v1/videos/models first, because supported_durations and supported_resolutions differ per model. Sume reserves the price at submit and usage.cost on the poll response is the billable amount, so the figures here are what leaves the balance. Neither model accepts a duration under 5 s.