Model type
Video generation
Designed for fast text-to-video and image-to-video generation.
Generate 5–15 second clips from text or a first frame with an optional last frame. Use 480p for drafts and 768p for selected takes, with per-second pricing and one EvoLink API key across video models.
Test MiniMax H3 Max Turbo output, estimate credits, and pick the model ID that matches your input type before wiring the API into your product.
Create a Sample
Pick a route, enter your prompt, and set the parameters.Results are kept for 24 hours — download anything you want to keep.
Both routes are billed per output second. 480p costs 5/8 of the 768p rate, and the playground shows the live price before you generate.
One 5s 480P sample
About 80 tests with $10 in credits.
The first test uses the cheapest visible route at 480p for 5s, with a first frame if required. Omitting quality defaults to 768p.
Good for a first validation.
Good for prompt and shot iteration.
Good before production integration.
Estimates use the current per-second rate for your user group. Duration is rounded up to whole seconds, exactly as the task reports it.
| Mode | 480P | 768P | Billing |
|---|---|---|---|
| Text-to-VideoStandard route | $0.024/s-5% 1.615 cr/s$0.025 official price | $0.038/s-5% 2.584 cr/s$0.040 official price | Output video seconds |
| Image-to-VideoStandard route | $0.024/s-5% 1.615 cr/s$0.025 official price | $0.038/s-5% 2.584 cr/s$0.040 official price | Output video seconds |
Billed per second of output video. Input frames are never charged separately — MiniMax H3 Max Turbo accepts at most a first and a last frame, which stay inside the included allowance.
Minimum charge per task equals the cheapest valid request (480p x 5s). Failed, expired, and rejected tasks are refunded in full.
Choose MiniMax H3 Max Turbo on EvoLink for 480p or 768p clips from text or a first frame, with an optional last frame. Choose H3 Max when the shot needs image, video or audio references, and H3 when it needs 2K. All three use the same EvoLink API key and balance; their model IDs and input limits differ.
Capabilities below describe the routes currently available on EvoLink. Other providers may expose different resolutions or inputs. Use each model’s pricing section for current rates.
| Feature | MiniMax H3 Max Turbo | MiniMax H3 Max | MiniMax H3 |
|---|---|---|---|
| Primary role | Text and first/last-frame clips | Clips guided by reference media | 2K output and reference workflows |
| Generation modes | T2V + I2V (first/last frame) | T2V + I2V + R2V | T2V + I2V + R2V |
| Reference input | Not on current EvoLink routes | Image + video + audio | Image + video + audio |
| Resolution | 768p / 480p | 480p / 768p | 2K / 768p |
| Duration | 5-15s | 5–15s | 4-15s |
| Billing | Per output second | Output seconds + applicable reference input fees | Per output second (+ reference video seconds) |
Each generation mode is its own model ID behind the same API key and credit balance - pick the route that matches your input.
minimax-h3-max-turbo-text-to-videoGenerate 768p or 480p video from a text prompt.
minimax-h3-max-turbo-image-to-videoAnimate a required first frame with an optional last frame.
Choose a route and output tier based on the input and delivery requirements of your workflow.
Video generation
Designed for fast text-to-video and image-to-video generation.
Text, first frame, last frame
Turbo supports text and first-frame image input, with an optional last frame. For reference media, use MiniMax H3 Max: minimax-h3-max-reference-to-video.
minimax-h3-max-turbo-text-to-video / -image-to-video
MiniMax-H3-Max-Turbo is the upstream model name in the supplied API contract. EvoLink exposes two complete route-specific IDs for text and frame inputs through one video endpoint and credit balance.
768p / 480p, 5-15s, MP4
On EvoLink, omitting quality defaults to 768p. The current Turbo routes accept 480p or 768p and 5–15 seconds; other providers’ settings do not apply to these model IDs.
Per output second, 480p and 768p tiers
EvoLink bills each output second through the shared credit balance. 480p costs 5/8 of the 768p rate.
Async submit, poll or callback, no cancel
Tasks report pending / processing / completed / failed. Cancellation is not available, so failures refund instead.
These fields cover the main integration decisions. Open the API Reference for route-specific request and response examples.
modelstringChoose the text or image EvoLink model ID that matches your input.
Default: route-specific
promptstringDescribe the scene, motion, and camera behavior in up to 7000 characters.
Default: required
durationintegerSet 5 through 15 output seconds (4-second clips are not supported); billing follows the output duration.
Default: 5
qualityenumSelect 480p or 768p. 480p is billed at 5/8 of the 768p per-second rate; there is no 2K tier.
Default: 768p
aspect_ratioenumText-to-Video only: 16:9, 21:9, 4:3, 1:1, 3:4, or 9:16. Image-to-Video follows the input frames.
Default: 16:9
image_startstringImage-to-Video: required HTTP(S) URL of the first frame.
Default: required (I2V)
image_endstringImage-to-Video: optional last-frame URL; a first frame is required.
Default: optional
callback_urlstringPublic HTTPS URL that receives the final task state; keep the task ID as a polling fallback.
Default: optional
Use the EvoLink API for product integration and batch jobs, or call it from Codex, Claude, or Gemini for fast creative and development workflows. Both paths share the same EvoLink API key, balance, model routes, and task history.
Best for: product backends, batch jobs, automated workflows
Call EvoLink’s unified video API from your server and control the model ID, parameters, task queue, callbacks, and result storage.
Best for: creative and development tasks in Codex, Claude, and Gemini
Give the Agent your output goal, assets, and acceptance criteria. It can choose the route, assemble the request, track the task, and return the result without requiring you to hand-code every step.
Choose the input first, then set duration and quality. These are suggested workflows, not measured speed or quality results.
This example shows the shortest runnable flow: create a task, save the returned task ID, then poll or wait for an HTTPS callback. Open the API tab for the complete parameter and response reference.
curl -X POST https://api.evolink.ai/v1/videos/generations \
-H "Authorization: Bearer $EVOLINK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "minimax-h3-max-turbo-text-to-video",
"prompt": "A female captain before a vast observation window as the fleet jumps away, cinematic slow dolly-in",
"duration": 5,
"quality": "768p",
"aspect_ratio": "16:9",
"callback_url": "https://your-domain.com/webhooks/video-task-completed"
}'
# Save the returned task ID, then query:
curl https://api.evolink.ai/v1/tasks/{task_id} \
-H "Authorization: Bearer $EVOLINK_API_KEY"Check every value against the parameter cards above: ranges, allowed options, asset counts, and file types must match the selected route.
Check the Authorization bearer token and confirm the available balance and task billing in the console.
Review likeness rights, brand assets, readable text, sensitive content, and input-asset compliance.
A MiniMax H3 Max Turbo task that reaches a final failed state is not charged. Keep the task ID, inspect the final state, and identify whether the cause is validation, review, or execution before retrying.
callback_url must be a public HTTPS URL, not localhost or a private network address. Always keep the task ID as a polling fallback.
Choose H3 Max Turbo for fast 480p / 768p iteration; switch routes when you need higher resolution or broader reference inputs.
Text-to-Video: minimax-h3-max-turbo-text-to-video. Image-to-Video: minimax-h3-max-turbo-image-to-video. Animate a required first frame with an optional last frame.
Create the task once, then poll its status or receive a callback until the MP4 is ready. Result URLs remain available for 24 hours, so copy completed videos to your own storage as part of the delivery flow.
Use 480p for lower-cost drafts and 768p for higher-definition output. Failed, expired, and rejected tasks are refunded; the same API key and balance let you route 2K or broader reference jobs to MiniMax H3.
See credits and per-second cost before each generation.
Switch between Hailuo, Seedance, Kling, and other video routes without rebuilding auth or billing.
Track credits, spending, and model usage for every route in one console.
See whether a task is pending, processing, completed, or failed, with refunds on failure.
Keep MiniMax H3 Max Turbo as one tested route and fall back to H3 or another family when a workload needs it.
Compare Hailuo generations under one EvoLink account and API key, then choose by resolution, duration, reference workflow, and cost.


MiniMax H3
The full-featured Hailuo route: 2K / 768p output, 4-15s, and text, frame, or reference driven generation.
View
Hailuo 2.3
The documented Hailuo generation for text-to-video and image-to-video through Standard and Fast routes.
View
Seedance 2.0
A multimodal route for text, image, video, and audio reference workflows from 480p to 4K.
View
Kling O3
A production video route with multimodal controls and a different capability and cost profile.
View
Wan 2.7
A video fallback for text-to-video and image-to-video workflows with different duration and pricing options.
View
Veo 3.1
Google DeepMind's Veo 3.1: 8-second clips with native audio, available in Fast and Pro variants.
ViewCheck Turbo’s launch details and the family comparison before moving workloads between routes.
See the two model IDs, output limits and first-frame requirements in the Turbo changelog.
Compare the Hailuo routes with an available multimodal audio-video workflow.
Decide whether to ship on Hailuo or move to the Seedance 2.5 API, live on EvoLink since August 7, 2026.
MiniMax H3 Max Turbo is a speed-oriented variant in the MiniMax H3 family. On EvoLink, it generates 5–15 second videos at 480p or 768p from text or a required first frame with an optional last frame. The two input modes use separate model IDs.
For the routes available on EvoLink, H3 Max Turbo targets faster 480p / 768p iteration through text-to-video and first/last-frame image-to-video, while MiniMax H3 remains the 2K option with broader reference workflows. H3 Max Turbo starts at 5 seconds; H3 starts at 4 seconds.
Text-to-video, image-to-video with first and last frame control, high-volume advertising creative, ecommerce product video, social clips, and any workflow where iteration speed matters more than the 2K tier.
Yes. EvoLink exposes MiniMax H3 Max Turbo as two routes through the unified video endpoint, with API keys, credit balance, async task tracking, and refunds on failed tasks.
minimax-h3-max-turbo-text-to-video and minimax-h3-max-turbo-image-to-video. Pick the ID that matches your input type; each route validates its own parameter set. These are the two H3 Max Turbo model IDs currently exposed by EvoLink.
MiniMax H3 Max Turbo is billed per second of output video through your shared EvoLink credit balance. 768p is the default tier; 480p is billed at 5/8 of the 768p rate. Use the pricing section and playground estimator for your user group's live rate before you generate.
Turbo supports text and first-frame image input, with an optional last frame. For reference media, use MiniMax H3 Max: minimax-h3-max-reference-to-video.
No on EvoLink's current H3 Max Turbo routes. They accept 480p and 768p, and reject 2K. Use MiniMax H3 when you need the 2K tier.
Five seconds. EvoLink's H3 Max Turbo contract accepts 5-15 seconds and rejects 4-second clips. The minimum charge follows the same floor: 480p at 5 seconds.
No. Output is 768p or 480p with durations of 5 to 15 seconds, and there is no cancel endpoint, so tasks report can_cancel false and failures are refunded in full.
Submit the task, then poll the task endpoint or register a callback. When the status turns completed the response carries the MP4 URL. Download it and store it yourself.
Results are kept for 24 hours. Save anything you want to keep within that window — the URL stops resolving afterwards.
Both offer 480p / 768p text-to-video and first-frame image-to-video, with an optional last frame and 5–15 second output. H3 Max also has a separate reference-to-video route; Turbo does not. Compare each page’s current pricing, then measure accepted-output cost and end-to-end time on your own workload.
No. The image-to-video route requires image_start. Add image_end only together with the first frame; a last-frame-only request is rejected.
No completion time is guaranteed here. Provider speed demonstrations are specific to their test conditions; your elapsed time also includes queueing, prompt processing and result delivery. Measure submission-to-completion time on your workload.
No. This page covers the hosted MiniMax H3 Max Turbo API on EvoLink. Community H3 Turbo LoRA projects use separate local inference workflows; their weights, hardware requirements and performance results do not define this API.