# Billing & credits (/docs/billing)

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.

Every metered call takes one path: authenticate, resolve the tools visible to
this caller, check holds, execute, charge, record activity. It ends in the
organization ledger.

## Credits \[#credits]

Every metered action is priced in **credits** — 1,000 credits = $1, a public
rate that does not change. Per-action prices are on the
[pricing page](https://corespeed.io/pricing); every charge lands itemized in
the organization ledger.

Credit enters the wallet three ways:

| Source         | Amount                                                                   | Expires                 |
| -------------- | ------------------------------------------------------------------------ | ----------------------- |
| Signup credits | 3,000 credits when your first organization is created — no card required | 90 days after the grant |
| Plan credits   | 10,000 credits each month on CoreSpeed Pro                               | reset monthly           |
| Top-ups        | $5–$1,000 per checkout, on CoreSpeed Pro                                 | never                   |

Signup credits are granted once per user, to the organization created at
signup — joining someone else's organization does not mint a new grant. Monthly
plan credits are spent before the top-up balance. The Free plan has no top-up:
signup credits cover metered actions, and adding more means subscribing to
CoreSpeed Pro.

Balance, credit detail, and payment history live in
[Dashboard → Billing](https://app.corespeed.io/billing).

## Organization boundary \[#organization-boundary]

When the wallet has no credit available — its balance minus credit held for
work still in progress — later metered tool calls are refused before the
underlying tool executes. When a charge spends the last available credit,
CoreSpeed emails the organization's billing contact. On `/mcp` the refusal is
a tool-level result — HTTP `200` with `isError: true` and the code
`payment_required`; discovery, account reads and key management keep working.
Memory calls are metered too, so they wait as well. Adding credit — plan credits or a
top-up — clears that state. New credit first repays any amount a call ran
over. `org_suspended` is an administrative state and is not cleared by adding
balance.

## API-key boundary \[#api-key-boundary]

A monthly spend cap can be attached to an API key. Once the month's recorded
usage reaches the cap, later metered calls using the key are refused the same
way, with the code `key_spend_limit_exceeded`, until the month rolls over or
the cap is raised.

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.

## One bill, separate audit trail \[#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](https://app.corespeed.io).