Jisuai AI Balance Query

Problem solved

When users ask how much Jisuai AI balance remains or how many calls are left, manually locating the config, building the API request, and parsing the JSON response is error-prone. This skill turns that workflow into a deterministic query path: it recognizes prompts such as “query Jisuai AI balance” or “how many Jisuai AI calls are left,” finds the existing Jisuai AI credential, and returns a clear result.

How it works

• Automatic config lookup: It reads models.providers in ~/.openclaw/openclaw.json, finds the entry whose baseUrl is https://v2.aicodee.com, and uses the matching apiKey. If the key was already configured, users do not need to provide it manually again.
• Balance API call: It runs scripts/check_balance.py and requests http://v2api.aicodee.com/chaxun/balance?key={api_key}. The response includes total for the account balance in USD and num for the remaining call count.
• Question-aware output: For balance-only questions it returns Your balance is: ${total}; for call-count questions it returns You have {num} calls left; for combined questions it returns both. If the response has success: false, it surfaces the message; if the call fails or no API Key is configured, it returns the corresponding warning.

Scope and limits

This skill only covers Jisuai AI balance and remaining-call-count queries. It does not handle top-up, configuration changes, or credentials for other platforms. Results depend on an existing apiKey in the OpenClaw configuration and on the API response, so missing credentials or API outages can only produce user-facing prompts to check the configuration or retry later.