PrecisionDocs

Wallet & Billing — Developer Docs

How API usage debits the organization credit wallet, and per-key and per-connection 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).
  • A chat-agent (MCP) connection can carry the optional daily and monthly credit caps the person chose on the consent page; past one, metered endpoints return 402 connection_credit_cap_exceeded, and the way past it is reconnecting with a higher cap.
  • A key's or connection's caps are read before every operation that spends credits, and count what that key or connection charged to the wallet.
  • 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 & Billing help articles.

Other API topics