20 trillion tokens in 6 days: what the Ox Alpha stealth launch taught us about model IDs

On 20 August 2026 a model called Ox Alpha appeared on OpenRouter and OpenCode. No lab name. No paper. No benchmark card. No price. It had a 1M token context window, accepted text, images and video, and it was free.

Six days later OpenRouter said it had processed over 20 trillion tokens, which made it the biggest model ever to run on that platform. Z.ai founder Jie Tang put its share at nearly 20% of OpenRouter weekly token volume, the number one slot, at roughly 1/100 of frontier pricing.

Then the ID went away.

Our social listening corpus picked up 1,211 mentions of the alias across X and Reddit in the week of 22 to 28 August, against 409 in the week of 15 to 21 August. That is a 2.96x jump, and it makes the stealth launch the single largest model story of the month in our data. It is worth pulling apart, because the operational lesson has nothing to do with which lab won.

The timeline

20 August. The listing appears. Within hours people are testing it against the flagships. One early tester called it a one shot replacement for tasks normally given to Claude Fable 5, and noted the tokenizer looked Chinese in origin.

21 August. Andrew Curran opens a public thread for guesses and test results. Users note the free window is capped at less than six days. OpenCode says it has capacity for 100 trillion tokens per day.

22 August. The story crosses into mainstream feeds. Polymarket posts that a mysterious new model with a 1 million token context window and no disclosed owner has appeared, and the reach compounds from there.

23 August. Reports circulate that it outperforms Claude Fable 5 and GPT-5.6 Sol at coding, which pushes speculation toward every major lab in turn.

26 August. Z.ai confirms to Bloomberg that Ox Alpha is a new GLM iteration, and ships GLM-5.3-Flash: 320B total parameters with 18B active, natively multimodal, 1M token context, MIT license, and trained on Chinese AI chips. Pricing lands at $0.15 per million input tokens and $0.50 per million output.

26 August, same day. r/openrouter posts a thread titled "OX Alpha removed?" and r/opencode asks whether the free unlimited listing just got pulled.

The part that cost people real work

The most useful post in the whole cycle is not a benchmark. It is this one from r/openrouter:

It was insanely fast and genuinely great output and code. I burned 350M tokens in 2 days from 2 accounts and shit that was good work. I didn't even know it was physically possible for me to consume that many tokens. And now I'm realizing that the same amount of usage would probably cost me like $1,000 with normal API pricing. The worst part is i started planning so much work around it not knowing that it will end in 2 days.

Read that last sentence again. The failure was not the model. The model was excellent and it is still available under a different name. The failure was that a person built a workflow around a string that had no contract behind it, and the string changed.

This is the same class of incident as a provider deprecating a checkpoint, a lab renaming a snapshot, or a free tier hitting its quota. We wrote about the general shape of it in the model release treadmill, and the Ox Alpha week is the cleanest example we have seen of the specific version: an ID that was never meant to be permanent, adopted at production scale because it was good and free.

A second thread shows the adjacent trap. A developer tested Ox Alpha through a Claude Code harness and got billed roughly $2 for a "supporting model" because the harness quietly used Sonnet as its orchestrator while burning 28M tokens of the free model. The headline model was free. The workflow was not. If you cannot see per model spend inside a single agent run, you will not catch that.

Why labs are doing this now

Stealth listing is a rational strategy and it is going to keep happening.

A lab gets a week of real agentic traffic at scale, from real harnesses, on real codebases, with no brand halo and no benchmark gaming. Z.ai researcher Zixuan Li thanked the community directly for pushing the model to its limits and said the official release delivered stronger performance and better stability as a result. Twenty trillion tokens of adversarial evaluation is worth more than any internal eval suite, and it costs less than a launch campaign.

It also works as demand generation. Thinking Machines ran the honest version of the same play in the same week, making Inkling free on OpenRouter for agentic harnesses only and saying plainly that it would use the data to improve the model. Same mechanic, disclosed.

So expect more anonymous aliases, more time boxed free windows, and more capability arriving under names that will not exist in a month. The supply side was already exploding. Now some of the supply is deliberately temporary.

What to do about it

Four changes, none of them large.

1. Never reference a raw model string from application code. Reference a policy. A managed policy is an indirection layer: the app asks for a routing intent, the gateway resolves it to a live model. When an alias retires you change one policy, not every service.

2. Put a fallback chain behind every primary. Fallback policies let you declare an ordered list of substitutes. When the primary returns a 404 because the ID no longer exists, the request completes on the next candidate. The Ox Alpha retirement would have been invisible to users behind a chain ending in GLM-5.3 or DeepSeek V4 Flash.

3. Keep an explicit list of what is allowed in production. Approved models is how you stop an experimental alias from drifting into a customer facing path. Free stealth models belong in evaluation, and an allowlist is the difference between a deliberate decision and a surprise.

4. Instrument per model spend inside agent runs. The supporting model surprise above is a visibility problem. Cost tracking and usage analytics attribute spend per model, per key and per user, so an orchestrator quietly calling a premium model shows up the same day rather than at the end of the month. If you want the alerting side of this, see how to cap runaway agent spend.

The wider point

GLM-5.3-Flash is a serious model. It halves the parameter count of GLM-5.2 and beats it across the board, which is why Yuchen Jin called it a big deal, and Z.ai released the GLM-5.3 weights two days after the reveal. The capability is real and it is cheap and you should test it.

But the week proved something more durable than any benchmark. In a market where no model stays number one and where model IDs now appear and disappear inside a single sprint, the model name is the least stable part of your stack. Anything you build directly on top of it inherits that instability.

Route through a layer that can absorb the churn. Compare current prices across every live provider on our models catalog and the cheapest model rankings, or read how we stack up against OpenRouter and LiteLLM if you are choosing a routing layer now.

Start routing on Requesty and put a policy between your code and the next model that does not have a name yet.