Credits and pricing

connect0 bills usage against a credit wallet on your account. Every number on this page is generated from the credit catalogue in code (the same source /pricing reads); a gate refuses a drift between the two. Work that costs money — model calls, paid tool calls, sandbox compute, storage — is metered and burned from your credit balance. This page explains the model so nothing about your bill is a surprise.

What consumes credits

Every metered action emits a usage event attributed to your account. The largest driver is normally model usage (input and output tokens on the model an agent runs). Cached input is billed at the cached rate shown on the model row — the share served from the provider's prompt cache is on your usage page, per model. Next come paid tool calls such as web_fetch and any provider-backed skills. Sandbox compute, connector materialise calls, file transfer, media jobs, and stored data all meter too. Reading data you already have, listing connectors, and other control-plane operations are not metered. See Usage and metering for exactly how events turn into credit burn.

Every account is on a plan

Every account has a subscription plan, and a new account starts on Free. A plan is not a feature paywall — every plan runs the same platform — it is a monthly grant of credits at a better rate, plus Storage Credits.

Account plan	Monthly	Yearly (per month)	Credits per month
Free	$0	$0	the starter grant
Team	$20	$16	2,300
Business	$200	$160	26,000
Scale	$500	$400	70,000
//: # (/pricing-snapshot)

• Free — the plan a new verified account starts on. It carries the one-time starter grant (the current amount is on pricing), no card required, so you can run real agent work before you ever pay. Free has no monthly grant; you top up credits when you need more.
• Team, Business, Scale — a monthly grant of credits to the whole account at a discount to the pay-as-you-go rate, and on Business and Scale more agent runs in parallel. Everyone in the account, its inboxes, its schedules and its dens draw on these credits. Every paid plan can be billed monthly or yearly: the yearly price is 20% lower and is charged once a year, but the credits still arrive every month and each month's grant expires on the same schedule as a monthly plan's (month end plus a grace window). An annual plan is a price, not a twelve-month credit bucket.

Member plans — a budget of their own

The account plan is the team's shared budget; a member plan is one person's own. An owner or admin adds a member plan to the account's subscription from the Billing page —

Starter ($20, 2,200 credits), Pro ($100, 12,000 credits) or Max ($200, 25,000 credits) per person per month //: # (/pricing-snapshot)

— and that person's own actions spend it first, then the account's credits, within any monthly limit the owner sets. Shared work (dens, inbound messages, schedules, agent-to-agent runs) always comes from the account's credits.

Buying credits

On any plan you can add credits at any time; purchased credits never expire.

• Credit packs — Basic $10 (1,000 credits), Standard $20 (2,100 credits), Plus $100 (11,000 credits), Max $500 (60,000 credits). Larger packs include bonus credits.
• Custom amount — any amount from $5 to $5,000, with the same bonus tiers as the packs (5% from $20, 10% from $100, 20% from $500). //: # (/pricing-snapshot)

Buy credits or change your plan from Billing at /a/<slug>/billing — see Managing billing.

How the wallet works

Credits are granted to your account and burned as usage is rolled up each hour. Your current balance and per-grant expiry are visible in the wallet at /a/<slug>/billing/credits. Grants can be time-limited, so an unused plan grant eventually expires; pack credits last much longer. The balance shown always reflects what's currently spendable — a purchase made with a delayed payment method (ACH, SEPA) shows as pending with an estimated settlement date and cannot be spent until it settles.

Platform key vs BYOK

By default your model calls run on connect0's platform provider keys and burn credits at the catalog rate. If you bring your own key (BYOK), you pay the provider directly and connect0 charges only a small orchestration fee in credits instead of the full token cost.

Running out

When the wallet is empty, credit-burning actions fail closed rather than running up a debt. For example web_fetch returns an insufficient_credits result and an agent run that needs a paid model call stops instead of proceeding. Reads, dashboards, and data export keep working — running out of credits never holds your data hostage. Top up at /a/<slug>/billing/credits and the same action succeeds on the next attempt.

Keeping costs predictable

• Pick a cost-appropriate runtime model — see Choosing a model — or put the agent on the dial, which picks the cheapest model that is strong enough for each task and records what it saved.
• Watch spend at /a/<slug>/usage; it aggregates every metered action by product and model so you can see where credits go.
• Set a spend cap and balance alert so nothing runs away — see Spend controls.

Where to go next

• Managing billing — buy credits, manage a subscription, and read invoices.
• Usage and metering — how a metered action becomes a credit burn.