User guide
Getting around
Everything lives at router.cocolevio.com behind the admin sign-in. The four pages you'll use daily:
- Dashboard — is spend on track? Any key burning money or blocked?
- AI Console — test prompts, watch routing decisions in real time.
- Auto-Switch — adjust which models serve each tier.
- Virtual Keys — mint keys for new apps and teammates.
A typical admin day
- Check the Dashboard — total spend for the period, spend per key, failed request counts. Click any key row to see its per-model breakdown.
- Adjust routing if needed — a new cheaper model came out? Open Auto-Switch, paste its id at the top of a tier's list, Save changes. Applied live.
- Mint keys on request — new app or teammate: Virtual Keys → Create New Key,
alias starting with
auto, set a budget. - Verify with the Console — send a simple / coding / reasoning prompt and confirm the routing log shows the models you expect.
Testing a change safely
The AI Console is the safest test bench: it uses the same gateway path as production apps. After changing a tier in Auto-Switch, send a matching prompt in the Console and read the routing log entry — tier, model, latency, cost — before telling anyone else.
Where settings live
| Setting | Location |
|---|---|
| Tier models & classifier | Auto-Switch tab (live) |
| API keys, budgets, expiries | Virtual Keys page |
| Key block/unblock/budget/delete | Dashboard (admin password required) |
| Provider credentials (OpenAI, OpenRouter, AWS…) | Server .env file — see Managing the stack |
| Registered models list | Models + Endpoints page |