Minimax Models
Usage
0
5
1 of 4
All 4 Minimax Models
Open in model list| Modalities | ||||
|---|---|---|---|---|
| MiniMax-Text-01 | Takes text. Output modality not published. | 1M | $0.14$1.12/M | — |
| alicloud-minimax-m2.5 | — | $0.2876$1.1504/M | $0.0288/M | |
| MiniMaxAI/MiniMax-M1-80k | — | $0.6$2.4/M | — | |
| minimax-h3-max | Takes text, vision, returns video. | — | $2$2/M | — |
Minimax on AIHubMix
Which Minimax model should I start with?
MiniMax-Text-01 at $0.14/M input — the cheapest entry here that declares a token price, and it carries a 1M context. Move up to minimax-h3-max when answer quality matters more than cost.
Why are there several entries for the same model?
Because each row is a route you can call, not a model release. Some IDs name an upstream (azure-, alicloud-, cc-), some are the open-weight repository form (MiniMaxAI/…), and some differ only in capitalisation, kept so older integrations keep working.
The catalog does not carry a field saying which of those a given row is, so this page does not sort them into buckets it would have to invent. Every row shows that route’s own price, context and speed — compare those directly, and open a model to see the upstreams that serve it.
How is cached input billed?
The Cache read column is the rate for input tokens served from the prompt cache — for example alicloud-minimax-m2.5 bills cache hits at 10% of the input rate. Cache write is the surcharge for putting a prompt into the cache in the first place, and only a few upstreams bill it separately. A dash in either column means the catalog carries no cache rate for that model, so plan on paying the full input rate.
Do I need a separate Minimax account?
No. One AIHubMix key covers every model on this page, and switching between them is a change to the model string — billing, rate limits, and logs stay in one place.
Start calling Minimax in one line
One key, one endpoint, 750 models across 29 model authors.