Open-weight 30B-A3B reasoning model with 200K context and 128K output for low-cost agentic coding and tool use.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Agentic Coding Results Well Above Its 3B Active-Parameter Class
Benchmarks
Independent Data: Index Score of 15, Strong Tool Use, Below-Median Speed
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Coding agents and issue triage
Z.ai reports 59.2 on SWE-bench Verified, and Artificial Analysis measures 22.0% on Terminal-Bench Hard with reasoning, up from 3.8% without it. That suits patch-generation loops, repository bug triage and terminal-style agents where many steps run per task. The model's lower intelligence ceiling means complex multi-file refactors may need escalation to GLM-4.7 or a larger model.
Multi-step tool-calling pipelines
The model supports function calling with automatic tool choice. Z.ai reports 79.5 on τ²-Bench, and Artificial Analysis measures 98.8% on τ²-Bench Telecom. Z.ai recommends Preserved Thinking for multi-turn agent tasks. This fits workflow agents that call internal APIs and reason across turns, as long as the reasoning delay is acceptable for background execution.
Long-context document analysis
A 200K-token window lets the model read large codebases, logs or report sets in one request. Artificial Analysis AA-LCR scores 41.7% with reasoning versus 20.3% without, so thinking helps long-context work. Treat it as moderate rather than best-in-class, and ground answers against the source text, since factual recall without context is weak.
Open-weight prototyping and self-hosting paths
The weights are MIT-licensed on Hugging Face. Lambda lists 62.5GB of weights and a single H100 or B200 as a minimal deployment, with more GPUs for the full 200K context. Teams can prototype through an API, then move to private infrastructure if data-control needs grow. Full-context self-hosting is memory-heavy.