MAI-1-preview vs MiniMax M3

Microsoft · US  |  MiniMax · China · Updated June 2026

Quick verdict

Pick MAI-1-preview for microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai or ranked in the top 15 on lm arena at launch. Pick MiniMax M3 for open-weight 428b moe (~23b active per token) with a 1m-token context or native multimodal input — text, image and video. Choose MiniMax M3 if you need self-hosting or data privacy; MAI-1-preview if you want a managed API.

MAI-1-preview (Microsoft, US) and MiniMax M3 (MiniMax, China) line up two different AI ecosystems against each other — a comparison that is as much about cost philosophy and openness as raw capability. MAI-1-preview is microsoft's first fully in-house foundation model - a strategic break from sole reliance on OpenAI, trained on ~15,000 H100 GPUs. MiniMax M3 is miniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing. They diverge most on price, context window and open vs. closed weights — each quantified below from the models' real specs.

Key differences at a glance

Side-by-side specs

SpecMAI-1-previewMiniMax M3
ProviderMicrosoft (US) MiniMax (China)
ReleasedAugust 28, 2025 May 31, 2026
Context window128K (~192 pages) 1M (~1,573 pages)
Price (in/out)Not published $0.23/$0.96 per 1M tokens
Open weight?No — API only Yes — self-hostable
Modalitiestext, code text, image, video, code
SWE-Bench VerifiedNot published Not published
MRCR v2 @ 1MNot published Not published

Who wins what

Microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI

MAI-1-preview

MAI-1-preview lists microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI among its strengths; MiniMax M3 does not.

Ranked in the top 15 on LM Arena at launch

MAI-1-preview

MAI-1-preview lists ranked in the top 15 on LM Arena at launch among its strengths; MiniMax M3 does not.

Trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment

MAI-1-preview

MAI-1-preview lists trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment among its strengths; MiniMax M3 does not.

Open-weight 428B MoE (~23B active per token) with a 1M-token context

MiniMax M3

Its 1M window holds about 8.2× more than MAI-1-preview's 128K in a single prompt.

Native multimodal input — text, image and video

MiniMax M3

MiniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing — and it carries the larger 1M context.

Reports 59.0 on SWE-Bench Pro (a strong open-weight score), surpassing GPT-5.5

MiniMax M3

Open weights make this possible at all — MAI-1-preview is API-only, so it cannot leave the vendor's servers.

Lowest cost at scale

MAI-1-preview

Its weights are open, so at volume you pay for your own hardware instead of MiniMax M3's $0.23/$0.96 per 1M tokens.

Largest single-prompt input

MiniMax M3

Its 1M window is about 8.2× larger than MAI-1-preview's 128K, fitting roughly 1,573 pages in one prompt.

Which should you pick?

A cost-sensitive startup shipping high volume

MAI-1-preview

At Not published it undercuts MiniMax M3, and on millions of tokens that margin decides the monthly bill.

Someone analysing very long documents or codebases

MiniMax M3

Larger 1M window fits more in one prompt.

A team with data-privacy or self-hosting needs

MiniMax M3

Open weights let you run it on your own hardware; MAI-1-preview is API-only.

Anyone whose priority is microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai

MAI-1-preview

It is specifically built for that.

Anyone whose priority is open-weight 428b moe (~23b active per token) with a 1m-token context

MiniMax M3

That is its strongest area.

An enterprise with regional data-residency rules

MAI-1-preview or MiniMax M3

Origin (US vs China) affects where data is processed and which compliance regime applies — check the provider's terms for your region.

MAI-1-preview: where it fits

Microsoft's first fully in-house foundation model - a strategic break from sole reliance on OpenAI, trained on ~15,000 H100 GPUs. Released August 28, 2025 by Microsoft, it is built for microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on OpenAI, ranked in the top 15 on LM Arena at launch, trained on roughly 15,000 NVIDIA H100 GPUs, a genuine internal infrastructure investment, and rolled into Copilot alongside OpenAI models, giving Microsoft a real second option.

Its trade-offs are real: a 'preview' release, not yet positioned as Microsoft's primary Copilot model, no public per-token API pricing - not sold as a standalone product, and distinct from Microsoft's later MAI-Thinking-1 reasoning model - an earlier, more general-purpose entry.

MiniMax M3: where it fits

MiniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing. Released May 31, 2026 by MiniMax, it is built for open-weight 428B MoE (~23B active per token) with a 1M-token context, native multimodal input — text, image and video, reports 59.0 on SWE-Bench Pro (a strong open-weight score), surpassing GPT-5.5, and low entry pricing at $0.30/$1.20 per million up to 512K tokens.

Its trade-offs: price doubles to $0.60/$2.40 above 512K tokens — not flat across 1M, miniMax's own reported 80.5 SWE-Bench Verified figure is vendor-stated, not independently verified, sWE-Bench Pro is a different, harder benchmark than SWE-Bench Verified, and newer than M2.7 but with less independent testing so far. At $0.23 in / $0.96 out per million tokens, it sits in the budget price band.

The bottom line for this matchup

The defining split here is open vs. closed. MiniMax M3 gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. MAI-1-preview gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.

Want both MAI-1-preview and MiniMax M3 without two subscriptions? LumiChats gives you these plus 40+ models under one ₹69/day pass (about $1/day) — draft with one, cross-check with the other.

See pricing

Frequently asked questions

Is MAI-1-preview or MiniMax M3 better for coding?

Public SWE-Bench figures are not available for either model, so the honest test is your own repository — run an identical real bug through both. By design, MAI-1-preview leans toward microsoft's first fully in-house, end-to-end foundation model - a historic break from relying solely on openai while MiniMax M3 leans toward open-weight 428b moe (~23b active per token) with a 1m-token context, and that positioning usually predicts which feels better on your codebase.

Which is cheaper, MAI-1-preview or MiniMax M3?

MiniMax M3 is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while MAI-1-preview is API-metered at Not published. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.

Which has the bigger context window?

MiniMax M3 — 1M vs 128K, about 8.2× larger. Useful only if the model actually reasons over the full window, which not all do.

Can I use both MAI-1-preview and MiniMax M3 together?

Yes — a multi-model platform like LumiChats gives you MAI-1-preview, MiniMax M3 and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.

Which is newer, MAI-1-preview or MiniMax M3?

MiniMax M3 — released May 31, 2026, about 9 months after MAI-1-preview.

Related comparisons

Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.