MiniMax M2: October 27, 2025 Agent-Oriented Open Model. This dated guide separates the actual model or API mechanism from promotional comparisons, endpoint aliases and features added by later releases. It focuses on implementable choices, documented limits and evidence a project should collect before deployment.
Cutoff: 25 October 2026 · Scope: publisher sources and editorial methods; account-specific features not independently verified.
What was released and when
MiniMax officially announced and open-sourced M2 on October 27, 2025. This date falls within the 25 October 2026 editorial cutoff, although it is two days after the October 25 date in the previous calendar year. The model was positioned around coding, tool use and longer task coordination. Its later successors should not be read back into the original release.
Architecture, interface and the important distinction
An agent-oriented foundation model is not itself an agent with trustworthy side-effect controls. M2 supplies predictions and tool-call candidates; an application supplies authentication, tool execution and approval boundaries. Claimed price or speed comparisons in the launch text represent vendor advertising for that launch and do not substitute for current AI10 pricing records.
A useful real-world implementation
For an issue-triage workflow, allow the model to classify a repository issue, propose a patch, and suggest tests inside a sandbox. Deny network writes and repository pushes unless a human explicitly approves. Capture every tool argument, execution result and post-patch regression to distinguish the model’s plan from what actually occurred.
Limitations, licensing and evidence quality
Published demonstrations are not independent production trials. Open-sourcing weights does not mean every remote hosting tier exposes the same tool schema, quantization or inference behavior. Treat tool output as untrusted and validate arguments before invoking shells, browsers or file-system functions.
Alternatives and the selection rule
Compare M2 with a coding-specific hosted model or a smaller local alternative after fixing the agent harness, context budget and tests. AI07 owns orchestration and AI06 developer-tool product comparisons; this article concerns the underlying model and technical interface.
Evaluation protocol worth running
Test a permissioned suite of 20 issues and count patch acceptance, regression failures, invalid calls and approval bypass attempts. Report the actual release-specific checkpoint and runtime rather than only “MiniMax agent”.
Deployment and provenance checklist
Deployment record to preserve: canonical editorial ID wai-ai02-minimax-m2, exact endpoint or checkpoint revision when verified, request date and region, model and tokenizer version, allowed tools, input modality, prompt template, output budget and actual measured usage. For current currency costs use the AI10 price snapshot matched by version, billing unit, region, tier and effective date. Unknown access entitlements must remain explicitly unknown.
Editorial evidence boundary
This is a 2026-10-25 editorial snapshot. A product or service may have changed after that date; the linked official pages can be edited without preserving every prior state. No independent model performance testing or live customer-account entitlement check was conducted for this article.
Sources & Further Reading
- www.minimax.io — documentation/reference (supplier-provided reference; not independently checked in this pass)
- www.minimax.io — documentation/reference (supplier-provided reference; not independently checked in this pass)
Source documentation establishes vendor-published facts, not independently measured model quality, tenant access, contractual rights or current prices. Use a dated pricing ledger and an account-specific entitlement check for deployment decisions.