The credit unit
connect0 bills in credits. Everything — every plan, pack, and per-unit rate — is expressed in credits and published before it runs, so you always compare apples to apples. Credits live in a single per-account wallet; work draws the wallet down and top-ups build it back up.
You never pay for connect0 by the seat or by the API call in dollars directly. You buy credits, and usage burns them.
How usage becomes credits
Every action you run — an agent turn, a model call, a minute of sandbox compute, a connector sync, a byte of egress, a GiB-month of storage — is a metered event. Each event type has a published per-unit rate. We meter the raw units as you go, then, on an hourly rollup, price those units and convert the total to credits (rounded up per line). Those credits are burned from your wallet.
Because billing is hourly and after-the-fact, your balance can briefly dip slightly negative before a burn settles; a small overdraft floor absorbs that, and hard stops kick in beyond it. Representative rates:
| Action | Credits |
|---|---|
| Model chat call — ~1K in / 500 out tokens (varies by model) | 3 |
| Image generation — one standard image | 40 |
| Sandbox compute — one minute of `sh` runtime | 2 |
| Storage — per GiB · per month | 5 |
| Web fetch — one `web_fetch` page | 1 |
| Connector sync — one materialise of a bound source | 2 |
| Ledger posting — one journal entry via API or MCP (reads 0.1) — available on every account, no subscription required | 0.3 |
| Ledger report — trial balance, explain, aged or statement matching run | 2 |
| Ledger period close — close, revaluation, consolidation or statutory export | 25 |
| Ledger storage — per GB of stored rows · per month (first 800 KB free) | 129 |
| Search — one API or MCP search across every block and file you can open (`search.query`); the dashboard command menu is free | 0.1 |
These are the rates you are billed at. Model-token and BYOK rates come from the live model catalog, and your dashboard always shows the exact usage for your account.
Three ways to get credits
You top up your wallet three ways, and they stack:
1. The Free plan and its starter grant
Every account is on a plan and starts on Free: no card, no monthly charge, pay per use. It comes with a free starter grant so you can build immediately; starter credits are time-boxed (they expire ~30 days after grant) to keep the free tier fresh.
2. Paid plans
A paid plan grants a batch of credits every month at a discount to buying them à la carte, and adds Storage Credits. Plan credits are granted each cycle and expire at the end of the cycle plus a grace period, so they’re “use-it-or-refresh.”
Starter
$20/mo · 2,300 credits/mo
$16/mo billed yearly
5 GiB Storage Credits
Pro
$200/mo · 26,000 credits/mo
$160/mo billed yearly
50 GiB Storage Credits
Ultra
$500/mo · 70,000 credits/mo
$400/mo billed yearly
100 GiB Storage Credits
3. Credit packs, or any amount
One-time top-ups on any plan — a fixed pack or any amount you choose. Bigger amounts carry a bonus, and — unlike plan credits — purchased credits never expire.
Basic
$10
1,000 credits
Standard
$20
2,100 credits · +5%
Plus
$100
11,000 credits · +10%
Max
$500
60,000 credits · +20%
Custom
$5–$5,000
any amount · same bonus tiers
When you burn credits, the soonest-to-expire ones are consumed first, so your non-expiring pack credits are preserved for as long as possible.
Two plans, one bill
The account plan is the team's shared budget; a member plan is one person's own. Every account has an account plan (Free by default): its credits are the pool that every member, every inbound message, every schedule and every den draws on. A member plan is an add-on on the same bill for one person — its credits pay only for what that person does directly, before the pool.
Starter
$20 per person / month · 2,200 credits/mo
$16/mo billed yearly
Pro
$100 per person / month · 12,000 credits/mo
$80/mo billed yearly
Max
$200 per person / month · 25,000 credits/mo
$160/mo billed yearly
Owners can cap how much of the pool a person's own actions draw in a month, per tier or per person; shared work — dens, inbound, schedules, agent-to-agent runs — always comes from the pool and is shown as its own line on the Billing page. When a member's own plan and their share of the pool are both used up, their next run stops and names which limit it hit.
Platform key vs bring-your-own-key (BYOK)
Model calls can bill two different ways depending on whose provider key runs them:
| Platform pool key | BYOK | |
|---|---|---|
| Who pays the provider | connect0 (bundled into your credit cost) | You, directly, on your own provider bill |
| What connect0 charges | The full model sell price, in credits | Only a small orchestration fee, in credits |
| Best for | Getting started, no key management | Volume/enterprise with your own provider pricing |
With a platform pool key, we manage the provider relationship and bill you in credits for the model tokens you use — nothing to set up. With BYOK, you attach your own provider key; you pay that provider directly for tokens, and connect0 charges only an orchestration fee (a small percentage of the notional model price plus a tiny per-call flat) for budgets, audit, and observability. BYOK shines when you already have negotiated provider pricing and want connect0 purely as the control plane.
Spend controls
No surprise bills. Set a hard spend cap and runs stop before they exceed it. Turn on balance alerts to get notified before you run low. Scope per-project budgets so one team or one agent can’t drain the account. And you can pre-purchase storage reservations at a term discount when you know you’ll hold data for a while.
Reading your usage
Your dashboard shows your live credit balance, month-to-date spend, and a breakdown of what burned credits — in both units (tokens, compute-minutes, GiB) and credits. That live view is always the source of truth; the rates on this page are illustrative.
Enterprise & committed credits
Need volume discounts, committed-use credit contracts, invoicing, or a custom BYOK orchestration rate? Reach out at hi@connect0.ai and we’ll set you up.