Ox Alpha: Zhipu Confirmed — GLM Identity, Evidence Timeline, Open Weights (Aug 2026)

Update — September 5, 2026: OpenCode shipped a second stealth model, Omen Alpha — same playbook, unconfirmed identity, this time paid-only at ~$0.20/M input tokens. Full coverage: Omen Alpha: OpenCode's new stealth model.

Update — August 26, 2026 (evening): Z.ai named the model GLM-5.3-Flash — 320B-A18B, MIT license, 1M multimodal context, API $0.15/$0.50 per M tokens. Full launch coverage: GLM-5.3-Flash official post.

Update — August 26, 2026: Z.AI (Zhipu) confirmed to Bloomberg News that Ox Alpha is a new iteration of its GLM series and said it would release the weights tonight. Ox Alpha had already hit #1 on OpenRouter's leaderboard, more than doubling DeepSeek's usage — Bloomberg frames it as the marketplace's biggest single-model launch. Community forensics pointing at GLM-5.3 / GLM-5.3-Flash were vindicated at the lab level; the exact public model name on Hugging Face may still differ until Zhipu publishes a card. See also GLM-5.3 launch context.

Ox Alpha is Zhipu AI's GLM model — officially confirmed August 26, 2026 via Bloomberg, after a week of anonymous stealth on OpenRouter. OpenRouter listed it under the generic "Stealth" provider from August 20; OpenCode called it "the stealth model." Independent researchers had already moved past vibes by August 22: serving-layer forensics pointed to Z.AI infrastructure — a Java stack trace naming Zhipu's internal API classes, an identical error-code dialect shared with GLM models on OpenRouter, and tokenizer matches on 30/30 probes.

The mystery is over at the lab level. What's still open: the exact GLM SKU Zhipu ships on Hugging Face tonight, and whether OpenRouter retires the stealth/ox-alpha slug for a named z-ai/... route.

TL;DR

The evidence, ranked by how much it actually proves

Most "who made Ox Alpha" coverage still lists vibes-based guesses. Here's what actually happened — updated August 22, 2026 — ranked from strongest to weakest.

1. Serving-layer stack trace (strongest — August 22)

Researcher Chetaslua (@chetaslua) sent a malformed request to OpenCode's direct Ox Alpha route — top_p set to the string "abc" instead of a number — and the server returned a Java stack trace naming its own internal class:

com.wd.paas.api.domain.v4.chat.ChatCompletionRequest

That package path maps directly to Zhipu's documented API route: /api/paas/v4/chat/completions on both open.bigmodel.cn and api.z.ai. This is not a tokenizer coincidence or an output-style match — it is the upstream server exposing its own Java domain model when validation fails.

Chetaslua's read: the stack trace is serving-layer evidence, not a fingerprint guess — and rates operator-layer confidence at 0.98. explainx.ai's read: that is the strongest independent signal so far, but still not the same as Zhipu naming the model.

Reproducible one-liner (via OpenCode's Zen endpoint — screenshot the stack trace while it still leaks; OpenCode may patch the error handler):

curl -s -X POST https://opencode.ai/zen/v1/chat/completions \
  -H "content-type: application/json" \
  -d '{"model":"x-preview-f-free","messages":[{"role":"user","content":"hi"}],"top_p":"abc"}'

The malformed-field trick forces the validation layer to surface implementation details that normal requests never expose. Treat this as live forensic evidence that can disappear once the bug is patched — not a permanent API feature.

2. Error-code dialect: operator fingerprint (strong — August 22)

Chetaslua ran the same malformed-role test against multiple GLM endpoints and found a clean split:

The control case is the killer detail: same weights, different host, different error dialect. That means the signature belongs to who operates the API, not to the model checkpoint in isolation. Ox Alpha's error envelope lines up with Z.AI's operator stack, not a generic OpenAI-compatible wrapper.

Unclecode's earlier 9-probe infrastructure forensics (tokenizer + error codes + templates across 12 suspects) had already pointed GLM as the only family hitting 4/4 — Chetaslua's August 22 work adds serving-layer proof on top of that.

3. Tokenizer fingerprinting — 30/30 probes (strong)

Researcher @aitrackerbot ran diverse prompts through Ox Alpha and recorded exact token counts against known tokenizers. Chetaslua expanded this to 30/30 probes across 14 writing systems, emoji, code, and SQL, all matching GLM-5.3.

The original @aitrackerbot pass (25 prompts) found Ox Alpha's native token counts matched GLM-5.3 exactly apart from a constant +75-token hidden wrapper on every request — the signature of a system prompt or routing wrapper, not evidence against the match.

4. Video-encoder analysis across 4 test videos (strong — and modality-specific)

The same researcher went further with video inputs, since Ox Alpha accepts video and most rival candidates don't, or handle it differently. Testing four controlled videos, Ox Alpha's token spend matched GLM-5V-Turbo — Zhipu's own multimodal agent model, documented in Zhipu's arXiv paper on GLM-5V-Turbo — token-for-token identical, across three independent encoder design choices:

• FPS-invariant frame sampling — how many frames get extracted regardless of the source video's frame rate
• ~147 tokens/second duration scaling — how token cost grows with video length
• Per-frame resolution scaling — how token cost changes with frame resolution

Three independent design choices matching exactly is a much harder coincidence to explain away than a single number lining up.

5. Elimination of rival candidates (corroborating)

The same test suite was run against the other names actually in circulation — MiMo v2.5, Qwen 3.8 Max, and GLM-4.6V — and none of them matched. All three produced clearly different tokenizer and/or encoder signatures from Ox Alpha.

One elimination is worth calling out specifically: Ox Alpha rejects audio input, routing it the same way GLM-5V does (no audio endpoint exposed at all). MiMo v2.5, by contrast, accepts and tokenizes audio. That's a binary behavioral difference, not a statistical fingerprint — either a model has an audio endpoint or it doesn't — which makes it a clean disqualifier for the MiMo theory specifically, independent of the tokenizer and video evidence.

6. Insider-adjacent commentary (weak, but corroborating)

dax (@thdxr — associated with OpenCode, which shipped its own direct Ox Alpha integration the same week) posted, in reply to the fingerprinting thread circulating: "i told you guys we had more guess what model it is." Read plainly, that's someone with plausible closeness to the routing/serving side signaling agreement with the GLM-5.3 theory — not an on-the-record confirmation, and not sourced to anything beyond a tweet, but a data point worth weighing above an anonymous forum guess.

What this rules against: the MiMo and Qwen theories

Before the fingerprinting results, the two most common guesses in replies and Reddit threads were Xiaomi's MiMo (on the pattern precedent that past stealth models — Hunter Alpha and Healer Alpha — both turned out to be MiMo) and, less commonly, Qwen 3.8 27B or Qwen 3.8 Max (a specific claim that circulated on Reddit's r/opencodeCLI without published supporting evidence).

Both are now weaker theories than they were on launch day:

• MiMo v2.5 is directly contradicted by the audio-endpoint behavior difference above.
• Qwen 3.8 Max was included in the same fingerprinting pass and produced a different tokenizer/encoder signature than Ox Alpha — the Reddit claim doesn't hold up against the actual test.

The MiMo precedent is still worth understanding even though it's now the less likely answer here: Hunter Alpha and Healer Alpha, two earlier OpenRouter stealth previews, were both eventually confirmed as Xiaomi MiMo releases after their preview windows ended. That's real precedent for "stealth listing → later official reveal" as a pattern — it just points to a different lab as the actual match this time, based on the fingerprinting evidence specifically.

Why would Zhipu ship this anonymously?

If the GLM-5.3 theory holds, the obvious question is why a lab would hide its own model rather than launch it under the GLM name. The Hunter/Healer-as-MiMo precedent answers this directly: an anonymous stealth listing on a neutral platform collects real-world usage, benchmark results, and failure modes at massive scale — Ox Alpha's own OpenRouter dashboard shows Claude Code and Hermes Agent alone pushing billions of tokens through it within days — before the model has to carry a lab's name and reputation into that scrutiny. It's a lower-risk way to stress-test a frontier checkpoint against real production traffic before a formal launch.

What's still open after the Bloomberg confirmation

Zhipu's statement confirms lab and GLM lineage, not every detail the community inferred:

Until the weights and model card land, treat "GLM-5.3-Flash" as the best community label — vindicated by forensics and leaks like @LuminaBench's thread — not as Zhipu's official product name unless the card says so.

Why the stealth launch pattern still mattered

Even now that Zhipu confirmed ownership, the Hunter/Healer → MiMo precedent explains why they did it anonymously first: collect billions of tokens of real agent traffic (Claude Code, Hermes Agent), stress-test at zero cost, then ship open weights with proof of demand. Bloomberg reporting that Ox Alpha more than doubled DeepSeek's usage on OpenRouter is the payoff metric — not a mystery for its own sake.

Related on explainx.ai

• Omen Alpha: OpenCode's new stealth model at $0.20/M tokens — the sequel stealth launch, unconfirmed identity

• GLM-5.3-Flash official launch — specs, benchmarks, pricing — the named product after stealth week

• Top 10 things people are building with Ox Alpha — fluid sims, 3D scenes, a DeepSWE benchmark run, and more

• GLM-5.3 launch — cyber-defense benchmarks and ExploitBench gap

• OpenRouter Ox Alpha: free 1M-context stealth model — full specs, pricing, and setup

• Heretic: complete guide to automatic LLM censorship removal

• Choosing open-weight vs. closed AI models

• AI token pricing, explained

• Hermes Agent #1 on OpenRouter rankings

Primary sources: Chetaslua (@chetaslua) — serving-layer proof thread, Aug 22, 2026 · @aitrackerbot fingerprinting thread on X · dax (@thdxr) on X · GLM-5V-Turbo documentation, Z.AI · Ox Alpha on OpenRouter

Zhipu confirmed Ox Alpha as GLM-5.3-Flash on August 26, 2026. MIT weights at huggingface.co/zai-org/GLM-5.3-Flash. Updated August 26, 2026.