Plan Management
Create and manage your Token Plans
What Is a Token Plan?
A Token Plan is the core unit in Router9 — each account has exactly one, shared across all your AI harnesses (agents and coding CLIs). Your Token Plan gets:
- One or more API keys for authentication (up to 5, one per harness/environment)
- Its own usage limits (rate limits and a credit quota with rollover)
- Separate audit logs
- A subscription tier (Free, Pro, or Max)
Your Token Plan
Every account has exactly one Token Plan on the Free tier, provisioned automatically the first time you open the dashboard — there is no manual creation step. From there you can rename it, view its API key, and upgrade the subscription tier.
Plan Overview
The dashboard shows your Token Plan at a glance:
- Usage Bars — Color-coded progress for the 4-hour window and credit allowance
- Green: Under 80%
- Yellow: 80-95%
- Red: Over 95%
- Alerts — Real-time warnings when you approach or exceed limits
Plan Sections
Your Token Plan is managed across these sections (under Profile):
| Tab | Description |
|---|---|
| API Keys | View key hint, regenerate key, copy integration snippets |
| Skills | MCP setup instructions, Skill usage monitoring |
| Usage | 4-hour and weekly quota bars, request history charts |
| Audit | Request logs with filtering, detail view, CSV export |
API Key Management
A Token Plan can have multiple API keys (up to 5). Create, name, and revoke them from Profile → API Keys. A newly created key's full value is displayed only once — copy it immediately.
Integration Snippet
The API Keys tab provides a ready-to-copy .env block:
OPENAI_BASE_URL=https://api.router9.com/v1
OPENAI_API_KEY=sk-r9k-your-key-hereManaging Keys
- Go to Profile → API Keys
- Click Create Key, give it a name, and copy the full value (shown once)
- Delete any key to revoke it immediately — other keys keep working
Managing via API
The REST resource is /v1/token-plans (the legacy aliases /v1/agent-plans and
/v1/agents continue to work). Your account has a single Token Plan, provisioned
automatically. API keys are managed under /v1/api-keys.
List Token Plans
GET /v1/token-plansUpdate Token Plan
PATCH /v1/token-plans/:id{
"name": "Updated Name",
"description": "Updated description"
}Regenerate Key
POST /v1/token-plans/:id/key/regenerateReturns the new full key (displayed once).