Cloud baseline

GLM 5.3 Prime — 0.6797 on Gauntlet 7.2

z-ai/glm-5.3-prime · scorer sb-7.2

GLM 5.3 Prime, single model via OpenRouterz-ai/glm-5.3-prime · single agentOct 7, 2026
Overall
0.6797
Excellent
no
Benchmark
Gauntlet 7.2
Model build
94m 11s
Prompt tok
34.9M
Gen tok
316.3k

Recorded inference cost

At least $23.23

From the saved OpenRouter generation billing summary (145 recorded requests). This is a lower bound; the billing record is incomplete. Includes auxiliary model calls made during the build. Scoring reuses the saved build; this amount describes the original inference spend.

  • The harness counted tokens no recovered generation id accounts for: prompt -972, completion -5

Token usage

Tokens: 34.9M in · 316k out · 34.5M cached (exact, OpenRouter records)

35,239,337 tokens over 145 model calls: every call of the run, the model's own and the harness's helper calls, counted from OpenRouter records. Reasoning tokens as the provider reports them: 191,262 (not added to the total).

  • z-ai/glm-5.3-prime-20260921

    In 34.9M · Out 316k · Cached 34.5M · Reasoning 191k · 144 calls

  • google/gemini-2.5-flash

    In 972 · Out 5 · Cached 0 · Reasoning 0 · 1 call

Tier breakdown

A · structure & runtime1.00
B · behaviour1.00
C · vendor contract1.00
D · finesse0.93

Scoring detail

How this score was built

Per-check scorer output, as posted by the app. Expand a section to inspect its checks.

Earned credit before admission

(0.88 × 0.8612 core + 0.12 × 0.87 gate × 0.60 excellence) × 0.8286 critical = 0.6797

Critical defects compound a multiplier on the whole score (pre-severity 0.8203):

j_workflow_journey 0.57 → ×0.83

The core (88% of the total) is the weighted mean of the thirteen measured tiers. The last 12% is the excellence slice: it unlocks in proportion to the perfection conditions below (13 of 16 met here), then pays out at the excellence tier's own measured mean. Core 0.7579 + excellence 0.0624.

j_first_use 1.00j_workflow_journey 0.57j_error_state 0.30j_empty_state 1.00console_clean 0.00v_responsive_375 1.00v_dates_readable 1.00t_scene_binding 1.00x_conservation_residual 1.00r_no_row_loss 1.00p_drag_frames 1.00p_idle_flatness 1.00p_stream_apply 0.00p_under_stream 1.00p_api_latency 1.00p_sync_wall 1.00

Earned score 0.680 · Admission ceiling 0.699 · Final score 0.680

Final score is the lower of earned credit and the admission ceiling. Passing admission adds no points.

Visible: passedMatching: not metGood: not metVisual excellence: not metBackend excellence: passed

Tower structure, currency mapping and scene truth: t_height_pixels (maximum 0.699)

3D interaction and overview legibility: t_camera_math, t_coast_identity, t_stream_diff, q_overview_legibility, q_inspector_framing (maximum 0.699)

Event animation and backend recovery: m_committed_event_replay (maximum 0.899)

Run notes and corrections

Scoring note, 2 November 2026. This run was graded by the sb-7.2 scorer as it was before harness version 3.0.148. That scorer had two blind spots that hit this build. It only noticed live updates arriving through the browser's EventSource, and this build reads /api/stream with fetch() instead, so p_stream_apply, t_stream_diff, e_stream_apply_latency and m_committed_event_replay may understate how the model did. It also only read notification text from elements with nothing nested inside them, unless the feed used a class name containing "notif". This build puts the kind in its own element inside each entry, so the scorer read none of its notifications, and the notification parts of j_workflow_journey and j_workflow_reject may understate it too. This build's files weren't kept, so it can't be re-graded with the fixed scorer, and the score stays as published.

Token rates

Measured by the engine itself, one record per completed model call: prefill rate is prompt tokens over time-to-first-token, generation rate is completion tokens over the decode window. Medians per node.

NodeCallsPrompt tokGen tokPrefill tok/sGen tok/s
gemini197251228.874.6
z14434,922,021316,33980448.768.0
fleet14534,922,993316,34479753.468.2

Graded browser recording

Loading duration…

Watch the full graded browser recording at its original speed: the payment field, structure inspection, committed updates and replay. The check results and screenshots on this page provide the wider evidence. Pause or scrub to inspect a view.

Each tower represents a payment: height encodes its amount, cap color its status, and the collar its currency. The selected detailed tower is expected to animate its collar after a committed backend update or replay. These are the task requirements; the check results show what this app actually achieved.

Ready to play0:00 / —:—
Open recording file

Drag the timeline to seek. Keyboard: arrow keys move 5 seconds; Home and End jump to the start and end.

Full graded browser recording: payment field, structure inspection, committed updates and replay

Screenshots

Captured from the built application during browser grading. Captions identify the recorded views and checks; these images do not represent repair rounds.

1Initial app view
2Error state
3Payment workflow
4First captured render
5Latest captured render

Run details

Model
z-ai/glm-5.3-prime
Engine events
0
Repair rounds
0
Started
Oct 7, 2026, 12:56 AM
Finished
Oct 7, 2026, 02:41 AM

How the benchmark is scored