Create a Circle developer account and enable Developer-Controlled Wallets (not User-Controlled); developer-controlled wallets are appropriate when your service orchestrates wallet actions on behalf of agents, since the private key operations are handled by Circle's infrastructure, not your application server
Provision wallets via the Circle Wallets API: each wallet is identified by a wallet ID and is associated with a blockchain network (e.g., Base, Ethereum, Solana); use wallet sets to group agent wallets for policy and reporting purposes
Integrate the Circle Agent Stack (launched May 2026): Agent Wallets provide programmable spend limits and policy guardrails; Circle Gateway enables receiving payments as small as $0.000001 USDC with revenue credited to a Gateway Balance; the Agent Marketplace enables service-to-service discovery
For agent payouts at scale, use the Circle Wallets batch transfer capability combined with Thirdweb Engine; batch USDC payouts across multiple recipient wallets atomically, settling on the configured chain with CCTP if cross-chain recipients are involved
Configure your Circle Gateway receiving endpoint to respond to x402 402 requests from paying agents; the Gateway deposits received USDC into your Gateway Balance, which you withdraw to a designated Payout Wallet via the Circle API
Test the full payout lifecycle in Circle's sandbox, including a nanopayment (sub-cent amount), a batch payout to multiple wallets, and a cross-chain transfer via CCTP — verify each leg with Circle's transaction status API before treating receipts as final
Known gotchas
Developer-Controlled Wallets require your server to call Circle's API for every transaction; if your server is down, the agent's wallet cannot send funds — ensure your Circle API integration has appropriate retry and failover logic
Gateway Balance withdrawals to Payout Wallets are not instant; factor the withdrawal processing time into your revenue reconciliation cycle and do not assume Gateway Balance equals immediately spendable on-chain USDC
Circle's CCTP cross-chain transfers require gas on the destination chain; ensure receiving wallets on non-gas-sponsored chains hold enough native token to accept inbound transfers, or use a gas sponsorship service to avoid stuck transfers
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp