An anonymous model with a million token context appeared on OpenRouter and costs nothing. Its maker has not said who they are.

Ox Alpha was created on OpenRouter on 20 August 2026, under the provider name “Stealth” and the identifier stealth/ox-alpha. The platform record gives a context length of 1,048,576 tokens, a maximum completion length of 131,072 tokens, prompt and completion pricing of zero, and no linked Hugging Face repository. Reasoning is mandatory and enabled by default. Over the two days since launch, trailing-day uptime has read 99.99 percent. Unsourced claims about who built it and how it scores are circulating; none are attributable to anyone in a position to know, so we are printing none of them.

Why it matters

A free, frontier-class, million-token endpoint appearing under a pseudonym is a real commercial event on its own terms — production teams are already routing traffic to it. An anonymous endpoint is also an unattributable one: no data-retention policy, jurisdiction, licence or safety record to check for a provider called “Stealth”.

What the platform record actually contains

We queried the OpenRouter models API directly on 22 August 2026, then its endpoints record for this model. This is the complete Tier 1 record.

The model identifier is stealth/ox-alpha; the display name is “Ox Alpha”. The `hugging_face_id` field is null — there is no linked weights repository. The creation timestamp is 1787256295, which is 20 August 2026 at 20:04 UTC.

There is exactly one endpoint, named “Stealth | stealth/ox-alpha”, provider name “Stealth”, tag “stealth”. Architecture fields: tokenizer “Other”, instruct type null, modality “text+image+video->text” — inputs are text, image and video, output is text only, with no audio. Quantisation is listed as “unknown”. Supported parameters include reasoning, include_reasoning, max_tokens, temperature, top_p, tools, tool_choice, top_k, response_format and reasoning_effort. Reasoning is flagged mandatory, default enabled, default effort high.

Pricing on the record is prompt “0”, completion “0”, discount 0. The `expiration_date` field reads 2098-12-31, which is a sentinel value in OpenRouter’s schema, not a stated commitment — the record does not say when, or whether, that will change.

Reliability, as reported by OpenRouter at query time: 99.99 percent uptime over the trailing day, 99.92 percent over thirty minutes, 99.99 percent over five minutes. That figure measures endpoint reachability over two days of a free preview — not correctness, and not behaviour under paid load. Latency and throughput fields were null. Implicit caching is not supported.

Unsourced claims about the model’s origin, its benchmark performance, and the length of its free window are circulating on social platforms and in aggregator posts. We could not trace any of them to the model’s operator, to OpenRouter, or to any other party in a position to know, so none of them appear in this piece, including as background.

What this means for buyers

Test it if you want to. Do not deploy it.

A zero-price endpoint from an unnamed provider is not something to put a customer workload behind. There is no service level, no named counterparty, no data processing agreement, and no notice period before the price becomes whatever the operator decides. Two days of uptime data on a free preview tells you nothing about behaviour under paid load.

If you are already routing to it, check what your prompts contain. An unattributable endpoint is the wrong place for anything covered by a confidentiality obligation. Our guide to what happens to your data assumes you know which vendor you are talking to; here you do not.

Watch for the reveal, not for benchmark claims circulating in the meantime. The identity of the operator will determine the licence, the price and the jurisdiction, and all three matter more than an unverified score.

What would change our reading

A statement from the operator claiming the model, or a Hugging Face repository with a licence file, would move attribution from absent to Tier 1 and let us report on terms, price and jurisdiction. An OpenRouter announcement naming the provider would do the same. Non-zero pricing appearing on the endpoint record would mark the end of the preview and establish commercial terms.

—

Sources