GLM-4.5-Air vs MiniMax-M3.1-Flash

GLM-4.5-Air

An English and Chinese cousin for agent, coding and tool-calling work, with switchable thinking and wide runtime support. It needs about 135 GB for Z.ai's FP8 build, two to four H100s by Z.ai's figures, and Z.ai and Novita host it. The main risk is age, with files from August 2025 and no answers from Z.ai since.

MiniMax-M3.1-Flash

A 428B mixture-of-experts model, 23B active, for agent work, coding and computer use, with image and video input, about 1M tokens of context and parallel tool calls. It needs a 4 to 8 GPU server for 250 GB of NVFP4 and MXFP8 weights, and vLLM and SGLang support was pre-release on 24 October 2026. Commercial use needs attribution and notice.

GLM-4.5-Air

1. Z.ai's FP8 recipe is python3 -m sglang.launch_server --model-path zai-org/GLM-4.5-Air-FP8 --tp-size 4 --tool-call-parser glm45 --reasoning-parser glm45, and 2 H100s are enough below the full 128K context
2. Use the glm45 tool and reasoning parsers for this model, the glm47 parser in Z.ai's current README is for GLM-4.7
3. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, which makes the template add /nothink and an empty think block
4. Declare tools in OpenAI style, and the template renders arguments as arg_key and arg_value pairs that the parser turns back into JSON
5. Keep prompts under 128,000 tokens, the tokenizer config's limit, though config.json allows 131,072
6. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented for the weights

MiniMax-M3.1-Flash

1. Check the use case first; commercial products must show "Built with MiniMax M3.1-Flash" and notify MiniMax once, or get written authorisation above $20M yearly revenue
2. On 8 H100 or H200 GPUs use vLLM's nightly image vllm/vllm-openai:minimax-m31-flash with --tensor-parallel-size 8 --block-size 128 --kv-cache-dtype fp8 --moe-backend marlin --max-model-len 262144
3. Pass --reasoning-parser minimax_m3 --tool-call-parser minimax_m3 --enable-auto-tool-choice in vLLM, or minimax-m3 for both in SGLang with --trust-remote-code
4. --block-size 128 is mandatory in vLLM, since MSA's sparse block size is 128
5. Set effort per request with chat_template_kwargs reasoning_effort (low, medium, high, xhigh, max); sample at temperature 1.0 and top_p 0.95
6. On Blackwell or MI355X, 4 GPUs serve it with the DSpark draft from dspark/; vLLM's Hopper command leaves DSpark off and turns video input off
7. For GGUF builds by others, use llama.cpp b11861 or later; earlier builds mis-scale the NVFP4 experts and produce garbage
8. Without the hardware, call MiniMax-M3.1-Flash on MiniMax's API (minimax-api), whose thinking defaults to max effort