MiniMax H3 on a Mac: the h3.c Metal port, or a hosted job

Yes, an Apple Silicon path for MiniMax H3 exists. The integration index MiniMax keeps on GitHub lists h3.c, a Metal-native implementation by antirez that it describes as MIT licensed. The index gives no speed or memory numbers for it, so there is no basis here for saying how long a clip takes on a given Mac.

What does MiniMax itself document?

The reference setup in MiniMax's self-hosting guide is Linux with Python 3.12 and eight NVIDIA B200 GPUs on one node, with about 108 GB of disk for the weights. Its other documented path is ComfyUI 0.30.0 or newer with pruned INT8 or NVFP4 weights from Comfy-Org. Neither is a Mac recipe. A Mac port is a community entry in a list, so read its repository before you rely on it.

The license is separate from the code license. h3.c being MIT licensed does not replace the H3 Community License for the weights.

• The license excludes the United States, the European Union, the United Kingdom and South Korea from its Applicable Territory.
• Above 20 million USD in yearly revenue, the license requires prior written authorization from MiniMax.
• Section VI.4 says MiniMax claims no rights over the Outputs.

What does a hosted job change?

Nothing runs on the Mac. You send JSON and download an MP4 from any machine, including a laptop with no GPU. On Sume the id is minimax-h3, 5 to 15 seconds at 480p or 768p. The weights license is not part of that call, but read the terms that apply to you either way.

The sketch below is the whole client for a 5-second 768p clip.

The response gives a polling_url; poll it until completed and download from unsigned_urls[0]. Details are in the video generation docs.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: h3-mac-001" \
  -d '{"model":"minimax-h3","prompt":"A paper boat on a rain-lit street, slow push-in","duration":5,"resolution":"768p"}'

What should you check before you start?

Open the h3.c repository and read three things: which H3 checkpoint it loads, which duration and resolution it supports, and what it says about speed. The integration index describes it as Metal-native for Apple Silicon and MIT licensed and says nothing else I can verify. A port can be correct for 5-second 480p clips and untested for 15-second ones.

Also decide what a Mac run is for. A local port is good for trying a prompt idea with no bill; it is a poor fit for a batch of 50 clips with a deadline. In that case a hosted job runs in parallel while the laptop does other work.