AllocateMiniMax M2.7 FP4 vs MiniMax M3
On provider list prices, MiniMax M2.7 FP4 costs $0.30 per million input tokens against $0.30 for MiniMax M3: effectively level. Output is $1.20 against $1.20. On Allocate both bill at list plus the 7% transaction fee.
Specifications and provider list prices from the Allocate catalog, checked 2026-07-08. Billed price is list plus the 7% transaction fee.
What the numbers say
Take 1,000,000 requests a month at 1,200 input and 350 output tokens each. That workload costs $780 a month on MiniMax M2.7 FP4 and $780 on MiniMax M3 at list: a gap of $0.
MiniMax M3 reads 512K tokens per request against 192K for MiniMax M2.7 FP4, 2.7x the window. That decides which one can take whole documents without splitting them.
Common questions
Which is cheaper, MiniMax M2.7 FP4 or MiniMax M3?
MiniMax M2.7 FP4, on this workload shape. At list prices it is $0.30/$1.20 per million tokens in and out against $0.30/$1.20 for MiniMax M3. Billed on Allocate: $0.32/$1.28 against $0.32/$1.28, list plus 7%.
Which has the bigger context window?
MiniMax M3: 524,288 tokens (512K) against 196,608 (192K) for MiniMax M2.7 FP4.
Can I fine-tune MiniMax M2.7 FP4 or MiniMax M3?
MiniMax M2.7 FP4 publishes open weights (Not listed) and can be fine-tuned on your own data. MiniMax M3 is a closed model served over API; its weights are not available.
Related comparisons
Run the numbers on your workload
Or don’t choose. On Allocate a route name is the contract: point yours at one model today, swap to the other tomorrow, and compare them on your live traffic with per-token metering.