Model comparisons
At 768p, MiniMax H3 costs 70% less than MiniMax H3 Singularity LoRA. Tier prices, request fields and limits side by side.
MiniMax H3 image-to-video starts from your opening frame, with an optional closing frame and a prompt that directs the motion between them. Clips run 4 to 15 seconds with generated audio at 768p or 2k.
View model details →View sample outputs →MiniMax H3 Singularity LoRA image-to-video runs a community fine-tune of MiniMax H3 on your opening frame, with an optional closing frame and up to three of your own LoRAs. Clips run 3 to 15 seconds at 480p to 1080p with stereo sound.
View model details →View sample outputs →Compare
Start with the input you have, the result you want and your budget. These are the differences that affect that choice.
Compare the published examples, then try the same input on both models with matching settings.
The Spicy Index and Freedom Score for both models, from the same daily calculation as the leaderboards.
| Measure | MiniMax H3 | MiniMax H3 Singularity LoRA |
|---|---|---|
| Spicy Index | 78.0 | 73.6 |
| Freedom Score | 70.7 | 100.0 |
| Evidence | Tested 6 of 6 probe types · 48 runs | Tested 6 of 6 probe types · 38 runs |
| Range if the rest pass | 70.7–100.0 | 100.0–100.0 |
| Price | $0.185 per 5-second clip | $0.625 per 5-second clip |
| Reviews | Read the MiniMax H3 review | Read the MiniMax H3 Singularity LoRA review |
Preliminary · limited independent quality evidence
See both on the leaderboard →Current price
A start price answers a different question than the one you have. These are the tiers both models publish, matched setting for setting, in US dollars per billed unit with no conversion step in between.
Swipe horizontally to compare all fields.
| Tier | MiniMax H3 | MiniMax H3 Singularity LoRA | Difference |
|---|---|---|---|
| 768p | $0.037 / output seconds | $0.125 / output seconds | MiniMax H3 −70% |
Arithmetic on the published rates at each model's own default setting, not a quote. The console prices your actual settings before a request is accepted.
About this comparison
Every row here is read from the JSON Schema the endpoint validates against, so it matches what the API will really accept rather than a feature list written by hand.
Swipe horizontally to compare all fields.
| Controls and limits | MiniMax H3 | MiniMax H3 Singularity LoRA |
|---|---|---|
| Supported tasks | image-to-video | image-to-video |
| Clip length | 4–15 seconds | 3–15 seconds |
| Resolution tiers | 768p · 2K | 480p · 540p · 768p · 1080p |
| Audio output | Yes | Yes |
| High-resolution tier | Yes | Yes |
| Seed | No | Yes |
| Execution | Submit, then poll or take the callback | Submit, then poll or take the callback |
| Request timeout | 120 minutes | 60 minutes |
| Availability | Live | Live |
Do low-filter models allow every request?
Two separate facts sit behind these labels. The first is what we do, which is nothing: no platform content filter, and no maturity flag to set on a request. The second is what each model does on its own, and that is the only part that varies between these two.
MiniMax H3
This model declares no content filter. SpicyAPI forwards the request without adding a platform content scan; legal and consent duties remain with the customer.
MiniMax H3 Singularity LoRA
This model declares no content filter. SpicyAPI forwards the request without adding a platform content scan; legal and consent duties remain with the customer.
Use these content labels to shortlist models, then open each model page for available examples and content-test details.
The label never changes your obligations. Age, consent, real-person likeness and the law where you operate stay with you, and SpicyAPI does not inspect each request.
Can I swap the model ID without changing the request body?
The task lifecycle is shared; the body is not. Each endpoint publishes its own JSON Schema and the API validates against that, so this is the list to reconcile before a switch.
Compare
The model identifiers are minimax/h3/image-to-video and minimax/h3-singularity-lora/image-to-video, and both go in the same field of the same request.
Both run the same way: submit the task, then poll it or take the callback. Queueing and retry logic carry over unchanged.
Both use the same submit-and-track flow, but their required inputs may differ. Check each model page before switching.
One key, one balance, one set of spend caps. Both bill to the same account in US dollars, and the per-key daily, monthly and lifetime limits apply to whichever one you call.
Questions developers ask
MiniMax H3 is 70% cheaper at 768p, the closest like-for-like setting the two publish. Prices may change; check the estimate shown for your actual settings before submitting.
MiniMax H3 allows 120 minutes per task and MiniMax H3 Singularity LoRA allows 60. Those are ceilings rather than typical times — most requests finish far sooner — but they are what your own client timeout has to survive.
Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples.