DocsBilling and usage
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 much usage a seat includes each month before the workspace balance is touched.
| Plan | Price | Included usage |
|---|---|---|
| Free | $0 | $3 of usage, topped back up every 30 days. Up to 2 seats. |
| Pro | $19 per seat per month | $10 per seat, added on each paid invoice. |
| Enterprise | Custom | Managed hosting, SSO, extended audit retention, an SLA, and an allowance to match your volume. |
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 adds the plan's included usage for each billed seat.
How Free renews
A Free workspace is topped back up to $3 of usage every 30 days, rather than being given that much more. The difference matters twice. A workspace that sat idle for a year does not accumulate a year of allowance 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: money you paid in is 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.
One balance, held in dollars
A workspace has one balance, not one per person, and it is money rather than a currency of ours. Put in $20 and you can spend $20. There is no credits-per-dollar rate to look up, because there are no credits: what you are quoted on this page is what comes off the balance.
Teammates and their agents spend from that one balance, 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, though the usage charts break it down by member, project and meter if you want to know.
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 usage costs
- A tool call
- Every call, on every plan, at any volume. A direct call is an in-process fetch and never touches a sandbox, so it costs nothing at all. A sandboxed call costs nothing for being a call: you pay for the sandbox time it holds, priced below.
- An hour of sandbox, 1 vCPU and 2 GB
- Charged per GB-second of memory actually held, at $0.04 per GB-hour, so a call that runs for two seconds is billed for two seconds. CLI operations and stdio MCP servers run here, and so does any action a connector marks as sandboxed. Queue time is never billed.
- Model tokens on the managed provider
- Twice what OpenRouter publishes for that model, input and output priced apart as they publish them. Computed from their live price rather than from a rate card of ours, so it follows their changes rather than going stale. Calls made with your own provider key are metered, attributed and charted, and charged nothing.
- Everything around a call
- Searching the catalog, listing toolkits, reading a usage guide, building a toolkit from a specification, and any request refused by a grant or resolving to no tool at all.
Top-ups
You can add money at any time, on any plan including Free, and it is added at face value: $20 adds $20 of usage. There is no volume bonus and no better rate further up the table, because there is no rate: a dollar you put in is a dollar you can spend. Purchased balance does not expire.
| You pay | Balance added |
|---|---|
| $20 | $20 |
| $50 | $50 |
| $100 | $100 |
Running without billing
Stripe is optional. A deployment with no Stripe keys configured starts every workspace on the Free plan with its renewing $3 of usage 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 a recurring per-seat price for Pro and three one-time prices for the top-ups in Stripe, set their ids in the environment, and point a webhook at /api/billing/webhook. Balance grants are idempotent by Stripe invoice or Checkout Session id, so a redelivered webhook cannot double-grant.