OpenRouter Activity and API keys
OpenRouter Activity is billing truth for gateway traffic: model slug, cost in credits, API key, and cache fields per generation.
Hub: Tokenminning with OpenRouter.
Open the dashboard
- Go to openrouter.ai/activity
- Filter by API key, model, or date range
- Click a row’s detail view for token breakdown including cache metrics
Export CSV or PDF for weekly reviews — group by Model or API Key to find dominant spend.
Per-key isolation
| Key | Purpose | Cap |
|---|---|---|
| Dev | Cline / Aider / OpenCode interactive | Moderate limit |
| CI | Bots, eval scripts | Low cap, haiku-only allowlist |
| Prod | App traffic | Separate from coding agents |
Rotate keys when a tool leaks into the wrong environment. Queries like openrouter_token ext:ini usually mean hunting leaked keys in repos — use env vars and secret scanners, not committed config.
Reconcile with client telemetry
| Source | Role |
|---|---|
| OpenRouter Activity | Billing truth |
opencode stats, Cline hints, Aider /tokens | Local trends |
GET /api/v1/generation?id=... | One expensive call |
After a heavy week: which key and model slug moved most? Split keys if one agent consumed the pool.
Organization accounts
Shared credit pool — Activity shows all members’ metadata (model, cost, timing) but not prompt text. Per-developer keys improve attribution.
Spending guardrails
- Set spending limit on each key at creation
- Org-level alerts before credits deplete
- Block CI keys from frontier slugs in client allowlists
- Weekly CSV export for cost attribution
Related
- OpenRouter hub
- Prompt caching — inspect cache in Activity detail
- Model routing
- Usage accounting
Last updated on