One compliant endpoint for every model
The control plane between your product and the model providers: central key custody, written data terms, and failover that fires mid-request, behind one OpenAI-compatible API.
Evaluation credits on request; no card, nothing to install. Billing is usage-based in USD, quoted per workload.
At a glance
- Interface
- OpenAI-compatible API
- Endpoint
api.router.runixcloud.io/v1- Keys
- Per key: quota, limits, allowed models, routing
- Models
- Public list prices, on the catalogue
- Failover
- Mid-request, streaming preserved
- Data terms
- Content never used for training
- Billing
- Usage-based, USD, itemised
- Contracting
- Runix AI Inc · MSA & DPA on request
- Status
- Early access, running traffic
$ curl https://api.router.runixcloud.io/v1/chat/completions \
-H "Authorization: Bearer $RUNIX_API_KEY" \
-d '{"model": "auto",
"messages": [{"role": "user", "content": "Hello"}]}'
02 · Example
one request, any model
An OpenAI-compatible request. "auto" lets Router choose by cost, health and your key's policy; an explicit model id pins the model, and failover stays within the providers that serve it.
03 · Capabilities
Built for the three things that block rollouts
Teams rarely stall on whether a model works. They stall on who holds the keys, what legal can sign, and what happens at 3am when a provider degrades.
Keys stop leaking out of .env files
Provider credentials live in the gateway, not in a dozen repositories and CI secrets.
- Central key custody — provider keys are held once, never distributed to app teams
- Scoped access — per-key limits and quotas, revocable without a redeploy
- Request-level trail — who called what, when, with which model and at what cost
- No training on your content — prompts and outputs are processed to serve the request, nothing more
Something procurement can sign
A registered US company to contract with, and terms written down before you ask.
- US entity — Runix AI Inc, Wyoming, invoiced in USD
- MSA & DPA on request — reviewed per engagement; an order form overrides the standard Terms
- Data handling in writing — content versus metadata, and how long each is kept
- No invented badges — we state the posture we actually hold, and name what we do not
A bad provider hour is not your outage
The gateway is on the hot path, so it is built to get out of the way and to recover without you.
- Failover mid-request — errors, rate limits and timeouts re-issue upstream under a retry budget
- Circuit breakers — a degrading provider is taken out of rotation before it drags latency
- Streaming preserved — token streaming and tool calls pass through intact, not buffered and replayed
- Routing you control — pin a model, or let the router choose on cost, health and configuration
A base URL, not a migration
If your code already calls an OpenAI-compatible API, the change is configuration. The SDKs, the streaming, the tool-call shape and the error semantics you already handle stay where they are.
- Point the client at Runix and swap the key
- Pin a model id, or send
"model": "auto"and let routing decide - Per-key limits and usage tracking apply from the first call
04 · How it works
What a provider's bad hour looks like from your side
Your application holds one base URL and one key. Everything below happens behind that line, while the request is still in flight.
- Your application sends every request to one Runix base URL, with one key.
- Runix Router tracks provider health, and trips a circuit breaker on errors, rate limits and timeouts.
- The degrading provider is taken out of rotation before it drags your latency.
- The request is re-issued to a healthy provider under a retry budget, so a retry storm cannot become the second incident.
- The provider returns to rotation when health checks pass. Nothing in your application changed.
05 · Specifications
The details a review asks for
One table, the same shape on every product page, kept current with the pages it points to.
| Item | Value | Where it is documented |
|---|---|---|
| API surface | Chat completions and model listing, with server-sent events for streaming | Router quickstart |
| Model selection | "auto", or an explicit model id | Router quickstart |
| Models and prices | Every model on the catalogue at its vendor's public list price; contract rates in writing | Models catalogue |
| Failover | Provider to provider, mid-request, streaming preserved | Reliability |
| Limits | Per key: rate limits, quotas and allowed models, revocable without a redeploy | Access |
| Errors | OpenAI-style error envelope, with a request id on every response | Router quickstart |
| Data handling | Content processed to serve the request; operational metadata kept for billing and support | Privacy Policy and Security |
| Transport | TLS 1.3 and 1.2; 1.0 and 1.1 refused | Security |
| Service level | No published SLA during early access; the failover mechanism is documented | Reliability |
| Billing | Usage-based in USD, per token or per request by model; prepaid balance or invoice | Pricing |
06 · Works with
The layers on either side
Runix Router hands off to its neighbours in the stack and works on its own. The same block sits on every product page, with the neighbours changed.
Above · 05 Agents
Runix Code and Runix Comic
Independent domain agents. One that wants a single endpoint for every model can put Router in front of its calls.
See the agents →Below · 03 Models
Runix Models
A model tuned on your data sits behind Router next to the hosted providers, on dedicated capacity.
Explore Runix Models →The whole stack
Five layers, seven products
How Router fits with data, storage and the agents on top.
See the stack →07 · How to start
How to start
Three steps, each with a person on the other end: Runix Router is not self-serve.
01Tell us what you are building
Models, expected volume, latency needs. We reply within one business day and set the account up.
02Evaluate before you pay
Evaluation credits on request, full router functionality, no card. Integration is a base-URL change.
03Go to production in writing
Rates stated before you commit; MSA and DPA on request; prepaid balance or invoice, in USD.
08 · Questions
Common questions
How much of my code has to change?
Runix Router speaks the OpenAI API. In most cases you change the base URL and the key; the SDK you already use keeps working, including streaming and tool calls.
What happens when a provider fails?
Errors, rate limits and timeouts trip a circuit breaker and the request is re-issued to a healthy provider under a retry budget, so one provider's bad hour does not become your outage.
Is my prompt content used for training?
No. Content is processed to serve your request, not used to train models and not sold. Operational metadata (usage counts, latency, error codes) is kept to run billing, reliability and support. See Privacy.
Can we sign a contract and get invoiced?
Yes. Runix AI Inc is incorporated in Wyoming. MSA and DPA on request; an order form takes precedence over the standard Terms. USD billing with itemised statements, prepaid or invoiced.
How do I get access?
Access is invite-only: tell us what you are building and your account is set up within one business day; evaluation credits are issued on request, so you can test against real traffic before you pay. The full process is on Access.
Put the gateway in front of your traffic
Tell us the models you call and roughly how much: we come back with an access plan and a quote within one business day.
Request access