Contact CodeRouter
Every enquiry below reaches the same inbox: support@coderouter.io. Naming the category in your subject line gets it to the right place faster.
Support and technical issues
Routing behaviour, integration problems, unexpected model selection, API errors.
Before writing, it is worth checking the LLM API error reference — it is indexed by exact error string and covers the errors we see most often.
Billing and account
Invoices, plan changes, top-ups, cancellation, refund requests.
Payments are processed by Stripe and subscriptions renew automatically unless cancelled before the renewal date. Refunds are handled case by case — see the terms.
Security disclosure
If you believe you have found a vulnerability, email us before disclosing it publicly.
Please include reproduction steps and do not include live credentials in the report.
Press and partnerships
Media enquiries, integration partnerships, and questions about how routing decisions are made.
What to include in a routing report
Routing issues are much faster to diagnose with these four things. Without them the first reply is usually a request for them.
- The agent and version — Claude Code, Cursor, Aider, Cline, Continue.dev, Windsurf, OpenClaw or an SDK, and which version.
- The exact error string, verbatim, including the HTTP status. Paraphrased errors frequently point at the wrong layer.
- What you expected to be routed to, and what was actually selected — the dashboard shows the per-request model.
- Whether it is reproducible, and if so the shortest request that reproduces it. Never include your API key.
Other channels
- Product and routing changes are recorded on the changelog.
- Setup and per-agent configuration is in the integration guide.
- Data handling questions are answered in the privacy policy.