Skip to main content
Make three separate choices: how your agent calls Conto, who signs the transfer, and which payment protocol the recipient accepts. An SDK integration can use an external wallet and pay an x402 API; these choices can work together. In every case, the agent owner or budget holder configures Conto on the buyer side. Merchants do not install Conto; protocol compatibility determines how they receive payment. Read buyer-side control for the authority boundary.

​
1. Connect your runtime

For your first integration, use the Tempo Testnet quickstart. An autonomous agent can start with the simulated sandbox.

​
2. Choose who signs

Start with managed execution if you want Conto to sign. Use external execution when you already operate a signer. A managed wallet is not a universal guarantee against transfers outside Conto: owner authority and key export matter. Read wallet ownership and custody.

​
3. Match the recipient’s payment protocol

Conto’s x402 and MPP pre-authorization endpoints evaluate controls. Your protocol integration still performs signing and the paid service request. Check payment support and prerequisites before selecting a network.

​
Continue with the same payment ID

Regardless of the integration, preserve returned IDs. Human review and HTTP 402 require a next action; a submission timeout requires reconciliation. Follow track and recover a payment before treating a request as settled or creating another payment intent.