Early access. Sandbox pricing.
Everything is free in the sandbox and no real money moves. Authorization pricing is not activated. The execution fee rules further down are published and receipted in sandbox so you can see exactly how execution would be charged - they apply only when Quattrino executes.
Sandbox
Free
real engine, simulated money
Authorization pricing
Not activated
metered, unpriced
Execution fees
Separate
only when Quattrino executes
Developer sandbox
Free while we validate with the first developer teams.
Open signup, no invite, no card. Every decision comes from the real authority engine; every payment adapter runs against test providers.
- Unlimited dry-run authorizations, intent compiles, authority discovery and explains
- Sandbox binding authorizations, outcomes and compliance checks
- Approvals, conserved delegation and purpose-bound disclosure decisions
- All execution adapters in test mode (Stripe test mode, sandbox Credits, x402 testnet)
- Python / TypeScript SDKs, MCP server, playground and runnable journeys
Future pricing architecture · not activated
What we expect to charge for - and what we never will.
This is the shape of the model, published so you can plan. No prices are published until approved, and nothing is billed in the developer preview.
| Tier / unit | What it covers | Status |
|---|---|---|
| Billable unit | A binding authorization decision - an AUTHORIZED decision that could be consumed. Already metered today as neutral Authorization Units with priced = false. | PROPOSED |
| Never charged | Dry runs · DENIED · NEEDS_INFORMATION · APPROVAL_REQUIRED · authority/me · authority/gap · explain · outcome reports · agents narrowing their own envelopes. Proof and refusals must never cost more than acting. | PROPOSED |
| Bundled | A monthly allotment of binding decisions, approvals, evidence retention, MCP and SDK access. | PROPOSED |
| Usage | Metered binding decisions beyond the bundle. | PROPOSED |
| Premium | Long evidence retention, compliance exports, SSO and roles, dedicated sandbox organizations. | FUTURE |
| Enterprise | Custom terms. | FUTURE |
Execution fees · separate from authorization
Only when Quattrino executes through one of its adapters.
Authorize-only usage never carries an execution fee. When a sandbox adapter executes, the published rule below is applied and named on the receipt. Numbers come from the live rule engine, not from copy; money in the sandbox is simulated.
Your own provider
No execution fee
You execute; Quattrino authorizes, checks the outcome and keeps the evidence.
Merchant checkout (Stripe SPT)
The merchant receives the full amount on its own Stripe account.
Marketplace purchase (Credits)
5% + $0.01 (min $0.01, max $50.00)
Buyer fee, separate line; the seller receives the full price.
Marketplace sale
5%
Seller fee on settled sales only; failed or refunded jobs cost nothing.
Credits top-ups carry no fee (funding, not a purchase). x402 machine payments run on testnet only. The legacy direct-card rail is retired and not offered. MPP pricing is proposed, not published.
Worked examples - computed by the real fee engine, sandbox money
Your agent uses a paid service
It pays $5.00 for a data service on the Quattrino marketplace (funded by Credits).
- Counterparty receives
- $5.00
- Execution fee
- $0.26
- Total (sandbox)
- $5.26
Rule marketplace_default_v1 v1 - the same id appears on the receipt.
Your agent checks out at a merchant
A $20.00 purchase at a merchant that accepts Stripe Shared Payment Tokens - the merchant receives the full $20.00.
- Counterparty receives
- $20.00
- Execution fee
- $0.00
- Total (sandbox)
- $20.00
Rule fee_none v0 - the same id appears on the receipt.
A small agent task
A $1.00 marketplace task paid from Credits - no separate card charge per micro-purchase.
- Counterparty receives
- $1.00
- Execution fee
- $0.06
- Total (sandbox)
- $1.06
Rule marketplace_default_v1 v1 - the same id appears on the receipt.