Four days after OpenCode quietly enabled the free model, its own usage dashboard showed developers had routed 26 trillion tokens through Ox Alpha, more volume than any prior model preview on the platform generated in that span. OpenCode, the open-source coding agent built by Dax Raad, disclosed the total on August 24: 327,000 unique users and 8,328,244 completed sessions in just four days. That places Ox Alpha second on OpenCode’s own leaderboard, trailing DeepSeek V4 Flash’s 33 trillion tokens but running ahead of Xiaomi’s MiMo-V2.5 at 12 trillion, according to OpenCode’s dashboard.
AI Insiders reported on August 22 that Ox Alpha had surfaced on OpenRouter as a free, anonymous model with a one-million-token context window. The four-day tally is a different signal: proof that a model nobody can identify pulled meaningful production traffic away from labeled competitors within days of going live.
The scale looks smaller once measured against OpenCode’s own claims. The company said it had secured capacity for up to 100 trillion tokens a day, yet actual throughput averaged roughly 6.5 trillion tokens daily, about 6.5% of that ceiling. Sessions averaged 3.2 million tokens each, with the typical user opening about 25 of them. OpenCode’s dashboard also flagged that 93% of input tokens came from cache, so the headline figure blends fresh prompts with context reused across long coding sessions rather than counting only new work.
OpenRouter told a similar story through its own count. The platform said Ox Alpha generated 11.6 trillion tokens in its first three full days. No other model debut on that service has ever pulled in that much traffic that fast, topping the previous record of 4.4 trillion over an equivalent opening window. OpenRouter projected the model would add close to 6 trillion more tokens on day four alone.
Two platforms, two ledgers, one pattern: a model with no declared owner captured 6.8% of all token volume OpenCode observed in four days. Price explains most of that. Ox Alpha runs free through an OpenAI-compatible endpoint, carries no stated per-token cost or usage cap in OpenCode’s own documentation, and drops into existing coding-agent workflows with minimal rework.
What the listing withholds matters more than what it advertises. OpenCode’s own model page reduces the provenance question to a single word, “Unknown,” and leaves four fields blank that its other model entries typically fill in: who built it, when it shipped, where its knowledge cutoff falls, and what caps apply to its output. OpenRouter’s listing adds only that some outside party built the thing and runs it, without naming itself during the preview, alongside a 1,048,576-token context window priced at zero for both input and output. Neither platform states who trained it, what data it saw, or when its knowledge stops.
The two routes also handle data differently, a distinction that matters for anyone pointing production code at either one. A prompt sent through OpenCode’s Go endpoint is deleted within a day and kept out of any training run, per OpenCode’s stated policy. Send that same prompt through OpenRouter instead, and both it and the resulting completion stay stored, even though OpenRouter says that stored data is also excluded from training. A developer choosing between the two endpoints is really choosing how long their code sits on someone else’s server, not just which is faster or cheaper.
The rollout has not been clean. A GitHub issue filed August 23 reported that requests carrying tool definitions failed on OpenCode’s Zen and Go endpoints even as plain chat requests kept working, a defect that hits directly at the file-reading, command-running core of a coding agent.
Teams that adopted Ox Alpha for free-tier experimentation should treat the missing maker, cutoff and output-limit data as an open production risk rather than a footnote, and confirm which endpoint’s retention terms apply before pointing any proprietary repository at it.
RuntimeWire (Ryan Merket) reported the usage figures on August 24, 2026, citing OpenCode’s dashboard and OpenRouter’s own launch data.
