Usage & budgets

Billable connector and built-in calls are attributed to an organization and, when an API key was used, to that key. CoreSpeed records the charge through one ledger so different agents and capabilities do not create separate billing systems.

Authenticate → resolve visible tool → check holds → execute tool → charge → record activity → organization ledger.

01Access

1. Authenticateorganization + key
2. Resolve toolvisible to this caller

02Govern

1. Check holdswallet + spend cap
2. Execute toolonly after checks pass

03Attribute

1. Chargeorganization and key
2. Record activitylink the charge once

ONE AUTHORITATIVE WRITEOrganization ledgerorgapi keycharge id

Organization boundary

If the wallet crosses its billing threshold, later billable requests return 402 payment_required before the underlying tool executes. Topping up clears that balance state. 403 org_suspended is an administrative state and is not cleared by adding balance.

API-key boundary

A monthly spend cap can be attached to an API key. Once recorded usage reaches the cap, later metered calls using the key return 402 key_spend_limit_exceeded.

Spend caps are request-boundary guardrails, not reservation systems. An action already in flight can finish above the remaining amount before its final cost is recorded.

Memory pricing

All seven memory__* operations cost $0 per call. Memory remains inside the metered boundary so holds and suspensions still apply, while storage quotas and rate limits cover resource use.

One bill, separate audit trail

The billing ledger is the authority for money. Activity records reference a charge when one exists and the dashboard joins the two for display; an audit retry cannot duplicate a charge.

Inspect spend, key caps, balance, and payment history in the dashboard.