MiniMax-H3 API
Use the exact MiniMax-H3 model ID through Modelflare asynchronous video routing.
MiniMax-H3 API
Use the exact MiniMax-H3 model ID through Modelflare asynchronous video routing.
Use the exact model ID MiniMax-H3. The model field must match this page exactly.
Authentication and endpoint
Use a Modelflare API key with https://modelflare.dev/v1. The gateway entry point is POST /v1/videos.
Authorization: Bearer YOUR_MODELFLARE_API_KEY
Create a task
curl https://modelflare.dev/v1/videos \
-H "Authorization: Bearer YOUR_MODELFLARE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "MiniMax-H3",
"content": [{"type": "text", "text": "A white cat runs through a neon-lit street in the rain, cinematic tracking shot"}],
"resolution": "2K", "duration": 5, "ratio": "16:9"
}'
Poll and download
Save the task ID. Poll GET /v1/videos/{task_id} and download with GET /v1/videos/{task_id}/content. Result URLs may expire, so transfer the file promptly.
curl https://modelflare.dev/v1/videos/TASK_ID \
-H "Authorization: Bearer YOUR_MODELFLARE_API_KEY"
Request notes
MiniMax-H3 uses content[] with resolution, duration, and ratio controlling output.
Request parameters
MiniMax-H3 uses a multimodal content[] array. Poll the MiniMax query path after task creation; first/last-frame and reference_* roles are distinct workflows.
| Field | Required | Notes |
|---|---|---|
model |
Yes | MiniMax-H3 |
content[] |
Yes | At least one text item; may include image_url, video_url, or audio_url |
resolution |
Yes | 768P / 2K |
duration |
Yes | 4–15 seconds |
ratio |
Conditional | 21:9 / 16:9 / 4:3 / 1:1 / 3:4 / 9:16 / adaptive |
aigc_watermark |
No | Whether to add a watermark |
callback_url |
No | Task status callback URL |
Input and output limits
Output is 768P or 2K for 4–15 seconds. Text-only requests need a concrete ratio; do not mix first_frame/last_frame roles with reference_* roles.
Supported scope
This page covers Modelflare model generation and editing calls. Search or map enrichment, voice management, and element-library management are resource APIs outside this public model-call surface and are not required request fields.
Pricing and billing
This model uses per-second video billing. See the model pricing page for the current customer price, reference list price, and complete specification.
This page documents Modelflare’s public interface; the fields and limits shown here are the current contract.