MiniMax-M1-80k
Official · BF16 · safetensors
Runtime certified: Transformers
| Precision / quantization | Format | Bits | Publisher trust | Deployment state |
|---|---|---|---|---|
| BF16 | safetensors | 16 | Official | Runtime certified |
MiniMax · General · MiniMax M1
MiniMax M1 80K: Specs, GPU requirements, hosting & deployment
MiniMax M1 80K is a legacy General release in the MiniMax family, certified from its immutable official source revision.
Total parameters456.0B
Active parameters45.9B
Context window10,240,000 tokens
Release statusLegacy · Legacy
ArchitectureMiniMaxM1ForCausalLM
ModalitiesText
Licenseapache-2.0
Deployment stateDeployable with certified configuration
Commercial stateCommercial Use Allowed
Release date2025-06-13
Architecture, strengths and use cases
MiniMax M1 80K is an official self-hostable MiniMax release in the MiniMax General track. It uses MiniMaxM1ForCausalLM, carries 456B / 45.9B MoE, supports a verified context window of 10,240,000 tokens, and exposes only source-certified checkpoints and runtime combinations. Its release, license and deployment facts are tied to the official repository revision rather than inferred from the family name.
MiniMax M1 80K uses MiniMaxM1ForCausalLM with 456B / 45.9B MoE. The stored architecture profile records 80 layers, hidden width 6144, 64 attention heads and a 10,240,000 token context ceiling where the official configuration publishes those fields.
Verified MiniMaxM1ForCausalLM architecture
10,240,000 token certified context
Official BF16, Unknown checkpoint coverage
Private LLM inference
Agentic workflows
Long-context document processing
Certified checkpoints and quantizations
Only exact, source-certified variants attached to this release are shown.
Recommended hardware
Use only the listed transformers runtime configuration with the exact checkpoint precision. The recommendation engine checks weight memory, KV cache, runtime overhead, safety headroom, GPU architecture and topology before ranking rentable and reference hardware.
Estimated weight memory874.85 GB
KV cache2.5 GB
Runtime overhead214.56 GB
Total with safety margin1353.97 GB
Technically compatible reference sizing
No current FusionPointAI inventory passes every runtime, architecture, topology and memory gate for this exact checkpoint. Use the estimator for global compatible hardware.
License and self-hosting considerations
The full 456B resident weight set must fit across the selected GPUs. Context and concurrency add KV-cache memory; MoE active parameters do not replace resident-weight memory.
MiniMax M1 80K is published under apache-2.0. The release-scoped official license link and verification date are retained with the catalogue record.
Commercial Use Allowed. The official license permits commercial use; its obligations still apply.
Alternatives and sibling variants
MiniMax M3, MiniMax M2.7, MiniMax M2.5
Release timeline
minimax/minimax/minimax-m1-80k
Source details
Source revision: 5e1291d5b7dfe2a74150c3eeeb6c6feba553622c9e2983615496c5b280cd286c
Frequently asked questions
How much VRAM does MiniMax M1 80K require?
The exact estimate depends on checkpoint precision, context and concurrency; the page recommendation uses the certified memory engine and compatible runtime configurations.
Which runtimes support MiniMax M1 80K?
Certified upstream runtime evidence is available for transformers.
Can MiniMax M1 80K be used commercially?
The stored commercial classification is Commercial Use Allowed. Consult the official apache-2.0 terms for the final obligations.
Official references
Last verified: 2026-09-03