Skip to main content
Skip to main content

MiniMax H3 Max Spicy

MiniMax H3 Max Spicy is a flagship uncensored video generation model powered by the high-tier MiniMax H3 Max architecture. Operating as a Spicy uncensored model, it completely bypasses standard safety guardrails to unlock maximum motion amplitude, intense physical interactions, and complex cinematic action sequences without content restrictions. Building on the enhanced rendering capacity and higher detail resolution of the Max tier, MiniMax H3 Max Spicy maintains exceptional frame consistency, realistic lighting, and photorealistic textures throughout dramatic camera movements. It is the premier tool for unrestricted dynamic video production, high-impact VFX pre-visualization, commercial action direction, and boundary-pushing creative AI visual assets.

  • 99.9% SLA
  • Official Discounts
  • Pay-as-you-go
  • Fast & Low Latency
Brand:MiniMaxPrice: $0.08 / sec

API DOCS / SIMPLIFIED

Integrate this model with one task-based API flow

MiniMax H3 Max Spicy is a flagship uncensored video generation model powered by the high-tier MiniMax H3 Max architecture. Operating as a Spicy uncensored model, it completely bypasses standard safety guardrails to unlock maximum motion amplitude, intense physical interactions, and complex cinematic action sequences without content restrictions. Building on the enhanced rendering capacity and higher detail resolution of the Max tier, MiniMax H3 Max Spicy maintains exceptional frame consistency, realistic lighting, and photorealistic textures throughout dramatic camera movements. It is the premier tool for unrestricted dynamic video production, high-impact VFX pre-visualization, commercial action direction, and boundary-pushing creative AI visual assets. The examples below are rendered from MiniMax H3 Max Spicy, the current gateway base URL, and the selected public model contract.

Input mode
X-API-Key on every request
POST /api/v1/openapi/task
GET /api/v1/openapi/task/status/{task_id}
Async task workflow

Single code window

Switch language once. Each example already includes both the task creation request and the task status polling request.

Unified Example
API_KEY="<API_KEY>"
BASE_URL="https://api.musespark.ai"
REQUEST_BODY='{
  "model_id": "minimax-h3-max-spicy",
  "parameters": {
    "prompt": "A cinematic drone shot over a futuristic city at sunrise, volumetric light, realistic motion",
    "resolution": "768P",
    "duration": 5,
    "aspect_ratio": "21:9",
    "batch_size": 1
  }
}'

CREATE_RESPONSE=$(curl --request POST "$BASE_URL/api/v1/openapi/task" \
  --header "X-API-Key: $API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw "$REQUEST_BODY")

TASK_ID="<TASK_ID_FROM_CREATE_RESPONSE>"

curl "$BASE_URL/api/v1/openapi/task/status/$TASK_ID" \
  --header "X-API-Key: $API_KEY"

Request and response JSON become the documentation

Keep the payload and task status envelope as the primary contract. Field descriptions, optionality, and enum hints now live inline as JSON comments.

Request Body

Caller payload

This is the request envelope accepted by the public gateway for the selected model contract.

Field comments and caller parameters come directly from the current item's model schema.
{
"model_id": "minimax-h3-max-spicy",// target model
"parameters": {
"prompt": "A cinematic drone shot over a futuristic city at sunrise, volumetric light, realistic motion",// prompt describing the video to generate · min 1 · max 7000 · min length 1 · max length 7000
"resolution": "768P",// output video resolution: 768P · enum: 768P
"duration": 5,// output duration in seconds, from 4 to 15 · min 4 · max 15
"aspect_ratio": "21:9",// output aspect ratio. Choose one of the six listed concrete ratios · enum: 21:9 | 16:9 | 4:3 | 1:1 | 3:4 | 9:16
"batch_size": 1// standard quantity control field. The allowed range for this item is 1-4 · min 1 · max 4
}
}
Response Body

Gateway response

This is the task status response you will query with task_id until the task reaches a terminal state.

Poll every 2-5 seconds and stop once status becomes completed, failed, cancelled.
{
"code": 200,// 200 on success
"msg": "success",
"data": {
"task_id": "task_01HQX8N2QJ0YQ8Q0T7G6N4V6K2",// use for status polling
"status": "completed",// enum: queued | running | completed | failed | cancelled
"progress": 100,// 0-100 if available
"completed_at": 1760000000,// unix timestamp
"expires_at": 1760001800,// unix timestamp
"result": {
"output_urls": [// generated files
"https://cdn.example.com/output.png"
]
}
}
}