AIGate Token Usage Query

The Problem

When using AIGate model APIs, engineers often need to check token balances, monthly usage, and daily consumption, especially during cost reviews, quota debugging, or shared API key operations. Manually querying a dashboard or calling endpoints is fragmented. The AIGate Token Usage Query skill wraps this into a conversational workflow: send a keyword containing Token in OpenClaw to trigger the query and receive the result.

How It Works And Boundaries

• Trigger: Any message containing Token is case-insensitive, such as token, TOKEN, or 查Token.
• Configuration: Set API_BASE to the AIGate query endpoint and API_KEY to the AIGate platform SK, typically formatted like sk-ag-xxx.
• Dependency: The skill relies on jq to parse JSON responses, so the tool must be available in the environment.
• Scope: The documentation covers balances, monthly usage statistics, and yesterday's consumption only; it does not describe key creation, top-ups, permission changes, or audit exports. If a query fails, check the endpoint, key format, network reachability, and jq availability.