GLM-4.5-Air vs Kimi K3

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.

Kimi K3

Kimi K3 is a 2.8T multimodal agent model with a 1M-token context, parallel tool calls and per-request effort, for long coding and research sessions. Its 1,561 GB of files need a multi-node GPU cluster, so most agents will call a hosted copy. The main risks are Moonshot's Python running at load and prompt time, and no answers in its repository.

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

Kimi K3

1. Start it with SGLang on a node of 8 B300s, sglang serve --trust-remote-code --model-path moonshotai/Kimi-K3 --tp-size 8 --context-length 65536 --mem-fraction-static 0.82 --reasoning-parser kimi_k3 --tool-call-parser kimi_k3 --port 30000
2. Use the kimi_k3 tool-call and reasoning parsers in vLLM or SGLang, and validate tool-call arguments against the schema, since vLLM's recipe says K3 sometimes emits a format its parser doesn't expect
3. Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
4. Thinking is always on; set reasoning_effort to low or high when max is too slow
5. Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
6. Don't hand an ongoing session from another model to K3, and state boundaries in the system prompt, since Moonshot warns it can act on its own when intent is unclear
7. Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page