How Conto works
When an agent goes to pay, Conto checks the request against your rules first, pauses anything that needs a second look, and keeps a record either way. Conto decides what clears, not what your agents buy. You choose whether Conto holds the wallet or the agent keeps its own key.
One control plane, from request to record
Every payment takes the same path. It comes in through your SDK or API, clears the same checks before it settles, and ends up in one record you can reconcile. The checks run before the money moves, not after.
Agents and operators
Integration surfaces
Control plane
Conto
Every request is checked and scored before any funds move, then logged with full context.
Policy engine
Limits, trust, categories, and velocity evaluated before settlement.
Network intelligence
Trust and risk scores on every counterparty.
Approvals
Exceptions route to a human with full context.
Agent wallets
A governed wallet identity for each agent.
Settlement
From wallets Conto manages or wallets controlled by the agent.
System of record
Every payment reconciled with full context for finance, operations, and security.
Inside the control plane
Every payment runs through the same set of checks. Each one is its own part of the product.
See the full productRuntime controls
Policy Engine
Limits, categories, velocity, and counterparty rules, checked on every request before it settles.
ExploreCounterparty trust
Network Intelligence
Identity, past dealings, and a trust and risk score for every recipient.
ExploreHuman review
Approvals
Anything unusual goes to a person with full context, by email, Slack, Telegram, or WhatsApp.
ExploreWallet operations
Agent Wallets
A wallet for each agent, held by Conto or by the agent itself.
ExploreFinancial visibility
Audit & Reconciliation
One record of every decision and payment, ready for finance and security to reconcile.
ExploreBuild surfaces
Developer Platform
SDK, REST, MCP server, and CLI to add these controls to any agent.
ExploreOne policy check, two execution paths
You pick who holds the keys. With a managed wallet, Conto sends the payment once it clears. With self-custody, the agent keeps its own key and sends the payment itself, while Conto signs off first and records the result after. The policy check and the audit trail are the same either way.
Managed wallet
Conto decides, the wallet sends · Conto holds the rules and the record
Agent requests a payment
POST /payments/requestConto evaluates policy
Human approves
Routine spend skips this step.
Wallet releases the funds
Once the request clears, the managed wallet signs and sends. Conto holds the decision and the record.
POST /payments/:id/executeLogged with full context
tx 0x9f2c… ✓
policy · approval · settled
Agent-controlled wallet
Agent keeps its own keys · Conto authorizes, logs on confirm
Agent asks to authorize
POST /payments/approveConto evaluates policy
Human approves
Routine spend skips this step.
Agent signs with its own key
Conto returns a 10-minute approval. The agent sends the transaction.
Agent reports the transaction ID
POST /payments/:id/confirmtx 0x9f2c… ✓
policy · approval · settled
Same payment context, same policy evaluation, same audit trail. Who signs and sends is where the path diverges.
What teams build with it
The same controls sit behind a lot of different work, whether an agent is paying people, buying from suppliers, or paying for compute by the call.
Browse all solutionsPayouts
Instant Payouts
Pay people or move funds the moment work is done, with every payout checked before it goes out.
ExploreProcurement
Autonomous Procurement
Agents find suppliers and buy, while Conto controls who they can pay, how much, and when to ask.
ExploreCredits
Refunds & Credits
Small refunds and credits clear on their own. Larger ones go for review.
ExploreVendor trust
Vendor & Counterparty Controls
Known vendors clear. New, changed, or risky ones pause for a look.
ExploreMachine payments
Micropayments and x402
Per-call and per-session budgets for APIs, inference, and compute.
ExploreEscalation
Approval Routing
Routine spend keeps moving. High-value or unclear requests pause for a person.
ExploreA control plane, not a custodian
Conto decides whether a payment goes through. The money itself moves on the rail, out of a wallet you manage or one the agent controls. Conto is never the one buying.
Conto is
- A policy check before money moves
- Trust and risk scores on every counterparty
- Approvals with separation of duties
- One record for finance and security
Conto is not
- Your checkout or the buyer
- A custodian, by default
- A payment rail
- A black box
Make your first policy-checked payment
Spin up an agent, wallet, and policy in the sandbox. It takes about ten minutes.
Keep exploring