Home / Docs

The router: one endpoint, the SDK you already use.

Call the router with the SDK you already use: change the base URL and the key, keep your code.

Start here

Quickstart — Point the OpenAI or Anthropic SDK you already use at the router and make a first call.
Authentication — The relay key, its scopes, and what the router answers when the key is missing or short of a scope.
Models — List the models a key may use, with their prices, and read the public catalogue without a key.
Routing — How the router chooses a model, and how to read why it chose that one.
Bring your own key — Use your own provider keys through the router: your key stays yours, and the fee is a line you can see.
Your model and your node — Route to a model you host yourself, and the status of renting capacity to others.
Credits and usage — Read your balance, your spending limits and the usage behind a bill.
Errors — The error body, and what 401, 402, 403, 413 and 429 mean.
Limits — The request-size and request-rate limits and how they are applied.
How this differs — Three things the router keeps visible that an aggregator does not.
Changelog — The latest changes to the router, from the release changelog.
The SDK — A typed TypeScript client generated from the contract, and the version rule that keeps it honest.
Integrate against your own install — The base URL, the token, the MCP server and the router endpoint of an install you run yourself, and what the golden run proves of each.

Every endpoint of the router, generated from the OpenAPI contract (version 0.4.0), so the reference cannot disagree with the code. Open the API reference →