Coding
Like-for-like- GLM-5.1
- 56.4
- Supported · #38/151
- Grok 4.3
- 33.6
- Supported · #131/151
- Basis
- BenchAlign lane · 7 vs 2 public rows
- Reading
- GLM-5.1 leads
Keep up with the models you depend on. Follow price changes, retirements, and API updates.Follow the models you depend on.
Follow model changesUpdated September 10, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
Decision reading
GLM-5.1 has the higher public score estimate, 63.24 versus 59.73, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.
7 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.
Share or export
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
Code generation, repair, and software-engineering tasks
GLM-5.1
GLM-5.1 leads on the public coding lane, 56.4 to 33.6, with Supported evidence for both models and non-overlapping 90% intervals.
Confidence: stronger
Prompts that approach the documented context limit
Grok 4.3
Grok 4.3 has the larger documented context window.
Confidence: documented
1K fresh input + 500 output tokens
Grok 4.3
Grok 4.3 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
Confidence: listed-rates
50K fresh input + 3K output tokens
Grok 4.3
Grok 4.3 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.
Confidence: listed-rates
Tool use, computer use, and multi-step task completion
Not enough matched evidence
GLM-5.1 is scored on Estimated evidence for agentic, so the reading is directional rather than like-for-like.
Confidence: limited
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. GLM-5.1 does not fit this workload in one request. GLM-5.1 has no published cached-input rate, so cached tokens use its listed input rate.
Confidence: rate-fallback
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
2 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Each row shows the public-lane category score for both models: the BenchAlign lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.
| Category | GLM-5.1 | Grok 4.3 | Basis | Reading |
|---|---|---|---|---|
| Coding | 56.4Supported · #38/151 | 33.6Supported · #131/151 | Like-for-likeBenchAlign lane · 7 vs 2 public rows | GLM-5.1 leads |
| Knowledge | 54.8Supported · #54/183 | 57.0Supported · #44/183 | Like-for-likeBenchAlign lane · 4 vs 2 public rows | Grok 4.3 leads · intervals overlap |
| Agentic | 54.3Estimated · #37/152 | 26.9Supported · #144/152 | Directional onlyBenchAlign lane · 9 vs 3 public rows | Directional only |
| Instruction following | 93.7#5/123 | 94.4#2/123 | Directional onlyProvisional lane · 0 vs 0 weighted rows | Directional only |
| Reasoning | 71.7Unranked · 2 rankable rows | 65.2Unranked · 2 rankable rows | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Math | 64.1#3/7 | Not ranked | Not comparableProvisional lane · 4 vs 0 weighted rows | Not comparable |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multimodal | Not ranked | 65.6#25/48 | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign) differ from the provisional-lane categories. Unranked scores sit on the lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.
LiveCodeBench (Vals)
Coding
MMLU-Pro (Vals)
Knowledge
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
1K fresh input + 500 output tokens
Grok 4.3 has the lower modeled cost
Costs use the listed standard API rates.
50K fresh input + 3K output tokens
Grok 4.3 has the lower modeled cost
Costs use the listed standard API rates.
200K cached + 20K fresh input + 10K output tokens
GLM-5.1 does not fit this workload in one request. GLM-5.1 has no published cached-input rate, so cached tokens use its listed input rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
GLM-5.1
203K
Grok 4.3
1M
GLM-5.1
Not sourced
Grok 4.3
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
GLM-5.1
Not published
Grok 4.3
$0.2 per 1M cached input tokens
GLM-5.1
Not sourced
Grok 4.3
Not sourced
GLM-5.1
Not sourced
Grok 4.3
Not sourced
GLM-5.1
Not sourced
Grok 4.3
Not sourced
GLM-5.1
Reasoning
Grok 4.3
Reasoning
GLM-5.1
Open Weight
Grok 4.3
Proprietary
GLM-5.1
Open Weight
Grok 4.3
Proprietary
GLM-5.1
2026-04-07
Grok 4.3
2026-04-30
Run the same representative tasks against both endpoints before changing production traffic.
Estimates at 50,000 req/day · 1000 tokens/req average.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Terminal-Bench 2.0
Not directly comparable
BrowseComp
Not directly comparable
τ³-bench results
Not directly comparable
MCP Atlas
Not directly comparable
CyberGym
Not directly comparable
Claw-Eval
Not directly comparable
Gert Labs
Shared sourceGLM-5.1 leads this result
ResearchClawBench
Shared sourceGLM-5.1 leads this result
Terminal-Bench 2.1 (Vals)
GLM-5.1 leads this result
SWE-bench Pro
Not directly comparable
NL2Repo
Not directly comparable
SWE-Rebench
Not directly comparable
Vibe Code Bench
Not directly comparable
OpenHarmony Bench
Not directly comparable
LiveCodeBench (Vals)
Grok 4.3 leads this result
SWE-bench (Vals)
GLM-5.1 leads this result
AIME26
Not directly comparable
HMMT Nov 2025
Not directly comparable
HMMT Feb 2026
Not directly comparable
MMAnswerBench
Not directly comparable
FrontierMath v2 (Tiers 1-3)
Not directly comparable
FrontierMath v2 (Tier 4)
Not directly comparable
GLM-5.1 has the higher public score estimate, 63.24 versus 59.73, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
GLM-5.1 leads the public coding lane, 56.4 to 33.6, with Supported evidence for both models and non-overlapping 90% intervals.
GLM-5.1 scores higher for agentic tasks on the public lane, 54.3 to 26.9. GLM-5.1 is scored on Estimated evidence for agentic tasks, so the reading is directional rather than like-for-like. BenchLM does not name a winner for agentic tasks from a directional reading; read the shared benchmark rows directly and test the models on the same task set.
For the stated presets, chat costs $0.0036 on GLM-5.1 and $0.0025 on Grok 4.3; repository review costs $0.0832 and $0.07; the cache-heavy agent loop costs $0.352 and $0.09. GLM-5.1 does not fit this workload in one request. GLM-5.1 has no published cached-input rate, so cached tokens use its listed input rate.
Grok 4.3 has the larger documented context window: 1M, compared with 203K.
Last updated September 10, 2026
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.