MiniMaxMiniMax M2.1
Minimax builds Minimax M 2.1, a chat model exceling at code generation and reasoning, with a notable context window of 196,608 tokens. It delivers strong performance in certain benchmarks, such as the Intelligence Index, MMLU-Pro, LiveCodeBench, and HLE, where it ranks in the top 25% or better.
Input
Output
Context
197K
Max Output
-
Parameters
228.7B
Technical Specifications
Input Modalities
Output Modalities
Capabilities
Loading capabilities…
Benchmarks
Estimated GPU requirements for MiniMax M2.1
Estimates based on INT8 quantization at up to 32K context. A count above one assumes tensor parallelism across the cards. Actual requirements vary by framework and configuration.
More models by MiniMax
The creator's other models in the catalog, with their context, size and license where published.
Compare it, or keep browsing
Put this model beside its alternatives on the same evidence, or go back to the full catalog.
Frequently asked questions about MiniMax M2.1
Answered from the entry's own fields: context, license, modalities, evidence, serving and the memory to self-host.
MiniMax M2.1 advertises a context window of 196,608 tokens. The figure is the creator's published maximum; a given provider may serve less, and the gateway routes on what each provider actually serves.
Yes. MiniMax M2.1 is an open-weight model released under the Other license, so the weights can be downloaded and self-hosted within that license's terms.
MiniMax M2.1 accepts Text and produces Text. The capabilities card on this page lists which API features each deployment honours, such as function calling and structured output, with the source each was checked against.
MiniMax M2.1 has published results from Artificial Analysis, shown by suite in the benchmarks card above exactly as the publisher reported them. Scores are not combined across suites, and a suite that has not measured MiniMax M2.1 is shown as not available rather than estimated.
Not on the managed pool today; MiniMax M2.1 is listed for reference and comparison. Connect your own provider key or endpoint that serves it and the gateway runs it on your account, with routing decisions recorded the same way.
About 221.0 GB at INT8 for the weights and a default context, from the catalog's 228.7B parameter count; FP16 needs roughly twice that, and long contexts or many concurrent requests add KV cache on top. The GPU section on this page lists cards that hold it, and the capacity planner sizes it for your context length and traffic.
Fields collected from public registries, provider APIs and benchmark publishers, each tagged with its source.
Last updated: Oct 16, 2026
Put intelligence in the middle.
One gateway in front of every model, with your policies applied and every decision on record. Start on the free plan with 5,000 requests a month, no card required.