Keys
One key per caller. People, agents, and tools each get a scoped gateway key. Provider secrets never leave the rack.
Platform · platform.routerlab.buzz
Usage, spend, requests, TTFT, and token counts at key and team scope. Aliases, waterfalls, and budgets are config — not a deploy.
One key per caller. People, agents, and tools each get a scoped gateway key. Provider secrets never leave the rack.
Call prod-chat in code. Route it to a hosted model today, your fine-tune tomorrow. Dev and prod are separate names.
Per person, per agent, per tool. A scope can pin a caller to local-only models so sensitive work never leaves your GPUs.
Caps by day, week, or month — key, project, or team. A capped key pauses and says so.
| Alias | Routes to |
|---|---|
| prod-chat | sonnet-class · hosted → backup |
| cheap-triage | gemini-flash · google |
| drafts | haiku-class · hosted |
| local-embed | qwen-27b · your gpus local |
The same spend, two cuts: which agent burned it and which person owns it. p50 TTFT sits next to cost, so a slow key is as visible as an expensive one. Everything the dashboard shows is queryable over the Usage API.