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 | — |
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 | 200k |
| API pricingUSD per 1M tokens · lower wins | ||
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 | — | |
| These models have no shared benchmark scores. | ||
BullshitBench v2Nonsense detection — Given a confidently-worded but nonsensical prompt, does the AI spot that it makes no sense and push back — instead of playing along and inventing an answer? The score is how often it clearly called out the nonsense. Higher is better. | — | 31% |
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 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% | — |
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% | — |
ZClawBenchOpenClaw task performance — mean task score on a zero-to-one scale across 116 OpenClaw tasks | — | 0.564 |
| Overview | ||
| Company | Qwen | Z.ai |
| Release date | Feb 3 2026 | Mar 15 2026 |
| Access | Open Weight | Closed |
| Model details | View model | View model |
Other comparisons
Qwen3-Coder-NextvsClaude Fable 5.2GLM-5-TurbovsClaude Fable 5.2Qwen3-Coder-NextvsGPT-6.2 AstraGLM-5-TurbovsGPT-6.2 AstraQwen3-Coder-NextvsGemini 4 HydrogenGLM-5-TurbovsGemini 4 HydrogenQwen3-Coder-NextvsMuse EmberGLM-5-TurbovsMuse EmberQwen3-Coder-NextvsGrok 4.7GLM-5-TurbovsGrok 4.7Qwen3-Coder-NextvsDeepSeek-V4.1-Flash-1017GLM-5-TurbovsDeepSeek-V4.1-Flash-1017Frequently asked questions
Qwen3-Coder-Next and GLM-5-Turbo don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Qwen3-Coder-Next shipped 40 days before GLM-5-Turbo, so benchmark comparisons should account for the intervening progress.
Context windows are 256k (Qwen3-Coder-Next) vs 200k (GLM-5-Turbo). Qwen3-Coder-Next is open weight, while GLM-5-Turbo is closed.
Direct benchmark comparisons are unavailable — Qwen3-Coder-Next and GLM-5-Turbo don't publish scores on any of the same benchmarks.