endpoint
One OpenAI-shaped endpoint
Point Claude Code, Codex, Cline, or any OpenAI client at /v1. Chat, Responses, images, audio, embeddings — translated per provider, streamed back in your format.
RelayStation routes your tools across 120+ AI providers through a single OpenAI-compatible /v1 — with fallback, OAuth refresh, and metering built in. Scoped keys and per-plan limits keep every tenant isolated.
$curl $HOST/v1/chat/completions
$-H "Authorization: Bearer rk-…"
Chapter 01 — Component lab
Everything between your prompt and the provider — handled once, in one place.
endpoint
Point Claude Code, Codex, Cline, or any OpenAI client at /v1. Chat, Responses, images, audio, embeddings — translated per provider, streamed back in your format.
fallback
Chain models into fallback combos. When one account rate-limits or errors, the next takes over mid-flight — no retries in your code.
auth
Claude, Codex, Gemini, Kiro, Cursor and more. Tokens refresh silently; 401s retry automatically.
metering
Per-key usage, cost estimates, and request logs out of the box.
isolation
Scoped API keys, per-plan limits, and per-workspace usage. One tenant never sees another.
regions
A single managed URL for every tool and teammate — no tunnels, no port-forwarding, no VPN.
Chapter 02 — How it works
01
Add OAuth logins or API keys in the operator dashboard. Test each connection with one click.
02
Set token, request, and RPM limits. Subscribers self-serve at /station — you never touch their machines.
03
Users mint an rk- key and call the OpenAI-compatible endpoint from any tool. You watch the meters.
Chapter 03 — Operator setup
Two minutes from signup to first token. Create an account, mint a key, call the endpoint from anything that speaks OpenAI.
$curl $HOST/v1/models -H "Authorization: Bearer rk-…"
$curl $HOST/v1/chat/completions -H "Authorization: Bearer rk-…" -d '{"model":"auto","messages":[{"role":"user","content":"hello"}]}'
Ready
Create a station account, mint an rk- key, and call the OpenAI-compatible API.