MiniMax-H3

Overview

Omitting compatibility options selects the official route: 768P or 2K, integer durations of 4–15 seconds, default four seconds at 768P and 1:1, billed by verified output seconds. To use compatibility pricing, explicitly send quality: "low" as in the example, keeping provider "minimax" and endpoint "MiniMax-H3". This selects the compatibility route even at 768p or 2K; it supports 480p, 768p, 1080p, 2K and 4K with 3–15 requested seconds, billed by requested seconds rounded up. For a 4K compatibility request, change resolution to "4K" and keep quality: "low". The pricing tables list both routes separately under your account plan. The example uses compatibility pricing. Accepted tasks are checkpointed. If a run is RUNNING, poll GET /v1/runs/{runId}; after a network timeout, repeat the identical request with the same Idempotency-Key to recover it.

After COMPLETED, read run.output.video_url, run.output.duration and run.output.resolution. Official duration is supplier-measured; compatibility duration is requested duration and billing rounds it up. Download the temporary video URL promptly.

Input

These go in the input object of the run request.

Requests up to 1 MB.

Example

Use your own API key and a saved idempotency key for each new job. Replace image or media placeholders with your own publicly reachable HTTPS URLs. Keep the same key and request body when recovering a timeout.

# Set once per job; reuse this key and the identical body after a timeout.
: "${AGENTSKY_IDEMPOTENCY_KEY:?Set a unique, saved key for this job}"
curl --fail-with-body https://gateway.agentsky.dev/v1/run \
  -H "authorization: Bearer $AGENTSKY_API_KEY" \
  -H "content-type: application/json" \
  -H "Idempotency-Key: $AGENTSKY_IDEMPOTENCY_KEY" \
  -d '{"provider":"minimax","endpoint":"MiniMax-H3","input":{"prompt":"A small blue sphere slowly rotates on a white background.","quality":"low","duration_s":4,"resolution":"768p"}}'
# If status is READY/RUNNING, poll GET /v1/runs/{runId} with the same API key.

Prices by supplier route and resolution, using your plan when signed in. Read the final customer charge from price.amount.value after the run finishes. A RUNNING response is not the final bill.

Questions