MiniMaxMiniMax Text 01
Minimax develops Minimax Text 01, a chat model that excels at handling long contexts due to its hybrid architecture combining Lightning Attention, Softmax Attention, and Mixture-of-Experts. With 456 billion total parameters and a context window of 10,240,000 tokens, it is particularly well-suited for tasks that require processing extensive amounts of text.
Input
Output
Context
4M
Max Output
2K
Parameters
456.1B
Technical Specifications
Input Modalities
Output Modalities
Capabilities
Loading capabilities…
Estimated GPU requirements for MiniMax Text 01
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 Text 01
Answered from the entry's own fields: context, license, modalities, evidence, serving and the memory to self-host.
MiniMax Text 01 advertises a context window of 4,000,000 tokens, with a maximum output of 2,048 tokens in a single response. 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 Text 01 is an open-weight model released under the MiniMax Model License Agreement license, so the weights can be downloaded and self-hosted within that license's terms.
MiniMax Text 01 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.
No published benchmark result for MiniMax Text 01 is in the catalog yet, so the model is shown as unmeasured. It is not ranked or estimated; the router treats it as unknown for every task until a suite measures it.
Not on the managed pool today; MiniMax Text 01 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 439.6 GB at INT8 for the weights and a default context, from the catalog's 456.1B 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 14, 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.