Wallet & Billing — Developer Docs

How API usage debits the organization credit wallet, and per-key caps.

How is API usage billed?

GET /v1/wallet returns the organization's credit balance so your integration can check affordability before metered work.

The credit model:

• Reserved then settled: project creation (POST /v1/projects) holds an estimate up front, then debits what bootstrap actually used and releases the remainder.
• Metered: agent turns (POST .../messages), summaries (POST .../summaries), and report generation (POST .../reports) debit credits based on the underlying work, exactly like in-app usage.
• Flat: knowledge-base search (POST .../search) costs 2 credits per call.
• Free: reads — project polling, site knowledge, message history, report status, artifact listing, wallet checks.

Caps:

• Keys can carry optional daily and monthly credit caps (never mandatory). When a cap or the wallet balance is exhausted, metered endpoints return 402 (api_key_credit_cap_exceeded or insufficient_credits).
• Owners top up or configure auto-refill from Account -> Billing.

Connector spend lands in the same workspace wallet as in-app work and is labelled API or MCP in usage views. For the customer-facing explanation of what spends credits and why amounts vary, see the Credits & Usage help articles.

Other API topics

• API Overview
• Authentication & API Keys
• Projects Lifecycle
• Plan Check, Sources & Uploads
• Ask the Agent
• Site Knowledge & Search
• Site Plan & CAD Handoff
• Reports & Artifacts
• Errors & Rate Limits
• MCP & Connectors
• OpenAPI Spec

• Full developer reference