Plan Management

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 (one per harness/environment; 5 on Free, 10 on Pro, unlimited on Max)
• Its own usage limits (rate limits and a credit quota that resets each billing period)
• 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 Studio's settings — there is no manual creation step. From there you can rename it, view its API key, and upgrade the subscription tier.

Plan Overview

Studio's Plan page 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 pages in Studio:

Per-key request history, filtering, and CSV export live on each key's own Activity tab (/studio/api/keys/:id) rather than a plan-wide log — see Audit Logs.

API Key Management

A Token Plan can have multiple API keys — 5 on Free, 10 on Pro, unlimited on Max. Create, name, and revoke them from Keys (/studio/api/keys). A newly created key's full value is displayed only once — copy it immediately.

Integration Snippet

The Keys tab provides a ready-to-copy .env block:

OPENAI_BASE_URL=https://api.router9.com/v1
OPENAI_API_KEY=sk-r9k-your-key-here

Managing Keys

1. Go to Keys (/studio/api/keys)
2. Click Create Key, give it a name, and copy the full value (shown once)
3. 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. Harnesses (API keys) are managed under /v1/harnesses (the legacy alias /v1/api-keys continues to work).

List Token Plans

GET /v1/token-plans

Update Token Plan

PATCH /v1/token-plans/:id

{
  "name": "Updated Name",
  "description": "Updated description"
}

Regenerate Key

POST /v1/token-plans/:id/key/regenerate

Returns the new full key (displayed once).