API credits and usage
Inspect the same workspace balance used by the app.
The current API uses workspace credits. There is no separate API dollar wallet to fund.
API access requires an active subscription or at least one successful historical top-up. Paid operations also need sufficient spendable credits and can be limited by the key creator's member cap.
Read the balance
Requires credits:read:
| Response field | Meaning |
|---|---|
balance | Workspace credit pool |
purchased_balance | Purchased credits included in that pool |
spendable | Amount this member can spend |
member_cap | Member limit, or null where no cap applies |
member_spent | Member's tracked spending |
Do not add purchased_balance to balance; it is already included.
Read API usage
Requires usage:read:
Choose the start timestamp for your reporting period. Without since, the endpoint uses the preceding 30 days. The response groups API requests and credits by mode. provider_cost_usd, when returned, is not the customer's invoice amount; use credits and your billing records for customer charges.
Funding and charging
Purchase plans or packs in the workspace Billing page. Included credits are used before non-expiring purchased credits. API generation reserves credits before execution and settles or releases reservations according to the outcome.
Voice creation includes preview generation. Agent planning is charged separately from execution. Do not infer that a failed multi-step run consumed no credits.
See Plans and pricing for current catalog amounts.