Pricing
One meter. No surprises.
You pay for a gated effect: the first time you ask about a given idempotency key. Everything after that — duplicate suppression, in-flight checks, retries, reports, lookups, policy changes, webhooks — is free.
That is deliberate. Charging per API call would bill you most on the day your agent misbehaves, which is precisely the day the product is doing its job.
Loading plans…
Overage is drawn from prepaid credit at the rate shown, so a runaway agent stops at your balance rather than generating an invoice. Credit is sold at parity: $10 paid is $10 of credit. Enterprise is the exception on both counts — it is invoiced, and it is arranged directly.
How you pay
Card
Subscribe monthly, or buy prepaid credit for overage. Card details are entered on the payment provider's own page and never reach Ratchet.
Crypto — no custody
Top up prepaid credit with USDC on Solana. Payments go straight to an address the operator controls; Ratchet holds no key and takes custody of nothing. Quotes are struck in USD, so a price move cannot mint credit.
What counts, and what doesn't
Metered
A begin call that creates a
new effect record.
That is the entire list. There is no second item.
What that means in practice
| Agent asks to refund a customer | 1 |
| Times out; retries 40 times | 0 |
| Reports the outcome | 0 |
| You read it back twice in the console | 0 |
| Billed | 1 effect |
A runaway loop is a support problem, not an invoice. The meter counts decisions about distinct actions — which is the thing you actually get value from.
Free
- Every repeat
beginfor the same key — duplicate, in-flight, blocked - Retries after a failure, however many the policy allows
- Reporting an outcome
- Lookups, listings, and effect reads
- Policy reads and writes
- Webhook deliveries and retries
- Resolving an indeterminate effect
Cost controls that bind before the bill does
- Prepaid, never postpaid. Overage draws down a balance you chose to load.
At zero, new effects are refused with a
402— existing ones still replay. - Daily external-spend ceilings per API key, per effect type, and per workspace. These bound your spend at third parties, not with us.
- Per-destination ceilings. “No more than $2,000 to any one counterparty a day,” and a count limit for effects that cost nothing at all. Ratchet counts the destination without ever seeing it — only a keyed hash of what you declare is stored. How that works.
- Per-effect cost ceilings. An effect declaring more than the configured maximum is refused before it runs.
- Rate limits per key, so one misbehaving agent cannot exhaust the throughput of another.
Enterprise, and what it deliberately leaves out
Enterprise exists because the risk controls above brought a different buyer, not a different feature. A payments or compliance function needs things a developer does not: retention long enough to name in a policy, headroom it will not trip over, and an invoice against a contract rather than a card.
It withholds no control. Every ceiling on this page — at-most-once initiation, per-destination and velocity limits, required dimensions, surge containment, the gate-only agent key that cannot rewrite its own policy — ships on every plan, including the free one. That is deliberate, and it is the one line we will not move: “the ceiling exists, you were on the wrong plan” is not a sentence a safety product gets to say. A test asserts Enterprise and Scale have identical capabilities, so it cannot quietly stop being true.
What it is instead is room and terms:
- 2,500,000 gated effects included, at $0.70 per 1,000 beyond — below the Scale rate, because a tier charging more per effect than the one beneath it would be a penalty for growing.
- 30,000 requests a minute, ten times Scale.
- 400 days of retention against Scale’s 90. That is the ceiling the database itself will accept; we do not publish a number the service cannot honour.
- 500 API keys and 100 webhook endpoints, for an organisation with more than one team pointing at this.
- Invoiced, not charged. There is no list price because the number depends on what you are protecting, so it is a conversation rather than a button.
Two things worth knowing before that conversation rather than during it: Ratchet has no third-party audit and is operated by one person. For a regulated buyer those are real blockers, and you should hear them here. The full security posture.
Billing status
Checking…
Ready?
The free plan is a real plan. Full API, full MCP surface, all policy modes, webhooks, and the complete audit trail.
Still working out which number applies to you?
The free plan is 1,000 gated effects a month, on a workspace whose email has been confirmed. A workspace an agent made for itself, with no email attached, is capped at 100 until someone claims it and clicks the link — same workspace, same key, nothing to migrate. The long version, in plain words.
More questions: every answer we have.