Build on one clear endpoint.
SRouter puts one inspectable endpoint between your tools and model providers. These docs connect the product surface to the source files that make it work.
Installation
Run SRouter with the published Docker image or directly from source code.
02 / docsGetting started
Connect a provider, create a key, and send the first request.
03 / docsArchitecture
Understand how the API, dashboard, CLI, and packages fit together.
04 / docsAPI reference
Browse the complete mounted HTTP route surface and auth boundaries.
05 / docsCLI
Connect Claude Code and OpenCode from the terminal.
06 / docsIntegrate
Connect OpenAI, Anthropic, streaming clients, and coding tools.
One endpoint, clear boundaries.
Follow a request from the client-facing API to the provider edge without losing the boundary between transport, business decisions, and reusable runtime behavior.
OpenAI-compatible and Anthropic-compatible clients use the local `/v1` surface.
Routes validate, authenticate, and adapt incoming requests into domain calls.
Combos, fallback, quota, pricing, and logs keep provider decisions visible.
Executors handle upstream auth, protocol differences, retries, and streaming.
From client to provider edge.
Each boundary has a home in the repository. Use the docs to move from behavior to implementation without guessing.