Loading the catalogue…
Loading the catalogue…
An open-weight 428B-parameter (~23B active) MoE model from MiniMax with a 1M-token context window, multimodal input, and a configurable thinking mode, suited to long-context, agentic, and coding-assist workloads.
Overview. MiniMax M3 is an open-weight, sparse mixture-of-experts model from MiniMax, with roughly 428B total parameters and about 23B active per token. It takes text, image, and video input and produces text output, with a 1M-token context window and up to 512K tokens of output. Developers reach for it when they need long-context, multimodal reasoning with the option to inspect the model's step-by-step thinking, without being locked into a closed-weight vendor.
Key strengths. Independent benchmarking from Artificial Analysis puts MiniMax M3's coding index at 58.6, its strongest measured area, with an intelligence index of 45.4 and an agentic index of 36.1 — a moderate, credible profile rather than a frontier one. MiniMax's own documentation describes agentic tool-use support and a configurable thinking mode (enabled, adaptive, or disabled), giving developers control over when the model exposes its reasoning trace. The model also accepts image and video input alongside text, and MiniMax reports substantial prefill and decode speed gains over its M2 predecessor thanks to a new sparse-attention design.
When to use it. Use MiniMax M3 for multi-step, tool-calling workflows and coding-assist tasks where its measured coding index is a meaningful signal, and for jobs that genuinely need its 1M-token context window — large codebases, long documents, or multimodal inputs mixing text, images, and video. Its optional thinking mode is worth turning on for tasks that benefit from a visible reasoning trace, and off for latency-sensitive, straightforward requests. It fits the 'complex' end of task routing — sustained, multi-step, or tool-using work — rather than simple single-turn queries.
Limitations. MiniMax has not published a training-data cutoff date, and the model uses a proprietary, non-standard tokenizer rather than a documented common one. Its agentic and general-intelligence index scores sit in a moderate band rather than a top tier, so it shouldn't be treated as a frontier reasoning model even with thinking mode enabled, and no independent safety or content-moderation evaluation for sensitive-domain use has been published.
Sovereignty note. MiniMax M3 is built by MiniMax, a China-based creator, and no CLOUD Act exposure, training-on-input policy, or endpoint data-residency details have been verified for this model. Because the weights are openly published under MiniMax's community licence, teams that need full control over where inference runs can self-host the model rather than relying on a third-party endpoint.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L1 | €0.36 / 1.81 | Online | |||
| L0 | €0.27 / 1.09 | Online |
19 use cases classified by the curator. The note says why.
The million-token context window is purpose-built for answering over large document corpora without retrieval-chunk loss.
1,048,576-token context window lets this model ingest entire large documents or document sets in a single pass without chunking, a clear differentiator for Q&A over long material.
Configurable thinking mode plus a 1M-token window supports synthesizing across many long sources in one context, though the 45.4 quality index means outputs should be verified before production use.
Coding index of 58.6 and a 1M-token window support multi-file agentic coding tasks, though this sits below top coding-specialist models.
Extended context window supports tracing bugs across large codebases; coding index of 58.6 suggests reasonable but not top-tier diagnostic accuracy.
Coding index of 58.6 indicates competent code generation; large context helps with whole-repo completion tasks.
Long context lets the model explain code in the context of an entire file or repo; coding index of 58.6 is mid-tier.
1M-token context allows reviewing large diffs or full repositories in one pass; coding index of 58.6 is mid-tier, not class-leading.
Vision input plus a 1M-token context is well-suited to processing long scanned documents, though OCR-specific accuracy is undocumented.
Draft status and a 45.4 quality index make this a poor fit for production-facing customer support where reliability matters more than context length.
No explicit tool-calling/function-calling capability is listed on the card (only vision and prompt-cache), making this a weaker fit than models with confirmed function-calling support.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, ifbench, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "minimaxai/minimax-m3",
"reasoning_effort": "high",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at