Crouton and Pulse Alpha offer mystery-model access with equally mysterious limits

What happened?

Two anonymous models moved from rumor into public catalogs this week, but not into authenticated product identities. OpenRouter’s Crouton Alpha page calls it a stealth model developed and operated by an anonymous third-party provider; OpenRouter says it routes requests and is not the developer, owner or provider. The page lists free access during the preview, multimodal input and a nominal 1.0 million-token context. OpenCode separately lists Crouton Alpha Free and Pulse Alpha Free as stealth models available without charge for a limited time.

The machine-readable OpenRouter record for Crouton gives a created timestamp of November 3, 2026, a 1,048,576-token context length, text/image/file/audio/video input and no public Hugging Face identifier. OpenCode’s Pulse page displays a 1M context, 131K output and text/image inputs, while its machine-readable record leaves the lab, release date, context, output, modalities and benchmarks unknown or null. Those conflicting levels of metadata are a reason to describe the numbers as platform catalog labels rather than verified usable context or output limits.

The access and privacy terms differ by platform. OpenRouter says the anonymous provider may retain prompts and completions even though it does not use them for training, and the model was not available through EU in-region routing when checked. OpenCode says Crouton data is retained for 30 days during its free period and not used for training, while Pulse data may be retained and used to improve the model; Pulse is unavailable in a list of countries and regions including the EU.

A November 5 OpenRouter follow-up also acknowledged a bug that could stop Crouton early before a tool call. That detail is small but editorially useful: a model can be interesting because of its context label and still be immature as an agent. Tool-call interruption changes the reliability of workflows that depend on a sequence of searches, file edits or approvals, and it is a reason not to equate a free preview with production readiness.

Source: OpenRouter ↗ · Source: OpenRouter ↗ · Source: OpenCode ↗ · Source: OpenCode ↗ · Source: OpenRouter ↗

Why does it matter?

The practical story is access without provenance. A free endpoint with a very large context label can be useful for experimentation, but users cannot evaluate the usual trust questions when the provider, weights, tokenizer and deployment history are undisclosed. A catalog entry proves that a platform routed requests under that name; it does not prove which model answered, how much context it can use reliably, or whether a community fingerprint matches a named lab. Teams should log the exact model ID, provider terms and request date when testing, so a later catalog change does not make an old result impossible to interpret. Community tests of image input, generative art and tokenizer behavior remain observations, not authentication.

The privacy terms matter more than the mystery branding. “Not used for training” does not mean “not retained,” and the provider’s policy may differ from the router’s. Teams should avoid sending confidential prompts until they have read the exact provider terms, then record which service handled the request, what regions are permitted and how long data may persist. Free access can also change abruptly: limited-time listings, anonymous backends and bug-fix posts are evidence of a preview, not a service-level commitment.

The same discipline applies to the Walrus or Meta theories attached to these models. A community post can establish that someone reported a similar internal checkpoint; it cannot establish Meta ownership, model equivalence, weights, training data or deployment relationship. The strongest current statement is narrower: Crouton Alpha and Pulse Alpha are real catalog listings with nominally large contexts and unknown providers, and their access and retention conditions deserve attention before their capabilities do today.

Source: OpenRouter ↗ · Source: OpenRouter ↗ · Source: OpenCode ↗ · Source: OpenCode ↗ · Source: OpenRouter ↗