Skip to main content
Your agent asks Conto before it pays. Conto approves the payment, holds it for a person, or denies it with a reason. Payments use supported stablecoins or, on Builder and Enterprise plans, connected cards.

​
Start with a payment

Make your first payment

Create an agent and funded Tempo Testnet wallet, then verify an onchain payment.

Try the agent sandbox

See approved and denied decisions without an account, signer, or movement of funds.

​
Where Conto fits

Agents and budget owners connect through the SDK, REST API, MCP, CLI, or Conto Pay. Conto checks each request with its policy engine, network intelligence, approvals, and agent wallets. Approved payments settle in stablecoins or x402 pay-per-call, and each one is recorded with the agent, policy result, approval, counterparty, settlement, and receipt. Agents and budget owners connect through the SDK, REST API, MCP, CLI, or Conto Pay. Conto checks each request with its policy engine, network intelligence, approvals, and agent wallets. Approved payments settle in stablecoins or x402 pay-per-call, and each one is recorded with the agent, policy result, approval, counterparty, settlement, and receipt. Conto only checks payments that go through it. If your agent holds its own wallet keys, it can still send funds without asking Conto. See wallet ownership and custody.