Credit management

Credits belong to the active personal or workspace context. In a workspace, the monthly allowance and purchased credits form a balance shared by all members.

What the credit page shows

The workspace credit page shows:

• Total remaining credits.
• A balance breakdown for the monthly workspace allowance, purchased credits, rewards or bonuses, and any shortfall.
• Grant and expiration dates when they apply.
• Daily usage attributed to the signed-in user.

Daily workspace history shows the signed-in user's own usage. In a personal account, daily history includes your API keys.

Monthly usage by user or API key

Your personal account shows monthly usage for you and your API keys. Workspace owners and admins can view monthly usage across the workspace, grouped by user or API key; ordinary members cannot view this breakdown. Switch months to review earlier usage.

The list displays current member names and API key names. Revoked or expired keys remain named until deleted. Former members, deleted keys, and other unrecognized actors are combined into a single Unknown row; their usage remains included in the total.

Purchase permissions

All workspace members can view the shared balance and their own usage. Only the workspace owner can purchase additional workspace credits; admins and members cannot start checkout.

One credit costs $0.01, and the minimum purchase is 500 credits ($5). Purchased credits are added directly to the workspace balance. Starting checkout and checking the balance do not consume credits.

Monthly allowance and additional credits

The monthly allowance is available only while the workspace has an active paid subscription. Additional purchases are separate credit grants. The balance breakdown shows their recorded and expiration dates, if any.

Usage is charged to the active workspace pool while preserving the user who performed the operation for attribution. Public playbook list/get reads are free on Web, CLI, API, and MCP. Ordinary Web page reads also stay free. Search and state-changing operations use the normal price; private API/CLI/MCP reads use the 1-credit band. If the shared balance is insufficient, a credit-gated operation can fail with 402 Payment Required.

For operation costs and consumption rules, see Credits. Subscription payments and credit purchases also appear in Subscription and billing.