agent-payment-x402

You can enable autonomous agent payments by implementing the x402 HTTP payment protocol with MCP tooling, which handles payment negotiation, budget checks, and retries on 402 errors while enforcing per-task and per-session spending policies.

The x402 payment protocol is an HTTP-based standard that enables AI agents to autonomously negotiate and complete payments for APIs or services, automatically handling 402 Payment Required errors through retries and integrated budget validation.

Yes, autonomous agent payments support non-custodial wallets using ERC-4337-style accounts, where an orchestrator enforces spend policies and ensures agents never hand over direct custody of funds during transactions.

You can configure spending limits by defining per-task budgets, per-session budgets, and allowlisted recipients within your orchestrator, which the policy enforcement workflow checks before approving any agent payment.

Yes, the MCP integration exposes standard MCP tools that slot directly into existing agent harness setups, allowing you to invoke the agentpay tool to initiate payments without restructuring your current architecture.

Autonomous payment policies are limited by their configured constraints: agents cannot transact with non-allowlisted recipients, exceed per-task or per-session budgets, or bypass rate limits enforced by the orchestrator's policy workflow.