Use Ox Alpha on OpenRouter.

Verify the OpenRouter Ox Alpha listing first.

The public OpenRouter model page for stealth/ox-alpha is the current source to check before acting on an OpenRouter listing. Inspect its live availability, route details, price display, limits, provider information, and terms at the time you make a decision.

A public listing is useful for discovery, but it is not proof of a model’s underlying family, training data, snapshot, behavior, or equivalence with a differently documented provider route.

Start a TokenRa Ox Alpha API request.

If you choose to evaluate the TokenRa route documented on this site, register for TokenRa, create an API key, and verify the active route and provider terms in your account. The examples below use the documented TokenRa Chat Completions endpoint and the stealth/ox-alpha label.

TokenRa cURL example

curl https://tokenra.io/v1/chat/completions \
  -H "Authorization: Bearer $TOKENRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "stealth/ox-alpha",
    "messages": [
      {"role": "user", "content": "Explain this function in two bullets."}
    ]
  }'

TokenRa Python example

import os
import requests

response = requests.post(
    "https://tokenra.io/v1/chat/completions",
    headers={
        "Authorization": f"Bearer {os.environ['TOKENRA_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "model": "stealth/ox-alpha",
        "messages": [{"role": "user", "content": "Explain this function in two bullets."}],
    },
)
response.raise_for_status()
print(response.json()["choices"][0]["message"]["content"])

TokenRa JavaScript example

const response = await fetch("https://tokenra.io/v1/chat/completions", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.TOKENRA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: "stealth/ox-alpha",
    messages: [{ role: "user", content: "Explain this function in two bullets." }],
  }),
});

if (!response.ok) throw new Error(`TokenRa returned ${response.status}`);
const data = await response.json();
console.log(data.choices?.[0]?.message?.content);

These are route-specific examples, not a statement that every optional parameter, endpoint, tool, streaming mode, structured-output feature, modality, or response field is available. Verify current TokenRa documentation and test the route you plan to deploy.

OpenRouter vs TokenRa: compare route boundaries.

The OpenRouter Ox Alpha listing and the TokenRa route both use the stealth/ox-alpha label in the documentation discussed here. That shared label helps with discovery; it does not establish the same provider, model snapshot, parameters, context policy, filtering, data handling, performance, availability, or price.

When evaluating more than one route, test representative prompts, errors, latency, token budgets, output validation, data handling, and account limits separately. Do not assume changing a base URL or API key is sufficient.

Review data handling for each route.

Review the current provider terms, account settings, retention practices, and your own obligations before sending production data. A provider statement about one route does not automatically describe another route, even when the displayed model label matches.

Minimize input, remove unnecessary identifiers, keep credentials server-side, and avoid using a public route as the only safeguard for confidential information. Confirm the current provider’s terms before sending prompts, completions, attachments, or other sensitive content.

Validate the provider route you will actually ship.

1. Record the provider account, endpoint, model label, account terms, and review date.
2. Confirm current availability, supported input types, request fields, rate limits, price display, and data-handling information for that route.
3. Test representative short inputs, long inputs, malformed inputs, empty outputs, timeouts, provider errors, and rate-limit behavior.
4. Validate output before it reaches a user, database, tool, command, or external service.
5. Keep a route-specific test record and repeat it when the provider listing, account tier, application prompt, or integration changes.

Questions about Ox Alpha on OpenRouter and TokenRa.