IT EN
Start a trial

Operational notes Observatory

MiniMax H3: the weights are out, the licence excludes the European Union

8 min read

Diamond-pattern metal fencing photographed close up, in black and white, with no people and no legible text
The mesh lets your gaze through, not your step: it is the same distinction the H3 licence draws over territory, not over the file.

On 1 August we wrote that MiniMax H3 — MiniMax’s multimodal generation model — had no weights yet: just one line in the announcement, “we plan to open up the model weights in the coming days, subject to applicable laws and regulations.” We are updating that story, not retracting it: the weights are here now. The official MiniMaxAI/MiniMax-H3 repository on Hugging Face was last modified on 6 August 2026 and holds 280 files, 104 of them .safetensors — the actual weights, downloadable by anyone, no gate. But the licence published alongside those files, dated 2 August 2026, carries a clause no earlier MiniMax model had: it expressly excludes the European Union from the territory where use is authorised.

What the text says

The document, the “MiniMax H3 COMMUNITY LICENSE AGREEMENT,” states its own scope up front: “The scope of this License Agreement… is expressly limited to the ‘Applicable Territory’ as defined below.” Section I defines it. I.5: “‘Excluded Territories’ means the European Union, the United Kingdom, the Republic of Korea and the United States of America.” I.3: “‘Applicable Territory’ means worldwide, excluding the Excluded Territories” — the rest of the world.

The grant of rights, in Section II, leaves no room for reading it another way: “Solely within the Applicable Territory, we grant you a non-exclusive, non-transferable, royalty-free, limited license…” Section V restates it as a prohibition, V.4: “You may not use, reproduce, modify, distribute, or display the MiniMax H3 Works or any of their Outputs or results outside the Applicable Territory. Any such use outside the Applicable Territory is not authorized by this Agreement.”

It is not a dead end. The same Section II adds: “We will continuously evaluate the applicable laws, regulations and compliance requirements for the Excluded Territories. In the meantime, should any person in such Excluded Territories be interested in deploying our models, you are welcome to contact us about obtaining a license…” Read it for what it says: MiniMax does not state that use in the EU is unlawful. It states that it is evaluating the laws applicable to those territories, and that in the meantime this contract does not authorise it — a contractual position, not a legal finding.

Who grants the licence, and on what terms

One fact, without speculation: “‘We,’ ‘Us’ or ‘MiniMax’ means Nanonoble Pte. Ltd.” — the licensor is a Singapore company, not a Chinese entity. Governing law and forum sit outside the EU regardless: Section IX fixes “the laws of the Hong Kong Special Administrative Region” and the exclusive jurisdiction of its courts for any dispute.

The rest of the text adds five points that bear on whoever installs H3, wherever they are:

  • Commercial threshold. Above 20 million US dollars in yearly revenue, “you shall obtain a separate, prior written authorization from MiniMax by contacting api@minimax.io” with the subject line “MiniMax H3 licensing - authorization request” (IV.1); below that threshold, you must still “prominently display ‘MiniMax H3’” on the interface of any commercial product (IV.2).
  • Anti-distillation. “You may not use the MiniMax H3 Works or any of their Outputs or results to improve any other artificial intelligence model (other than MiniMax H3 or its Model Derivatives)” (V.3). “Model Derivatives” (I.11) explicitly covers distillation, methods using intermediate data representations, and training on synthetic-data outputs generated by the model itself.
  • Downstream policing duty. Anyone offering a service that generates outputs with H3 must “implement, maintain, test, and periodically review reasonable and proportionate technical and organizational safeguards,” and keep a reporting channel open (V.5) — a compliance burden pushed onto whoever redistributes.
  • Sue us, lose your licence. If the licensee brings an intellectual-property claim against MiniMax, “all licenses granted to you under this Agreement will terminate as of the date such suit or proceeding is filed” (VI.3).
  • On breach. An obligation to “delete or destroy all copies within your possession or control” and “notify each downstream recipient that your authorization has ended” (VIII.2).

A closing note in the text itself: “the encoder of MiniMax H3 uses Qwen3-VL-32B, which is licensed under Apache 2.0 License” — one genuinely open component, inside a model that is not.

The file you download is hardly ever the official one

I re-checked overnight, at 00:51 on 7 August 2026 Italian time (22:51 UTC on 6 August), the two repositories holding the same weights. MiniMaxAI/MiniMax-H3, the official one: 12,102 downloads, 2,731 likes, 280 files, 104 .safetensors. Comfy-Org/MiniMax-H3, a third-party repackaging for ComfyUI with quantised variants — bf16, scaled fp8, int8, including “pruned” versions: 2,295,377 downloads, 839 likes, 17 files, 15 .safetensors. Roughly 190 times the downloads of the original, from a sixteenth of the files.

I opened the third-party repository’s card to check, as recommended. Its README.md declares license: other, license_name: minimax-h3-community-license-agreement, and a license_link pointing straight at the text quoted above — the same licence identifier as the original. There is nothing improper here: the licence requires it (V.2, “you must bind each recipient or user to enforceable terms at least as protective… and you must notify each recipient or user that those restrictions apply”). The reference is there, formally in order. What is missing is the reading: whoever downloads one of the 17 files listed under diffusion_models is unlikely to click through to the definition of “Excluded Territories.”

Open weights describes the file, not the right to use it

“Open weights” describes the availability of a file, not the right to use it. Here the weights are downloadable by anyone, with no gate — from the official repository or, 190 times more often, from the repackaged one. But the contract that comes with them says use inside the European Union is not authorised. For a European business or public body, the consequence is plain: downloading is technically possible, running it in production in Europe is not covered by the licence on offer, and the route the licensor points to is requesting a separate authorisation first. That is not the same as saying the use is unlawful outright: it means this particular licence, the one you accept by running the model, does not cover it.

And there is a second layer, which is our line of work: the file that ends up in your pipeline might not be the one you evaluated. The most downloaded copy is a third-party repackaging with quantised, “pruned” weights — different artefacts, carrying the same licence by reference rather than by direct reading. We measured the same problem, on a different pair of repositories, only days ago with Qwen3.8: whoever keeps a register of models in production needs to know which artefact, from which repository and under which licence is running — not “MiniMax H3” as a label, but the file, with its hash. The same lesson applies to a software package: the trust boundary is not the project’s name, it is what actually ends up installed.

What to do about it

  • Before writing “MiniMax H3” into a specification, check which repository the package is built on — official or repackaged — and read the licence at source.
  • If you operate in the EU, treat the territorial clause as a block on production adoption: the route the licence provides is to write to MiniMax before running the model, not afterwards.
  • Above 20 million US dollars in annual revenue, the separate written authorisation is required anyway.
  • For every model in production, record the artefact — file and hash — the source repository, the licence and the territory it covers.

How we solve this

A licence that excludes your territory should not stop a project: it should stop a component. Verifying the licence, provenance and permitted territory of every model in production becomes a check that actually runs on the client’s own systems — a register with artefact, source repository, hash, version, licence and authorised territory, ready to show at an inspection, not a spreadsheet updated once a year.

The same setup brings the organisation’s scattered data — plant, archives, business systems, sensors, documents — into a single operating model on which AI agents execute decisions with a human operator in command, for large enterprises, defence, government and healthcare. The model running underneath stays a replaceable component: if H3’s licence changes, or another model serves the use case better, the ontology, the data and the processes remain yours, not the vendor’s — which is why our systems are never tied to a single model. We always deliver in two modes: on-premise, on self-contained machines that require no deep integration into the client’s network, or dedicated cloud with a data centre in Italy; always with shared governance.

Assessing MiniMax H3, or another open-weight model, for a European use case? Thirty minutes with one of our experts: we’ll check the licence, the authorised territory and the exact artefact together before it goes into production.

Sources