Balance and usage: one look before a batch run

Parameter

What it returns

quota_usd is the remaining credit (USD), used_usd is cumulative spend, group and group_zh give the account's group (mainland and overseas platform groups are enabled separately), and is_admin flags an admin account.

Typical use: price the batch before it runs

The usual pattern for a batch job is to call check_balance for the remaining balance, then price the whole batch at the per-call average and split it into runs if the budget is short. Far less trouble than finding out halfway through that you are out of money.

Quotas and keys

Every key under one account shares the account balance — each key does not get its own allowance. If you do want a cap on one key, set a positive quota for it in the console; that cap then takes precedence.

Copy and run

curl -s https://lucydomi.com/mcp/v1/check_balance \
  -H "Authorization: Bearer $BUSYBEE_API_KEY" \
  -H "Content-Type: application/json" \
  -X POST \
  -d '{}'

import os, json, urllib.request

KEY = os.environ["BUSYBEE_API_KEY"]
req = urllib.request.Request(
    "https://lucydomi.com/mcp/v1/check_balance",
    data=json.dumps({}).encode(),
    headers={"Authorization": f"Bearer {KEY}", "Content-Type": "application/json"},
    method="POST",
)
data = json.load(urllib.request.urlopen(req, timeout=60))
for it in data["items"]:
    print(it.get("url"), it.get("text", "")[:60])

Real response sample

A real production response below — truncated to one item, billing fields removed.

{ "ok": true, "username": "your_account", "quota_usd": 0.2, "used_usd": 0.0231, "quota_exact_usd": 0.2, "group": "default", "group_zh": "default group", "is_admin": false, "note": "Values are illustrative; a live call returns your account's actual remaining credit" }

FAQ

Related