Billing and usage
How Arc0 prices active connected users, what fair use includes, and how to read your usage meters and change plans.
Arc0 bills per active connected user, not per call. An active user is anyone with at least one successful connection-backed action or authorized event poll in the billing period, counted in production only. A user with both counts once. Development-mode users and failed operations do not incur connectivity charges. Funded provider consumption is a separate meter described below. See Environments for what separates the two.
Plans
| Plan | Price | Included active users | Audit retention |
|---|---|---|---|
| Build | Free | 100 | 30 days |
| Launch | $99/mo | 1,000, then graduated | 90 days |
| Scale | From $1,500/mo, billed annually | Priced on your volume | 365 days |
There's also a free Personal plan for connecting your own apps to your own agents, with no separate developer project setup required — see Arc0 for individuals.
Graduated per-user rates
Launch includes 1,000 active users in the $99 base price. Past that, each band of users is billed at its own rate — it's graduated, not a cliff where every user jumps to the higher rate:
| Users | Rate |
|---|---|
| 1–1,000 | Included in the base price |
| 1,001–10,000 | $0.10 per user |
| 10,001–100,000 | $0.05 per user |
| 100,001+ | $0.03 per user |
Worked example: Acme Desk is on Launch and has 3,000 active users in September. The first 1,000 are covered by the $99 base price. The next 2,000 (users 1,001 through 3,000) fall in the $0.10 band: 2,000 × $0.10 = $200. The month's bill is $99 + $200 = $299.
When you move to Launch, this per-user rate is locked for 12 months, so a plan you agree to today doesn't change under you as your user count grows.
Fair use and call overage
Each active user brings 5,000 calls a month, and those calls are pooled across the whole organization rather than capped per user — a quiet user's unused calls cover a busy one's. Calls past the pool cost $0.25 per 1,000.
Worked example: 3,000 active users give Acme Desk a pool of 3,000 × 5,000 = 15,000,000 calls. If agents make 15,200,000 calls that month, the 200,000 over the pool cost 200 × $0.25 = $50.
Failed calls and Development-mode activity don't count toward connectivity active users or the call pool. A dispatched funded-provider call can still consume its reserved wallet charge.
Usage and payment management
Organization owners and administrators can open Settings → Billing to inspect the current plan and project usage. The dashboard's calendar-month usage summary uses UTC. Dodo Payments invoices use the subscription's billing period; those periods may start on a different day. Do not treat a calendar-month summary as a finalized invoice.
Launch checkout and the customer billing portal are handled by Dodo Payments. The portal manages payment details and subscription settings. Arc0 changes entitlements only after verifying a provider event; returning from checkout does not by itself grant paid access. Scale remains a quoted plan.
Build allows up to 100 active connected users in production across the organization. An existing active user can continue making calls at that limit; a new user's connection-backed call requires an upgrade. Sandbox is unlimited. Calls that fail do not consume a user's monthly allowance.
Usage dashboard
Open Usage in a project, organization, or personal workspace to inspect the last 7, 30, or 90 days. The screen shows tool calls, error rate, active end users, and funded wallet spend, with daily UTC call counts and the top apps and end users. Organization usage combines its projects; a project view follows the selected Live or Sandbox project. Personal usage follows your own identity.
These activity metrics are separate from billing-period connected-user counts. Funded spend counts settled USD wallet charges during the selected window, including charged failures; credits, held reservations, released funds, and charges on your own provider credentials are excluded. See the API reference for programmatic aggregates.
Premium access
Paid provider consumption is a separate meter from connectivity subscriptions. Public tools, business credentials and Arc0-provided access retain their own usage and cost records; they do not silently become connected users. A free connectivity plan does not fund third-party charges. Provider charges on your own credentials are billed by that provider.
The implemented prepaid wallet holds USD service credits. The default starting offer is $2 per verified Arc0 user, claimed once into their first-created organization. The amount is configurable; use the signed-in grant-status response for current eligibility and amount. Organization owners and administrators can inspect available, held and spent balances, paginate the ledger, set monthly project/end-user limits and start a Dodo top-up from Billing. Top-ups start at $10 in $10 increments, with no automatic top-up or funded subscription. Credits are non-refundable Arc0 service credits. A checkout return is advisory: only a matching verified payment webhook credits the wallet, once per payment ID.
An enabled funded offer shows its published price per call before execution. Arc0 reserves the maximum charge before dispatch, then settles or releases it. A definite refusal before dispatch releases the reservation; a dispatched failure or unknown outcome can consume the reserved amount. Wallet balance, UTC-month project/end-user limits and bounded provider quota all constrain admission. Development connectivity allowances do not waive these charges.
This wallet backend is implemented; deployment, Dodo payment acceptance and each provider's permission/quota activation are separate gates. Do not infer that a provider offer is active from wallet availability. See the API reference for the authenticated Core-origin wallet routes; these do not accept runtime execution keys.
Next
Environments
Why development users are free and how the query param works.
Members and roles
Who can change the plan and payment method.
Arc0 for individuals
The free plan for connecting your own apps and agents.
App-event polling
A successful authorized production poll counts its end user as active, deduplicated with tool-call activity across the organization. Failed polls and Sandbox activity do not count. Polling does not add to the successful tool-call total or consume the pooled fair-use call allowance. The dashboard shows successful polls separately from successful calls.