3 min read

Credits & pricing

All usage is metered in credits: 1 credit = $0.0001 (10,000 credits per US dollar). The live price book is public at GET /api/bots/pricing.

Per-call pricing

Every MCP/A2A request incurs a base protocol:call charge (1 credit). Expensive operations are priced per tool on top of that base:

OperationCreditsUSD
protocol:call (base, reads, lists)1$0.0001
Writes / updates (docs, storage, calendar…)5$0.0005
search:read (web search)50$0.005
mail:send100$0.01

The charge is resolved from the tool you call — an MCP tools/call of mail_send draws 100 credits; mail_list_messages draws 1.

AI usage

AI-backed work (triage, drafting, assistants) is charged at the model's real token cost × a markup multiplier, converted to credits and drawn from the same balance.

Charge-at-gate semantics

The charge is taken when the request is admitted. A call that subsequently fails validation or scope checks is still charged — keep your arguments and scopes correct.

Insufficient balance answers HTTP 402 with the amount required; hitting your key's spend cap answers 403 with code: "spend_cap_reached".