Compare AI models
| Specifications | ||
ParametersThe learned values that shape how a model responds. B means billion and T means trillion. For mixture-of-experts models, the total count is larger than the number active for each token. Parameter count alone does not measure quality. | 80B | 9B/32B |
Context windowHow much information the model can work with in one request, measured in tokens — pieces of words or other data. This includes your question, attachments, conversation and reply. Limits can vary by model variant and provider. | 256k | 128k |
| API pricingUSD per 1M tokens · lower wins | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | — | $0.1032B checkpoint |
Output priceWhat you pay for the text the model writes back. It is normally the dearer half: producing an answer costs more than reading one. | — | $0.10 |
Cheapest inputLowest input rate across every provider on OpenRouter, the lab included. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $0.12Parasail | — |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $0.80Parasail | — |
| $64.00Parasail · bf16 | $25.00Z.ai list price | |
| Benchmarks | ||
SWE-Bench VerifiedCoding — Real coding tasks pulled from open-source projects — the AI has to find and fix actual bugs. A human-checked version of the original SWE-Bench. Higher is better. | 70.6% | 27.2% |
SWE-Bench ProAgentic coding — Can the AI fix real bugs in real software? It's handed actual problems from open-source projects and has to write code that genuinely solves them. Higher is better. | 44.3% | — |
SWE-Bench MultilingualMultilingual coding — Like SWE-Bench, but the coding problems span many programming languages, not just one. Tests how broadly the AI can code. Higher is better. | 62.8% | — |
Terminal-Bench 2.0Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? (Version 2.0 of the test.) Higher is better. | 36.2% | — |
IFEvalAgentic tasks — following verifiable instructions in generated responses | — | 87.6% |
| Overview | ||
| Company | Qwen | Z.ai |
| Release date | Feb 3 2026 | Apr 14 2025 |
| Access | Open Weight | Open Weight |
| Model details | View model | View model |
Other comparisons
Qwen3-Coder-NextvsClaude Fable 5.2GLM-4-0414vsClaude Fable 5.2Qwen3-Coder-NextvsGPT-6.2 AstraGLM-4-0414vsGPT-6.2 AstraQwen3-Coder-NextvsGemini 4 HydrogenGLM-4-0414vsGemini 4 HydrogenQwen3-Coder-NextvsMuse EmberGLM-4-0414vsMuse EmberQwen3-Coder-NextvsGrok 4.7GLM-4-0414vsGrok 4.7Qwen3-Coder-NextvsDeepSeek-V4.1-Flash-1017GLM-4-0414vsDeepSeek-V4.1-Flash-1017Frequently asked questions
Qwen3-Coder-Next leads GLM-4-0414 on 1 of the 1 benchmark they both report (SWE-Bench Verified). Only GLM-4-0414 has a verified first-party price for an available API: $0.10 per million input tokens and $0.10 per million output tokens. No currently available pay-as-you-go API rate is tracked for Qwen3-Coder-Next. The listed GLM-4-0414 rates use the “32B checkpoint” pricing scope. GLM-4-0414 shipped 295 days before Qwen3-Coder-Next, so benchmark comparisons should account for the intervening progress.
Qwen3-Coder-Next has 80B parameters, while GLM-4-0414 has 9B/32B. Context windows are 256k (Qwen3-Coder-Next) vs 128k (GLM-4-0414).
On SWE-Bench Verified, Qwen3-Coder-Next leads at 70.6% vs GLM-4-0414 at 27.2%.