Need production access now?
Start with Hailuo 2.3 Standard for current text-to-video and image-to-video work. Use a route whose model ID, billing, and task behavior can be tested.
Compare MiniMax H3, Hailuo 2.3 Standard and Fast, and Hailuo 02 inside one aggregation platform by generation mode, current API access, iteration speed, accepted-output cost, and fallback strategy.
MiniMax H3 is the next-generation Hailuo video route. EvoLink exposes it as three model IDs — text-to-video, image-to-video with first and last frame control, and reference-to-video — billed per output second with 2K output and 4-15 second durations.
Choose by verified access and workflow first. Exact live pricing remains on each available model page.
| Model | Status | Documented modes | Documented output | Best current use | Next step |
|---|---|---|---|---|---|
MiniMax H3 Next generation | Available on EvoLink as three routes | Text-to-video, image-to-video (first/last frame), reference-to-video | 2K at 4-15s, MP4, billed per output second | Reference-guided work and first/last-frame control at 2K | Open MiniMax H3 API |
Hailuo 2.3 Current generation | Available on EvoLink | Text-to-video and image-to-video | 768p at 6/10s; 1080p at 6s in MiniMax docs | Quality-first MiniMax video generation | Open Hailuo 2.3 API |
Hailuo 2.3 Fast Faster iteration | Available through the Hailuo 2.3 page | Image-to-video | Variant limits shown in the current model workflow | Faster image-to-video drafts and iteration | Select Hailuo 2.3 Fast |
Hailuo 02 Previous family route | Available on EvoLink | Text-to-video, image-to-video, first/last-frame workflows | 512p, 768p, and 1080p options on current route | Existing integrations and first/last-frame control | Open Hailuo 02 API |
A new version number is not a migration reason by itself.
Start with Hailuo 2.3 Standard for current text-to-video and image-to-video work. Use a route whose model ID, billing, and task behavior can be tested.
Choose Hailuo 2.3 Fast on the same family page, then measure accepted-output cost rather than latency alone.
Keep Hailuo 02 where its existing first/last-frame workflow is already integrated and meets quality targets.
Run your real prompts and source assets on the live route, then compare identity consistency, first-pass acceptance, queue time, and accepted-output cost against Hailuo 2.3 before you migrate.
Use Hailuo 2.3 as the current control. Score motion, camera adherence, physical plausibility, artifacts, and acceptance across every attempt.
Compare Standard and Fast under the same source image, duration, resolution, prompt, queue, and review rubric.
Treat MiniMax H3 as the challenger route: check per-second cost including reference video seconds, failed-task refunds, callbacks, and retention, then canary by workload and keep a tested fallback.
EvoLink lets teams compare Hailuo, Seedance, Kling, and other video routes under one account while preserving model-specific parameters and task rules. The advantage is not model count; it is whether each choice can be called, billed, observed, and safely rolled back.
Official 2K samples with full prompts, plus a browser playground with 10 free credits.
Prompt examples for all three routes, each with its result video, input requirements and constraints.
Confirmed facts, unverified claims, and the checks used before the route opened.
Plan an evidence-based same-family upgrade.
Compare two multimodal video routes with documented reference inputs.
Compare availability, native audio, duration, operations, and cost evidence.
MiniMax H3 is the newest generation and is callable on EvoLink as three model IDs. Hailuo 2.3 remains the per-video baseline for comparison.
MiniMax H3, Hailuo 2.3, Hailuo 2.3 Fast, and Hailuo 02 all have current routes. Pick MiniMax H3 for 2K output, reference inputs, and per-second billing.
Hailuo 2.3 Standard covers text-to-video and image-to-video; MiniMax positions Hailuo 2.3 Fast as an image-to-video route for faster iteration.
Yes. MiniMax H3 is billed per second of output video at a single 2K rate, and reference video seconds are added to the billable duration. The MiniMax H3 page shows the current rate for your user group.
No. Output is 2K with durations of 4 to 15 seconds, and there is no upstream cancel endpoint. Failed, expired, and rejected tasks are refunded in full.
Only after matched quality, reliability, latency, accepted-output cost, compatibility, and rollback tests pass for your workload.