> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comfy.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Use MiniMax H3 with Comfy Router

> Call minimax/minimax-h3 through Comfy Router: endpoint, request shape and the response Router returns.

API Reference for `minimax/minimax-h3`, served by Comfy Router from MiniMax.

## Quick start

Create a key at [platform.comfy.org/profile/api-keys](https://platform.comfy.org/profile/api-keys) and export it as `COMFY_API_KEY`. The Python and TypeScript snippets use the Comfy SDKs (`pip install comfy-sdk`, `npm install @comfyorg/sdk`); the cURL snippet is the same call over raw HTTP.

**Model ID:** `minimax/minimax-h3`

**Endpoint:** `POST https://api.comfy.org/v2/models/minimax/minimax-h3`

<CodeGroup>
  ```python Python theme={null}
  from comfy_sdk import Comfy

  # Reads COMFY_API_KEY from the environment. Each call sends a fresh
  # Idempotency-Key and waits up to 10 minutes for the finished result.
  with Comfy() as client:
      result = client.models.run(
          "minimax/minimax-h3",
          {
              # Request fields are the provider's own — see Input below.
          },
      )

  print(result)
  ```

  ```typescript TypeScript theme={null}
  import { comfy } from "@comfyorg/sdk";

  // Reads COMFY_API_KEY from the environment. Each call sends a fresh
  // Idempotency-Key and waits up to 10 minutes for the finished result.
  const { data } = await comfy.models.run("minimax/minimax-h3", {
    // Request fields are the provider's own — see Input below.
  });

  console.log(data);
  ```

  ```bash cURL theme={null}
  # Request fields are the provider's own — see Input below.
  curl https://api.comfy.org/v2/models/minimax/minimax-h3 \
    -H "X-API-Key: $COMFY_API_KEY" \
    -H "Idempotency-Key: $(uuidgen)" \
    -H "Content-Type: application/json" \
    -d '{}'
  ```
</CodeGroup>

## Schema

### Input

<Note>
  Router has not published an authored input schema for this model yet: `GET /v2/models/minimax/minimax-h3/openapi.json` returns an open object with `x-comfy-input-schema-authored: false`. Router forwards the body to MiniMax unchanged, so [MiniMax's own API reference](https://platform.minimax.io/docs/api-reference) is authoritative for the request fields, and nothing is validated server side.
</Note>

### Output

<ResponseField name="task" type="object">
  A Minimax V2 video generation task.
</ResponseField>

<ResponseField name="task.content" type="object">
  Generated output; present when status is succeeded.
</ResponseField>

<ResponseField name="task.content.prompt" type="string">
  The enhanced video prompt produced by a succeeded h3\_context\_ir task.
</ResponseField>

<ResponseField name="task.content.url" type="string">
  Time-limited URL of the generated MP4. Query again for a refreshed URL.
</ResponseField>

<ResponseField name="task.duration" type="number">
  The duration of the generated video in seconds.
</ResponseField>

<ResponseField name="task.error" type="object">
  Error details when status is failed; carries code and message.
</ResponseField>

<ResponseField name="task.id" type="string">
  The task ID.
</ResponseField>

<ResponseField name="task.model" type="string">
  The model used for the task.
</ResponseField>

<ResponseField name="task.ratio" type="string">
  The actual aspect ratio of the generated video.
</ResponseField>

<ResponseField name="task.resolution" type="string">
  The resolution of the generated video.
</ResponseField>

<ResponseField name="task.status" type="string">
  Task status. Options: queued, running, succeeded, failed, cancelled, expired.
</ResponseField>

<ResponseField name="task.task_type" type="string">
  The type of the task.
</ResponseField>

<ResponseField name="task.usage" type="object">
  Usage recorded for the task.
</ResponseField>

<ResponseField name="task.usage.completion_tokens" type="integer" />

<ResponseField name="task.usage.input_image_count" type="integer" />

<ResponseField name="task.usage.input_seconds" type="number" />

<ResponseField name="task.usage.output_seconds" type="number" />

<ResponseField name="task.usage.prompt_tokens" type="integer" />

<ResponseField name="task.usage.total_seconds" type="number" />

<ResponseField name="task.usage.total_tokens" type="integer" />

## Examples

### Output

```json theme={null}
{
  "task": {
    "content": {
      "url": "https://example.invalid/minimax/minimax-h3/generated.mp4"
    },
    "duration": 6,
    "id": "3f7a1b28-5c0d-4e91-8a6f-1b2c3d4e5f60",
    "model": "MiniMax-H3",
    "ratio": "16:9",
    "resolution": "768P",
    "status": "succeeded",
    "usage": {
      "output_seconds": 6,
      "total_seconds": 6
    }
  }
}
```

## Before you ship

The snippets above are the shortest working call. Three things are the same for every model and are documented once on the [Comfy Router headers](/development/comfy-router/headers) page: send an `Idempotency-Key` on every paid call and reuse it when you retry, expect the connection to be held up to Router's 10 minute deadline, and keep `X-Comfy-Request-Id` from every response. The SDKs do all three for you; the cURL tab does none of them. On failure, `X-Comfy-Error-Type` names the bucket, and a `422` means the body failed the model's schema and was never billed.

<CardGroup cols={3}>
  <Card title="Headers" icon="list" href="/development/comfy-router/headers">
    Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
  </Card>

  <Card title="Quick Start" icon="rocket" href="/development/comfy-router/quickstart">
    Typed error handling in Python and TypeScript, reading the 422, walking the catalog.
  </Card>

  <Card title="Limitations" icon="triangle-exclamation" href="/development/comfy-router/limitations">
    What Router does not do today, and what to use instead.
  </Card>
</CardGroup>