Help Center
Setup, per-agent integration, troubleshooting by exact error string, and billing. If an error message brought you here, go straight to the error reference and search the verbatim string.
Getting started
Point one base URL at CodeRouter and set the model to auto. These two pages cover the whole first run.
- Set up CodeRouterCreate a key, point your agent at the endpoint, send a first request.
- Integration guidePer-agent configuration for Claude Code, Cursor, Aider, Cline, Continue.dev, Windsurf, OpenClaw, GitHub Copilot and the OpenAI / Anthropic SDKs.
- How routing decidesPhase detection, capability filtering, cost ordering and provider failover — the four steps behind every request.
Troubleshooting
Errors are indexed by their exact string, because that is how you search when something breaks mid-session. Paste the verbatim message, including HTTP status.
- LLM API error referenceThe full index: exact error string, what it actually means, and the fix. Start here.
- reasoning_content must be passed back (400)DeepSeek thinking-mode traces dropped when replaying tool-call history.
- You exceeded your current quota (429)A billing problem in a 429 costume — and how to tell it from a real rate limit.
- prompt is too long: N tokens > M maximumWhat counts toward an Anthropic context window beyond the visible chat.
- Claude Code 401 after setting a custom base URLTwo environment variables fighting over which key wins.
- ECONNREFUSED on a local model endpointFive causes for Ollama and LM Studio connection refusals, checked in order.
- Query errors from inside your editorThe MCP server exposes the verified error database to any agent that speaks Model Context Protocol.
Models and routing
Which models are in the pools, what they cost, and why a given request went where it did.
- Model lineup and per-phase scoresEvery model in rotation with its capability score for planning, implementation, debugging, testing and documentation.
- ChangelogModels added and retired, routing rule changes, provider failover behaviour — dated.
- Which models need special handlingThinking modes, vision, long context and the fields a router has to preserve per provider.
- Your own routing dataPer-request model selection, detected phase and spend for your account.
Billing and account
Plans, payment, cancellation and what happens to your data.
- Plans and pricingCurrent plans, what each includes, and how top-ups work.
- Terms of servicePayment, renewal, refunds and account termination.
- Privacy policyWhat we collect, what is forwarded to upstream providers, and how keys are stored.
- Contact supportWhere to send a billing question or a routing report, and what to include.
Not covered here? Email support@coderouter.io — the contact page lists what to include so the first reply is an answer rather than a request for details.