| name | openrouter-usage |
| description | Query OpenRouter API costs, credits, and usage breakdown by model, provider, and date for the last 30 days. Triggers on API spending, check costs, openrouter usage, how much have I spent. |
OpenRouter Usage
Query OpenRouter API costs and generate usage reports via the command line.
When to Use
- Checking OpenRouter spend over the last 30 days
- Breaking down costs by model, provider, or date
- Exporting usage data as CSV or JSON for accounting
- Auditing which models and API keys consume the most credits
Prerequisites
Usage
python3 ~/.claude/skills/openrouter-usage/scripts/openrouter_usage.py
python3 ~/.claude/skills/openrouter-usage/scripts/openrouter_usage.py --date 2026-02-01
python3 ~/.claude/skills/openrouter-usage/scripts/openrouter_usage.py --csv
python3 ~/.claude/skills/openrouter-usage/scripts/openrouter_usage.py --json
python3 ~/.claude/skills/openrouter-usage/scripts/openrouter_usage.py --no-credits
Output
The default report includes:
- Credits balance: total purchased, used, remaining
- Spend by model: per-model cost with token counts (prompt, completion, reasoning)
- Spend by provider: aggregated by provider (OpenAI, Anthropic, Google, etc.)
- Spend by date: daily spend with visual bar chart
API Endpoints
Both endpoints are read-only GETs authenticated via Bearer token:
| Endpoint | Purpose |
|---|
GET /api/v1/credits | Total credits purchased and used |
GET /api/v1/activity | Last 30 days of usage grouped by model/endpoint/provider |
The activity endpoint returns per-row: date, model, provider_name, usage, byok_usage_inference, requests, prompt_tokens, completion_tokens, reasoning_tokens.