Coding
Directional only- DeepSeek V3
- 38.9
- GLM-4.7
- 75.4
- Weighted basis
- 2 vs 3 rows
- Reading
- Directional only
Model comparison
Updated July 30, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
GLM-4.7 has the higher public score estimate, 60.39 versus 44.15, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.
5 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.
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.
Prompts that approach the documented context limit
GLM-4.7
GLM-4.7 has the larger documented context window.
Confidence: documented
Code generation, repair, and software-engineering tasks
Not enough matched evidence
The category averages use different weighted benchmark sets, so they are directional rather than like-for-like.
Confidence: limited
Tool use, computer use, and multi-step task completion
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
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. DeepSeek V3 does not fit this workload in one request. GLM-4.7 does not fit this workload in one request. GLM-4.7 has no comparable published API token rate.
Confidence: listed-rates
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Confidence: listed-rates
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
3 categories use different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Each row states whether both averages use the same weighted benchmark set. Directional and not-comparable rows remain visible, but they never receive a winner in this template.
| Category | DeepSeek V3 | GLM-4.7 | Weighted basis | Reading |
|---|---|---|---|---|
| Coding | 38.9 | 75.4 | Directional only2 vs 3 rows | Directional only |
| Knowledge | 72.7 | 51.8 | Directional only2 vs 3 rows | Directional only |
| Math | 1.7 | 1.8 | Directional only1 vs 2 rows | Directional only |
| Agentic | Not measured | 45.7 | Not comparable0 vs 2 rows | Not comparable |
| Reasoning | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Multilingual | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Multimodal | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Instruction following | 86.1 | Not measured | Not comparable1 vs 0 rows | Not comparable |
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
Coding
SWE-bench Verified
Coding
GPQA
Knowledge
MMLU-Pro
Knowledge
FrontierMath v2 (Tiers 1-3)
Math
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
GLM-4.7 has no comparable published API token rate.
50K fresh input + 3K output tokens
GLM-4.7 has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
DeepSeek V3 does not fit this workload in one request. GLM-4.7 does not fit this workload in one request. GLM-4.7 has no comparable published API token 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.
DeepSeek V3
128K
GLM-4.7
200K
DeepSeek V3
Not sourced
GLM-4.7
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
DeepSeek V3
$0.07 per 1M cached input tokens
GLM-4.7
No comparable hosted API rate
DeepSeek V3
Not sourced
GLM-4.7
Not sourced
DeepSeek V3
Not sourced
GLM-4.7
Not sourced
DeepSeek V3
Not sourced
GLM-4.7
Not sourced
DeepSeek V3
Non-Reasoning
GLM-4.7
Reasoning
DeepSeek V3
Open Weight
GLM-4.7
Open Weight
DeepSeek V3
Open Weight
GLM-4.7
Open Weight
DeepSeek V3
2024-12-26
GLM-4.7
2025-10-01
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.
FrontierMath v2 (Tiers 1-3)
Shared sourceGLM-4.7 leads this result
AIME 2025
Not directly comparable
FrontierMath v2 (Tier 4)
Not directly comparable
IFEval
Not directly comparable
GLM-4.7 has the higher public score estimate, 60.39 versus 44.15, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
The current coding averages use different weighted benchmark sets, so BenchLM does not name a winner from them. Read the shared benchmark rows directly and test the models on the same task set.
The published evidence does not provide a shared weighted agentic tasks basis for both models, so BenchLM does not name a agentic tasks winner.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
GLM-4.7 has the larger documented context window: 200K, compared with 128K.
Last updated July 30, 2026
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.