Unverified60% confidenceFactExact time
MiniMax M3.1 Flash defaults to the max setting when the effort field is not passed in the request, and the model always performs thinking.
2
Sources
60%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedMiniMax M3.1 Flash's thinking tokens count toward the max_tokens limit, so reusing the 4K or 8K caps from the M2.x era may cause truncation with finish_reason: "length"; MiniMax recommends raising max_tokens to 131,072, with an upper limit of 524,288.78% similarUnverifiedMiniMax M3.1 Flash cannot disable thinking: passing thinking: {"type": "disabled"} or setting effort to none returns HTTP 400 with the error message model "MiniMax-M3.1-Flash" requires adaptive thinking.77% similarUnverifiedBecause Flash models have fast inference speeds (50–200ms per request vs. 500–2000ms for flagship models), they can support higher QPS under the same TPM limits.75% similarUnverifiedCompared with MiniMax M2.7, M3.1 Flash's context window expands from 204,800 to 1,000,000, its input types expand from text-only to text, images, and video, and its thinking mode changes from always-on with no levels to five adjustable levels defaulting to max.70% similarUnverifiedMaximum output tokens: MiniMax M3.1 Flash is 512K, DeepSeek V4.1 Flash 1017 is 384K, and Claude Haiku 5.5 is 128K.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067173API
curl https://kongchang.com/api/v1/knowledge/claims/1067173MCP
get_claim(id=1067173)