MiniMax-M3.1-Flash-Preview pricing, plans and limits

The model is built for agentic reasoning, tool use, coding, and long-context tasks, per MiniMax's official API documentation. It supports a context window of up to 1,000,000 tokens for long documents, codebases, and multi-step agent sessions, and accepts multimodal chat input across text, images, and video. MiniMax has not disclosed a parameter count, active-expert count, or architecture family (dense vs. Mixture-of-Experts) specifically for this variant, in contrast to sibling MiniMax-M3, documented separately as a 229.9B-parameter Mixture-of-Experts model with MiniMax Sparse Attention.

The defining mechanical feature is tunable reasoning depth. The effort parameter (output_config.effort on the Anthropic-compatible endpoint, reasoning_effort on the OpenAI-compatible endpoint) accepts low, medium, high, xhigh, and max, with higher levels producing more thorough reasoning at higher latency and token cost. Omitting the parameter defaults to max, the deepest and slowest setting. Reasoning cannot be switched off: sending thinking:{type:"disabled"} or effort:"none" returns an HTTP 400 error stating the model requires adaptive thinking.

No official benchmark suite has been published for M3.1-Flash-Preview. It does not appear on Artificial Analysis's index, and no responsible SWE-bench, GPQA, or Terminal-Bench figure exists for it from MiniMax itself, unlike published rivals such as DeepSeek V4 and DeepSeek V4 Flash. Scattered third-party community testing exists, but none of it is independently verified to a standard this page can responsibly repeat, so no benchmark scores are listed here; treat any vendor or blog claim of coding-quality gains as provisional until MiniMax releases formal evaluation numbers.

Access runs through two paths, and neither is a conventional metered API key at launch. MiniMax's Token Plan is a flat monthly subscription, tiered by usage volume (exact tier pricing is in the pricing FAQ below), covering M3.1-Flash-Preview alongside the rest of the M-series and MiniMax's image, speech, and video models, billed against 5-hour rolling and weekly usage quotas rather than per-token spend. The model is also usable directly inside MiniMax Code, MiniMax's own coding agent product. The model is entirely absent from MiniMax's public pay-as-you-go pricing table, which lists exact per-token rates for MiniMax-M3, M2.7, M2.7-highspeed, and the legacy M2.x line but nothing for M3.1-Flash-Preview. MiniMax's Token Plan documentation notes that once a subscription quota is exhausted, usage can fail over to a standard pay-as-you-go API key, implying a metered price exists internally, but no such rate has been published for this model as of this writing.

MiniMax aims the model squarely at everyday engineering work, bug fixes, refactors, and end-to-end feature implementation, rather than research-grade reasoning benchmarks, and documents integration guides for reaching it from several popular coding-agent tools, including Claude Code and Cursor (the full list is under Key Features below). Two request formats are documented, letting teams already wired to a major model SDK point their base URL at MiniMax and swap in the model name rather than adopt a new client library.

MiniMax has not published a system card, named red-teaming partners, or a responsible scaling policy for the M-series generally, and no model-specific safety disclosure accompanies this preview. It also has not published SOC 2, ISO 27001, or HIPAA attestations for its platform as a whole. How MiniMax handles API inputs for training is covered in the FAQ below.

Overall, M3.1-Flash-Preview reads as MiniMax testing a faster, subscription-gated coding model ahead of a fuller rollout: the underlying capability, a huge context window and tunable reasoning, is real and documented, but the commercial and evaluation groundwork other frontier launches ship with, pricing, benchmarks, and a system card, has not caught up yet. The FAQ below covers exactly who it fits today.