DocsBilling and credits
Start here
Build and run
DocsBuild and run
Billing and credits
Seats are what a workspace pays for. Credits are what its calls spend. The two are separate on purpose, so adding a teammate and running a busy agent are different decisions.
Plans
Every plan includes the whole gateway. There is no feature held back for a higher tier: the marketplace, custom toolkits, access policies, projects, the sandbox and the audit log are on the Free plan too. What the plans differ on is how many credits a seat brings with it.
| Plan | Price | Credits |
|---|---|---|
| Free | $0 | 5,000 credits, topped back up every 30 days. Up to 2 seats. |
| Pro | $19 per seat per month | 50,000 credits per seat, granted on each paid invoice. |
| Enterprise | Custom | Managed hosting, SSO, extended audit retention, an SLA, and a credit volume to match. |
Seats are not managed on a screen of their own. The seat count is your workspace's active member count, and the subscription quantity is adjusted to match when somebody joins or leaves. The next paid invoice then grants the plan's credits for each billed seat.
How Free renews
A Free workspace is topped back up to 5,000 credits every 30 days, rather than being given that many more. The difference matters twice. A workspace that sat idle for a year does not accumulate a year of credits and stop needing a plan. And a workspace that bought a top-up is never reduced to the ceiling to make room for a free grant: purchased credits are yours, so a balance already above the ceiling is passed over rather than cut back to it.
Nothing has to be running for this to happen. The top-up is applied the next time the workspace does anything at all, whether that is a tool call or opening the billing page.
Credits are pooled
A workspace has one balance, not one per person. Teammates and their agents draw from the same pool, which is the honest shape for a shared gateway: the question a team asks is how much its agents cost in total, not which colleague spent what.
Every movement is a row in an append-only ledger, keyed by a stable reference so a retry of the same operation is charged once. The balance is derived from the ledger and never from the audit log, so nothing about retention or redaction can change what a workspace owes.
What a call costs
- A direct call
- An HTTP request to a REST API, or a call to a streamable MCP server. It is an in-process fetch, so it costs one credit.
- A sandbox-backed call
- A CLI operation or a stdio MCP server. These queue, boot a container and hold memory for the duration of the call, which is what the 5 is paying for.
- A toolkit build
- 10 credits per interface the build reads, charged together. A build is several model calls over a large document.
- A refusal
- A call denied by a grant, a tool name that resolves to nothing, and any request rejected before it reaches a provider. Searching, listing toolkits and reading a guide are free too.
Top-ups
Credits can be bought outright at any time, on any plan including Free. Purchased credits do not expire.
| Credits | Price |
|---|---|
| 25,000 | $15 |
| 100,000 | $50 |
| 500,000 | $200 |
Running without billing
Stripe is optional. A deployment with no Stripe keys configured starts every workspace on the Free plan with its renewing 5,000 credits and simply does not offer checkout, which is the usual shape for an internal or self-hosted install. See Self-hosting.
To enable checkout, create two recurring per-seat prices and three one-time prices in Stripe, set their ids in the environment, and point a webhook at /api/billing/webhook. Credit grants are idempotent by Stripe invoice or Checkout Session id, so a redelivered webhook cannot double-grant.