The vendor-shaped entry point for MiniMax video generation. If you already have MiniMax code, point base_url at Amux — request and response shapes match what your client already sends.

This endpoint is asynchronous: submitting returns a task ID and you poll for the result. That is the vendor API's own contract, not an Amux limitation.

The task ID is an Amux ID

The task_id you get back is the Amux task ID, not the upstream one. The upstream handle stays internal: it would reveal which provider served the call, and it is not accepted on any Amux endpoint.

Every retrieval endpoint accepts only this ID. GET /v1/tasks/{id} and the MiniMax-shaped alias below read the same task, so SDKs that build the polling URL themselves keep working.

Three differences from the Model Studio shape

Billing is identical to /v1/tasks

Routing, price book and the reservation taken at submit time are the same. Choosing this endpoint over the unified one changes the wire format, nothing else.

Note that this model bills for input material: reference images per image and reference video by its input duration, both at the rate of the chosen output resolution; reference audio is free. The reservation covers 15 seconds of output, plus another 15 seconds of input when a reference video is present, and the difference is released at settlement.

{
  "model": "minimax/minimax-h3",
  "content": [
    {
      "type": "text",
      "text": "A ginger cat running through fresh snow, slow motion"
    }
  ],
  "resolution": "768P",
  "duration": 5
}