Compare MiniMax M2.7 (MiniMax) and MiniMax M3 (MiniMax) by price, context, capabilities, and latency.
Lado a lado
Compare preço, fornecedor, contexto, capacidades, latência e base da fonte.
| Model | Provider | Input | Output | Context | Capabilities | Best for | Latency | Status | Source |
|---|---|---|---|---|---|---|---|---|---|
| MiniMax M2.7minimax-m2-7 | MiniMax | ¥1.68 / 1M tokens | ¥6.74 / 1M tokens | 128k | Tool callingJSON modeStreamingLow cost | high-volume chat, agentic tool use | 900-2800ms | Production | Platform curated |
| MiniMax M3minimax-m3 | MiniMax | ¥2.81 / 1M tokens | ¥11.23 / 1M tokens | 128k | Tool callingJSON modeStreamingLow cost | high-volume chat, agentic tool use | 900-2800ms | Production | Platform curated |
FAQ
MiniMax M2.7 is cheaper (¥1.68 / 1M tokens input / ¥6.74 / 1M tokens output) vs MiniMax M3 (¥2.81 / 1M tokens input / ¥11.23 / 1M tokens output). Actual cost depends on your input/output token mix — estimate it with the pricing calculator.
Both offer the same context window: 128k tokens.
Both target Low cost. Pick MiniMax M2.7 to optimize cost, or MiniMax M2.7 for the longer context window. Test both on real prompts before committing production traffic.