MODEL PROFILE

MiniMax-M3.1-Flash-Maya-GGUF

peasantsmith · MiniMax-M3.1-Flash-Maya-GGUF

GGUF quantizations of MiniMaxAI/MiniMax-M3.1-Flash (428B parameters, 23B active per token: 128 routed experts per layer, 4 active, plus a shared expert; sparse attention in every layer; up to a 1M-token context), made for **Project Maya**. Project Maya keeps the most-used experts on the GPU and computes the rest from RAM, so the model runs well below its size. Both quants are made from MiniMax's own release (FP4 experts, FP8 dense weights), not from a re-quantized file, and keep every expert. Measured on held-out conversations never used for calibration, on the model's own answers, against the original model's predictions (MiniMax's released weights, decoded exactly), with the files as published running in Project Maya's engine - the same results on NVIDIA and AMD. 1. **Calibration text** in MiniMax's own chat format, thinking included: tool calls and agent traces, code (with three.js / canvas / WebGL and other front-end work), reasoning, long answers, chat, multilingual chat - 384 sequences of 2,048 tokens. A separate held-out set is kept for evaluation. 2. **Statistics from the model itself**, layer by layer: an importance matrix for every expert separately. 3. **Where the bits go:** every layer's gate, up and down matrices were measured in each candidate type, and the extra bits went to the layers where the model is most sensitive. 4. **Error-feedback rounding** of every expert, at the quantizer's 256-weight blocks, each expert against its own input statistics - and each layer calibrated on what the already-quantized layers before it produce. 5. **llama.cpp's own quantizers (ggml)**, so the files are ordinary GGUFs in llama.cpp's `minimax-m3` layout.

Visual QAmultimodallicense:other
Context windowNot disclosed
Input → OutputText、Image → Text
Model weightsNot verified
Profile updated2026/10/30 14:28:01
OVERVIEW

Model overview

GGUF quantizations of MiniMaxAI/MiniMax-M3.1-Flash (428B parameters, 23B active per token: 128 routed experts per layer, 4 active, plus a shared expert; sparse attention in every layer; up to a 1M-token context), made for **Project Maya**. Project Maya keeps the most-used experts on the GPU and computes the rest from RAM, so the model runs well below its size. Both quants are made from MiniMax's own release (FP4 experts, FP8 dense weights), not from a re-quantized file, and keep every expert. Measured on held-out conversations never used for calibration, on the model's own answers, against the original model's predictions (MiniMax's released weights, decoded exactly), with the files as published running in Project Maya's engine - the same results on NVIDIA and AMD. 1. **Calibration text** in MiniMax's own chat format, thinking included: tool calls and agent traces, code (with three.js / canvas / WebGL and other front-end work), reasoning, long answers, chat, multilingual chat - 384 sequences of 2,048 tokens. A separate held-out set is kept for evaluation. 2. **Statistics from the model itself**, layer by layer: an importance matrix for every expert separately. 3. **Where the bits go:** every layer's gate, up and down matrices were measured in each candidate type, and the extra bits went to the layers where the model is most sensitive. 4. **Error-feedback rounding** of every expert, at the quantizer's 256-weight blocks, each expert against its own input statistics - and each layer calibrated on what the already-quantized layers before it produce. 5. **llama.cpp's own quantizers (ggml)**, so the files are ordinary GGUFs in llama.cpp's `minimax-m3` layout.

Key features

特点摘要待依据来源补齐,不凭模型名称推断能力。

Limitations & considerations

Sources are insufficient to establish specific limitations. Verify task performance, latency, data policies, licensing and version lifecycle.

PRICING & COST

Source prices & cost analysis

Prices vary by channel, region and configuration. Channel quotes are listed independently and are not treated as a single official provider price.

Source / channelInputOutputBilling unitCollected at
No verified prices yet. Check the source channel.

Estimate monthly base token costs

—

Estimates exclude cache discounts, tiered pricing, multimodal surcharges, web search, taxes and additional reasoning output.

INDEPENDENT BENCHMARKS

Public benchmarks & run configuration

暂无已采集的可核验公开评分。模型未上榜不代表能力较低。

View full indexed rankings →

Frequently asked questions

Do open weights permit free commercial use?

Not necessarily. Check the version license, commercial conditions and usage policies. Self-hosting incurs compute and maintenance costs.

Are these real-time billing prices?

These are timestamped source snapshots, not live billing prices. Check the channel for current versions, regions, discounts and billing methods.

Sources & traceability

许可证:other。模型介绍与第三方评测均以原来源的具体版本和方法为准。