Skip to main content

Model comparison

GLM-5.1 vs Grok 4.3

Updated July 30, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.

GLM-5.1

Z.AI

66.8/100

Supported · Public rank #22

90% interval 57.0–76.7

Grok 4.3

xAI

64.2/100

Supported · Public rank #36

90% interval 54.5–74.0

GLM-5.1 has the higher public score estimate, 66.84 versus 64.2, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.

2 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.

  • Long documents

    Prompts that approach the documented context limit

    Grok 4.3

    Grok 4.3 has the larger documented context window.

    Confidence: documented

  • Chat turn cost

    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

Show secondary and unsupported calls
  • Repository review cost

    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

  • 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

  • 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.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

What is actually comparable

Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.

Shared results
2
GLM-5.1 only
18
Grok 4.3 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.

Agentic

Not comparable
GLM-5.1
65.4
Grok 4.3
Not measured
Weighted basis
2 vs 0 rows
Reading
Not comparable

Coding

Not comparable
GLM-5.1
61.3
Grok 4.3
Not measured
Weighted basis
2 vs 0 rows
Reading
Not comparable

Reasoning

Not comparable
GLM-5.1
Not measured
Grok 4.3
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Knowledge

Not comparable
GLM-5.1
52.3
Grok 4.3
Not measured
Weighted basis
1 vs 0 rows
Reading
Not comparable

Math

Not comparable
GLM-5.1
62.0
Grok 4.3
Not measured
Weighted basis
4 vs 0 rows
Reading
Not comparable

Multilingual

Not comparable
GLM-5.1
Not measured
Grok 4.3
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Multimodal

Not comparable
GLM-5.1
Not measured
Grok 4.3
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Instruction following

Not comparable
GLM-5.1
Not measured
Grok 4.3
Not measured
Weighted basis
0 vs 0 rows
Reading
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.1
$0.0036
Fits in one request
Grok 4.3
$0.0025
Fits in one request

Grok 4.3 has the lower modeled cost

Costs use the listed standard API rates.

Repository review

50K fresh input + 3K output tokens

GLM-5.1
$0.0832
Fits in one request
Grok 4.3
$0.07
Fits in one request

Grok 4.3 has the lower modeled cost

Costs use the listed standard API rates.

Cache-heavy agent loop

200K cached + 20K fresh input + 10K output tokens

GLM-5.1
$0.352
Does not fit in one request
Cached input priced at the published list-input rate
Grok 4.3
$0.09
Fits 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.

Specification differences

Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.

Context window

Maximum documented context; output-token limits may be lower.

GLM-5.1

203K

Grok 4.3

1M

API model ID

GLM-5.1

Not sourced

Grok 4.3

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.1

Not published

Grok 4.3

$0.2 per 1M cached input tokens

Documented inputs

GLM-5.1

Not sourced

Grok 4.3

Not sourced

Documented outputs

GLM-5.1

Not sourced

Grok 4.3

Not sourced

Provider availability

GLM-5.1

Not sourced

Grok 4.3

Not sourced

Reasoning profile

GLM-5.1

Reasoning

Grok 4.3

Reasoning

Weight access

GLM-5.1

Open Weight

Grok 4.3

Proprietary

License

GLM-5.1

Open Weight

Grok 4.3

Proprietary

Release date

GLM-5.1

2026-04-07

Grok 4.3

2026-04-30

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
GLM-5.1 has the higher public score estimate, 66.84 versus 64.2, but the 90% score intervals overlap.
Workload cost
Repository review: $0.0832 vs $0.07. Cache-heavy agent loop: $0.352 vs $0.09.
Context tradeoff
Grok 4.3 has the larger documented window (1M).

Run the same representative tasks against both endpoints before changing production traffic.

Self-host vs API cost

Estimates at 50,000 req/day · 1000 tokens/req average.

GLM-5.1
API / mo$4,350
Self-host / mo$18,221
Break-even264M/day
Grok 4.3
API / mo$2,813
Self-host / moNot listed
Break-even
Proprietary model — self-hosting not applicable.
Model the full break-even

Benchmark evidence

The full public result ledger is available for audit without forcing a wide desktop table onto a phone.

Browse raw public benchmark evidence20 rows

Agentic

  • Terminal-Bench 2.0

    GLM-5.163.5%
    Source
    Grok 4.3

    Not directly comparable

  • BrowseComp

    GLM-5.168%
    Source
    Grok 4.3

    Not directly comparable

  • τ³-bench results

    GLM-5.170.6%
    Source
    Grok 4.3

    Not directly comparable

  • MCP Atlas

    GLM-5.171.8%
    Source
    Grok 4.3

    Not directly comparable

  • CyberGym

    GLM-5.168.7%
    Source
    Grok 4.3

    Not directly comparable

  • Claw-Eval

    GLM-5.162.3%
    Source
    Grok 4.3

    Not directly comparable

  • GLM-5.160.11%
    Grok 4.343.86%

    GLM-5.1 leads this result

  • ResearchClawBench

    Shared source
    GLM-5.118.2%
    Grok 4.312.4%

    GLM-5.1 leads this result

Coding

  • SWE-bench Pro

    GLM-5.158.4%
    Source
    Grok 4.3

    Not directly comparable

  • NL2Repo

    GLM-5.142.7%
    Source
    Grok 4.3

    Not directly comparable

  • SWE-Rebench

    GLM-5.162.7%
    Source
    Grok 4.3

    Not directly comparable

  • Vibe Code Bench

    GLM-5.131.46%
    Source
    Grok 4.3

    Not directly comparable

Knowledge

  • GPQA-D

    GLM-5.186.2%
    Source
    Grok 4.3

    Not directly comparable

  • HLE

    GLM-5.152.3%
    Source
    Grok 4.3

    Not directly comparable

Math

  • AIME26

    GLM-5.195.3%
    Source
    Grok 4.3

    Not directly comparable

  • HMMT Nov 2025

    GLM-5.194.0%
    Source
    Grok 4.3

    Not directly comparable

  • HMMT Feb 2026

    GLM-5.182.6%
    Source
    Grok 4.3

    Not directly comparable

  • MMAnswerBench

    GLM-5.183.8%
    Source
    Grok 4.3

    Not directly comparable

  • FrontierMath v2 (Tiers 1-3)

    GLM-5.133.448%
    Source
    Grok 4.3

    Not directly comparable

  • FrontierMath v2 (Tier 4)

    GLM-5.112.500%
    Source
    Grok 4.3

    Not directly comparable

Frequently asked questions

Which is better, GLM-5.1 or Grok 4.3?

GLM-5.1 has the higher public score estimate, 66.84 versus 64.2, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.

Which is better for coding, GLM-5.1 or Grok 4.3?

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.1 or Grok 4.3?

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.1 or Grok 4.3?

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.

Which has the larger context window, GLM-5.1 or Grok 4.3?

Grok 4.3 has the larger documented context window: 1M, compared with 203K.

Related comparisons

Last updated July 30, 2026

Watch GLM-5.1 vs Grok 4.3

One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.

Read a sample issue

Join 2,000+ readers.