/v1/models and /v1/chat/completions endpoints, so existing SDKs work without changes. The management plane covers authentication, routing configuration, cost tracking, and key management under /v1/router/*.
Shared provider models and hard constraints (cost, latency, capability) are evaluated at request time. You configure entrypoints, providers, and routing rules in a YAML v0.3 config file that the router reloads dynamically.
Authentication
How to authenticate with the router: Bearer tokens for data plane, sessions or API keys for management.
Chat Completions
Send chat requests through the router with standard OpenAI parameters and streaming support.
List Models
Discover available entrypoints and provider models via the OpenAI-compatible models endpoint.
Auth Endpoints
Register, log in, manage users, and configure OAuth for the router dashboard.
Base URL
<router-host> with the host where your router instance is running.