How do I install the Openrouter Analytics skill?

Run npx skillmds@latest add modbender/openrouter-analytics in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openrouter Analytics safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openrouter Analytics?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openrouter Analytics free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openrouter Analytics?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openrouter Analytics by modbender — Agent Skill

Name: Openrouter Analytics
Rating: 4.2 (5 reviews)
Author: modbender

Openrouter Analytics

Review OpenRouter usage, analytics, and troubleshooting data via API. Use when the user asks for spend/usage monitoring, activity trends, per-key management reporting, or deep investigation of specific request IDs (latency, provider fallback, finish reason, token/cost breakdown).

modbender Updated Sep 9, 2026 12 repo stars

File contents

OpenRouter Analytics

Use this skill to pull management-level usage data and request-level troubleshooting details from OpenRouter.

Quick Start

Run from this skill folder:

cd ~/clawd/skills/openrouter-analytics

Management key operations (set OPENROUTER_MANAGEMENT_KEY):

python3 scripts/openrouter_analytics.py activity --limit 20
python3 scripts/openrouter_analytics.py activity --date 2026-02-18
python3 scripts/openrouter_analytics.py activity --from 2026-02-01 --to 2026-02-18 --summary --csv /tmp/activity.csv
python3 scripts/openrouter_analytics.py credits
python3 scripts/openrouter_analytics.py keys --limit 50 --summary
python3 scripts/openrouter_analytics.py report --from 2026-02-01 --to 2026-02-18 --format markdown

Request-level troubleshooting (set OPENROUTER_API_KEY):

python3 scripts/openrouter_analytics.py generation --id <generation_id>

Use --raw on any command to print full JSON.

Workflow

Check macro activity
- Run activity for daily spend/traffic patterns.
Check account-level usage
- Run credits to review consumed vs remaining credits.
Find key-level consumers
- Run keys to identify which keys are driving usage.
Investigate incidents
- Run generation --id ... for detailed logs on one request (latency, fallback providers, finish reason, token and cost details).

Notes

activity, credits, keys, and report require a Management API key.
generation uses a standard OpenRouter API key and requires the request id.
The script auto-loads ~/.openclaw/.env and current-directory .env before execution.
Use --retries and --timeout to tune robustness under transient API/network issues.
Keep generation IDs in your application logs to support reliable post-incident analysis.

Resources

Endpoint reference and field guide: references/endpoints.md
CLI helper script: scripts/openrouter_analytics.py

---name: openrouter-analyticsdescription: Review OpenRouter usage, analytics, and troubleshooting data via API. Use when the user asks for spend/usage monitoring, activity trends, per-key management reporting, or deep investigation of specific request IDs (latency, provider fallback, finish reason, token/cost breakdown).--- # OpenRouter Analytics Use this skill to pull **management-level usage data** and **request-level troubleshooting details** from OpenRouter. ## Quick Start Run from this skill folder: ```bash cd ~/clawd/skills/openrouter-analytics ``` Management key operations (set `OPENROUTER_MANAGEMENT_KEY`): ```bash python3 scripts/openrouter_analytics.py activity --limit 20 python3 scripts/openrouter_analytics.py activity --date 2026-02-18 python3 scripts/openrouter_analytics.py activity --from 2026-02-01 --to 2026-02-18 --summary --csv /tmp/activity.csv python3 scripts/openrouter_analytics.py credits python3 scripts/openrouter_analytics.py keys --limit 50 --summary python3 scripts/openrouter_analytics.py report --from 2026-02-01 --to 2026-02-18 --format markdown ``` Request-level troubleshooting (set `OPENROUTER_API_KEY`): ```bash python3 scripts/openrouter_analytics.py generation --id <generation_id> ``` Use `--raw` on any command to print full JSON. ## Workflow 1. **Check macro activity** - Run `activity` for daily spend/traffic patterns. 2. **Check account-level usage** - Run `credits` to review consumed vs remaining credits. 3. **Find key-level consumers** - Run `keys` to identify which keys are driving usage. 4. **Investigate incidents** - Run `generation --id ...` for detailed logs on one request (latency, fallback providers, finish reason, token and cost details). ## Notes - `activity`, `credits`, `keys`, and `report` require a **Management API key**. - `generation` uses a standard **OpenRouter API key** and requires the request `id`. - The script auto-loads `~/.openclaw/.env` and current-directory `.env` before execution. - Use `--retries` and `--timeout` to tune robustness under transient API/network issues. - Keep generation IDs in your application logs to support reliable post-incident analysis. ## Resources - Endpoint reference and field guide: `references/endpoints.md` - CLI helper script: `scripts/openrouter_analytics.py`

Frequently asked questions