MiniMax M3 on VM0. Official MiniMax coding model at ×0.2
Official MiniMax M3 routing for coding agents, 1M context, and native multimodal understanding.
1M tokens · Text / Vision / Code · Prompt cache
MiniMax M3 is MiniMax's frontier coding and agentic model, exposed on VM0 through the official MiniMax Anthropic-compatible endpoint. It is the right MiniMax choice when an agent needs stronger coding, tool use, long-context reasoning, and native vision understanding than the retained M2 series.
VM0 prices M3 from MiniMax's standard non-promotional pay-as-you-go tier for the base context band: $0.60 / $2.40 per 1M tokens, with prompt cache reads at $0.12 / 1M and no separate cache-write billing in the M3 table. MiniMax M2.1 remains available for lower-cost compatibility, while M3 is the default MiniMax BYOK model.
MiniMax M3とは？
June 1, 2026 · Official MiniMax M3 text model alongside the retained M2 series.
MiniMax M3 is the new official MiniMax text model for coding and agentic workloads. MiniMax describes it as combining frontier coding capability, a 1M-token context window, and native multimodal understanding.
On VM0, M3 is added to the existing MiniMax API-key provider instead of creating a new integration. It uses the same api.minimax.io/anthropic routing surface and the same MINIMAX_API_KEY secret as M2.
The existing M2 entries stay available, while M3 is the MiniMax provider default for new selections.
MiniMax M3の注目ポイント
アーキテクチャと機能の主な特徴。
M3 uses MiniMax Sparse Attention for ultra-long context. The official API supports up to 1M tokens with a 512K guaranteed minimum, automatic prompt cache support, and native multimodal understanding.
スペック概要
MiniMax M3のベンチマーク
MiniMax positions M3 around coding, agentic tasks, and long-horizon execution. Treat these as vendor-reported signals and validate against your own VM0 agent regression set.
MiniMax M3の価格
プロバイダー定価、100万トークンあたり。
MiniMax M3の実践的な挙動
本番エージェント実行で観測された動作。
Coding agents
The best MiniMax option for coding assistants, long tool chains, and multi-step repository work.
Long context
A 1M context window lets agents keep large documents, code, logs, and previous work in scope without switching model families.
Multimodal
Native vision understanding makes M3 a better fit than M2 when screenshots, diagrams, or visual artifacts are part of the workflow.
MiniMax M3に最適なエージェントタスク
The coding agent that must stay on MiniMax
Repository edits, debugging, and agentic coding flows where your deployment already uses MiniMax keys but needs a stronger coding model than M2.1.
The long-context review run
Large pull requests, logs, notebooks, or design documents that should stay in one model context while the agent reasons and edits.
The multimodal investigation
Workflows that mix text with screenshots or diagrams. M3 is marked image-input capable on VM0, while the M2 entries stay text/code only.
MiniMax M3を避けるべきケース
Skip M3 when you need the absolute lowest MiniMax cost and text-only M2.1 is already good enough, or when you need OpenRouter/Vercel routing because this VM0 entry intentionally uses only the official MiniMax path.
MiniMax M3 vs 他のモデル
MiniMax M3 vs Kimi K2.6
Both target coding and agentic work at low cost. Kimi has broader existing gateway support on VM0, while M3 uses the official MiniMax route and gives MiniMax users the newer model.
MiniMax M3 vs Claude Sonnet 4.6
Sonnet 4.6 remains the baseline for reliability on complex English tool-use. M3 is much cheaper and attractive for MiniMax-native coding agents, but should be validated on critical workflows.
結論: MiniMax M3を使うべきか？
Use MiniMax M3 when you want the official MiniMax coding model with long context and vision support. Keep M2.1 when cost and compatibility matter more.
よくある質問
Is MiniMax M2.1 still available?
Yes. VM0 keeps MiniMax M2.1 in the direct MiniMax provider. M3 is now the default MiniMax BYOK model.
Does VM0 route MiniMax M3 through OpenRouter or Vercel?
No. This entry intentionally uses only the official MiniMax Anthropic-compatible endpoint.
Which M3 pricing tier does VM0 show?
The VM0 model page and usage seed use MiniMax's non-promotional standard base tier. MiniMax also documents a higher standard tier for input above 512K tokens.
代替モデル
VM0でMiniMax M3を使う
VM0でMiniMax M3にアクセスする2つの方法
VM0はMiniMax M3を、VM0クレジットで課金されるBuilt-inモデル、およびMiniMax API keyを使用したBring-your-ownの2通りでサポートしています。Built-inパスではVM0 Managedルーティングと後述のクレジット倍率が適用され、Bring-your-ownパスでは上流プロバイダーに直接課金され、VM0クレジットへの変換は行われません。
VM0の推奨
VM0はMiniMax M3をコアエージェントモデルではなく、コスト削減オプションとして位置付けています。一括分類、プレフィルター、レイテンシが重要な短い返信、固定のレガシーエージェントなど、非コア作業の単価最適化に使用し、実行を左右するステップにはClaude Opus 4.7、Claude Opus 4.6、またはClaude Sonnet 4.6を維持します。
クレジットと×0.2倍率
VM0のすべてのBuilt-inモデルは、×1クレジット基準となるClaude Sonnet 4.6の倍数で価格設定されています。MiniMax M3は×0.2クレジットで課金されます。倍率はVM0の請求書に表示されるもので、上記の価格表のベンダー定価はVM0がクレジットに変換する前に上流プロバイダーが請求する金額です。
MiniMax M3は×0.2で課金されます。つまり、1ステップのコストはSonnet 4.6（×1基準）の同等ステップのわずか0.2倍です。これはクレジット基準を大きく下回り、ピーク時の推論品質よりもステップあたりのコストが重視される高ボリュームのバックグラウンドワークに自然な選択肢です。
VM0でJune 1, 2026から利用可能。