Agentic
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Model comparison
GLM-5-Turbo vs SLAM-Omni
Updated August 4, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. Use the documented cost, context, and runtime rows instead.
0 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.
Which one for your work
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.
No workload recommendation clears the current evidence threshold.
Use the matched evidence, workload costs, and sourced specifications below instead of treating a point score as a universal answer.
Show secondary and unsupported calls
Coding work
Code generation, repair, and software-engineering tasks
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
Agentic work
Tool use, computer use, and multi-step task completion
Not enough matched evidence
No shared weighted benchmark basis supports a winner.
Confidence: limited
Long documents
Prompts that approach the documented context limit
Not enough matched evidence
A complete context comparison is not sourced.
Confidence: limited
Chat turn cost
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
Cache-heavy agent loop cost
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-Turbo does not fit this workload in one request. GLM-5-Turbo has no published cached-input rate, so cached tokens use its listed input rate. SLAM-Omni has no comparable published API token rate.
Confidence: rate-fallback
Repository review cost
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
What is actually comparable
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
1 GLM-5-Turbo only
- Shared results
- 0
- GLM-5-Turbo only
- 1
- SLAM-Omni only
- 0
- Like-for-like categories
- 0 / 8
Category results, on a stated basis
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.
Coding
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Reasoning
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Knowledge
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Math
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Multilingual
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Multimodal
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
Instruction following
Not comparable- GLM-5-Turbo
- Not measured
- SLAM-Omni
- Not measured
- Weighted basis
- 0 vs 0 rows
- Reading
- Not comparable
| Category | GLM-5-Turbo | SLAM-Omni | Weighted basis | Reading |
|---|---|---|---|---|
| Agentic | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Coding | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Reasoning | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Knowledge | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
| Math | 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 | Not measured | Not measured | Not comparable0 vs 0 rows | Not comparable |
Shape of the matched evidence
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
A shared-evidence shape is not available.
BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.
What each workload costs
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.
Chat turn
1K fresh input + 500 output tokens
- GLM-5-Turbo
- $0.0032
- Fits in one request
- SLAM-Omni
- API rate not published
- Fit state unavailable
SLAM-Omni has no comparable published API token rate.
Repository review
50K fresh input + 3K output tokens
- GLM-5-Turbo
- $0.072
- Fits in one request
- SLAM-Omni
- API rate not published
- Fit state unavailable
SLAM-Omni has no comparable published API token rate.
Cache-heavy agent loop
200K cached + 20K fresh input + 10K output tokens
- GLM-5-Turbo
- $0.304
- Does not fit in one request
- Cached input priced at the published list-input rate
- SLAM-Omni
- API rate not published
- Fit state unavailable
- Cached-input rate unavailable
GLM-5-Turbo does not fit this workload in one request. GLM-5-Turbo has no published cached-input rate, so cached tokens use its listed input rate. SLAM-Omni has no comparable published API token rate.
Specification differences
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
SpecificationGLM-5-TurboSLAM-Omni
Context window
Maximum documented context; output-token limits may be lower.
GLM-5-Turbo
200K
SLAM-Omni
N/A
API model ID
GLM-5-Turbo
Not sourced
SLAM-Omni
Not sourced
Cached-input rate
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
GLM-5-Turbo
Not published
SLAM-Omni
No comparable hosted API rate
X-LANCE model documentationDocumented inputs
GLM-5-Turbo
Not sourced
SLAM-Omni
Not sourced
Documented outputs
GLM-5-Turbo
Not sourced
SLAM-Omni
Not sourced
Provider availability
GLM-5-Turbo
Not sourced
SLAM-Omni
Not sourced
Reasoning profile
GLM-5-Turbo
Reasoning
SLAM-Omni
Non-Reasoning
Weight access
GLM-5-Turbo
Proprietary
SLAM-Omni
Open Weight
License
GLM-5-Turbo
Proprietary
SLAM-Omni
Open Weight
Release date
GLM-5-Turbo
2026-03-01
SLAM-Omni
2024-12-20
If you already use one of these models
- Deployment change
- The models list different providers, so authentication, endpoint behavior, limits, and feature support may change.
- Quality signal
- The public evidence has no benchmark result shared by both models, so it does not support a quality verdict.
- Workload cost
- A complete comparable API-rate estimate is not available for both models.
- Context tradeoff
- A complete documented context comparison is not available.
Run the same representative tasks against both endpoints before changing production traffic.
Benchmark evidence
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Browse raw public benchmark evidence1 rows
Agentic
Claw-Eval
GLM-5-Turbo55.8%SourceSLAM-Omni—Not directly comparable
Frequently asked questions
Which is better, GLM-5-Turbo or SLAM-Omni?
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. The page therefore keeps the decision tied to the specific documented workload.
Which is better for coding, GLM-5-Turbo or SLAM-Omni?
The published evidence does not provide a shared weighted coding basis for both models, so BenchLM does not name a coding winner.
Which is better for agentic tasks, GLM-5-Turbo or SLAM-Omni?
The published evidence does not provide a shared weighted agentic tasks basis for both models, so BenchLM does not name a agentic tasks winner.
Which costs less, GLM-5-Turbo or SLAM-Omni?
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Which has the larger context window, GLM-5-Turbo or SLAM-Omni?
A complete documented context-window comparison is not available.
Related comparisons
Last updated August 4, 2026
Watch GLM-5-Turbo vs SLAM-Omni
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.