MiniMax H3 License: Territory, Revenue, and Commercial Use

MiniMax H3 is open-weight, but its community license does not cover the United States, European Union, United Kingdom or South Korea without separate written authorization. It also requires separate authorization above a stated $20 million annual-revenue threshold and includes attribution conditions for commercial products.^[1]

The weights being downloadable from Hugging Face answers a distribution question. It does not by itself answer whether a company may deploy them in a particular country or product.

This article identifies the clauses in the public license. It is not legal advice and does not decide how they apply to a specific corporate or cloud arrangement.

MiniMax H3 is not Apache, MIT or BSD

The repository uses the MiniMax H3 Community License. That matters because “open-weight” describes access to model files, while an open-source license such as Apache-2.0 describes a different set of permissions and obligations.

Question	What the public files establish
Can the weights be downloaded?	Yes
Is the license Apache, MIT or BSD?	No
Does the license apply in every country?	No
Can companies use H3 commercially?	Conditions and thresholds apply

Do not carry expectations from another open model into this one. The license text attached to H3 is the contract that needs review.

Four regions are outside the applicable territory

The license defines an “Applicable Territory” and excludes:

the United States;
the European Union;
the United Kingdom;
South Korea.

It instructs users in those places to contact MiniMax for separate written authorization.^[1]

The operational questions become more complicated than a country list. A company may be incorporated in one country, employ a team in another and deploy GPUs in a third. The public text does not let a general article determine which fact controls every arrangement.

What it does establish is enough to reject one shortcut: a public download is not evidence that every global deployment is licensed.

The $20 million commercial threshold

The community license also states that separate authorization is required when the relevant product or service exceeded $20 million in annual revenue during the preceding calendar year.^[1]

Being below that figure does not erase the rest of the license. Commercial products still need to follow its other conditions, restrictions and notices. One product detail that is easy to miss is the requirement to display “MiniMax H3” in the user interface of a commercial product.

Revenue thresholds can be misread when a model sits inside a larger company. Is the relevant number company revenue, product revenue or service revenue? The exact license language and the facts of the deployment should be reviewed together rather than reduced to a sentence from this page.

Self-hosting and hosted API access are different decisions

Self-hosting means the team downloads and operates the H3 weights. The community license is directly relevant to that activity.

A hosted API provides access under the service provider's contract and acceptable-use terms. It may return output from the same model family, but the customer is not taking possession of the weights or running the same deployment.

That distinction does not prove that every API arrangement is permitted. It means the documents and roles are different. Ask the hosted provider what terms govern access instead of assuming the model repository license maps unchanged onto an API account.

MiniMax H3 on reAPI is a metered hosted route for 768P and 2K generation. Teams considering that option should evaluate reAPI's service terms; teams taking the weights should evaluate the community license and their deployment facts.

A deployment record worth keeping

Before H3 enters a product, record:

the legal entity using the model;
the countries where the team and users are located;
where the model is actually deployed;
whether the tool is internal or user-facing;
the relevant prior-year revenue figure;
the attribution displayed in the interface;
the exact license version reviewed at launch.

Save a copy of that license with the deployment record. Model repositories can change, and a compliance review six months later should not depend on reconstructing which text was visible on launch day.

What to do when the license does not fit

There are three ordinary paths:

request written authorization from MiniMax;
choose an open-weight video model whose license covers the intended deployment;
use a hosted route after reviewing its service terms.

The correct alternative depends on why H3 was chosen. If local privacy is the requirement, switching to an API does not solve the same problem. If 2K output and native audio are the requirements, a hosted route may preserve them without a local deployment. If permissive redistribution is essential, another model license may be the deciding feature.

Do this review before purchasing GPUs or building custom nodes. The local-versus-API cost guide shows that hardware work can be substantial; a territory clause should not be discovered after it is complete.

MiniMaxAI. MiniMax H3 Community License. Retrieved August 23, 2026. huggingface.co
MiniMaxAI. MiniMax H3 model repository. Retrieved August 23, 2026. huggingface.co
MiniMax. MiniMax H3 launch announcement. Published July 31, 2026. minimax.io