Authenticate with the Circle API using your API key (YOUR_KEY) and set the correct environment (sandbox vs. production) base URL.
Create a blockchain payout by calling the Circle Payouts API with the destination wallet address, amount in USDC, and the target blockchain (e.g., Ethereum, Polygon, Solana — choose based on fee and speed requirements).
Record the Circle payout ID returned in the response; use it to poll the payout status endpoint or listen for Circle webhook events for status transitions (pending → complete or failed).
Confirm on-chain settlement by verifying the transaction hash in the Circle payout response against a blockchain explorer or your own node, checking for sufficient block confirmations before considering the payment final.
Reconcile Circle USDC payouts against your internal ledger: debit the USDC balance, credit the payout obligation, and mark settled once on-chain confirmation is received.
Handle payout failures (e.g., invalid destination address or insufficient balance) by catching the error response and alerting the operations team for manual resolution.
Known gotchas
On-chain transaction finality varies by blockchain: Ethereum requires more confirmations than Polygon or Solana — define your confirmation threshold per chain and do not treat a single-block confirmation as final on high-value payouts.
Circle USDC balances are denominated in USD-equivalent cents internally but displayed as USDC in the API; do not conflate the Circle API amount field format with on-chain token decimal precision (USDC uses 6 decimals on most chains).
Blockchain gas fees and Circle service fees are separate from the payout amount; the recipient receives the specified amount, but your Circle balance must cover the amount plus fees — ensure buffer funding.
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