openrouter-usage

What This Skill Does

The openrouter-usage skill provides an integrated interface for monitoring your AI expenditure within the OpenClaw environment. It allows users to gain granular insights into their OpenRouter consumption without leaving the terminal or the agent's chat interface. By leveraging session log analysis, it provides accurate credit balance lookups, per-model cost breakdowns, and future spending projections based on existing usage patterns. The skill is designed to bridge the gap between abstract API usage and tangible budget management, ensuring that users can maintain visibility over their AI-driven project costs with simple command-line triggers.

Installation

To integrate this functionality into your environment, run the following command within your terminal:

clawhub install openclaw/skills/skills/lcajigasm/openrouter-usage-info

Ensure that your environment has either the OPENROUTER_API_KEY set in your system variables or that your agent has been properly authenticated via the OpenClaw store, as the skill relies on these credentials to pull real-time credit data.

Use Cases

This skill is indispensable for developers and power users managing multiple agent workflows. Use it to audit the cost-efficiency of different models by comparing spend-per-model metrics. It is also highly effective for budget tracking in team environments where multiple agents may be running concurrently. By generating projections based on historical data, you can prevent unexpected overages before they affect your billing cycle.

Example Prompts

1. "How much credit do I have left in my OpenRouter account right now?"
2. "Can you give me a breakdown of how much I spent on GPT-4 versus Claude 3.5 Sonnet over the last 30 days?"
3. "Show me a report of my total usage for the current week and let me know if I am on track to exceed my monthly budget."

Tips & Limitations

The skill performs all session parsing locally, ensuring that your raw usage history is not uploaded to external servers. Because it reads logs from ~/.openclaw/agents/*/sessions/*.jsonl, ensure that your OpenClaw installation has proper permissions to access these directories. Note that while local parsing is efficient and secure, it depends on the integrity of your local logs; if you clear your session logs, historical data for the sessions section will not be recoverable. Use the --utc flag if you find that your timestamps are misaligned due to machine localization settings, as local time shifts can sometimes cause discrepancies in date-specific queries.