Configuration
Configure how BitRouter selects models, applies policy, falls back, and records what happened.
Configuration defines how BitRouter handles a request. It connects the model surface your application calls to selection policy, fallback behavior, output constraints, and the evidence BitRouter records about the run.
Start with bitrouter.yaml, then add only the routing behavior your workflow needs.
Config file
Configure providers, policies, routing behavior, and runtime features.
Routing
Control provider selection, fallbacks, virtual models, and variants.
Guardrails
Block or redact matching request and response content.
Observability
Trace and evaluate routing decisions across a workflow.
Configure, run, inspect
Configuration documentation follows the same three-step path:
- Configure the intended behavior in
bitrouter.yaml. - Run requests through the local daemon or BitRouter Cloud.
- Inspect the effective route, outcome, usage, and traces rather than inferring behavior from saved configuration alone.
Use the CLI for exact commands, Code for an interactive ACP conversation, and Observability when you want execution evidence from the running router.
How is this guide?