According to Woofun AI, Circle officially launched the Facilitator Service, which aims to solve the pain points of gas fees when AI agents make USDC payments on the blockchain, allow agents to complete transactions without holding a separate Gas wallet, and Circle assumes responsibility for identity review, transaction submission, and on-chain settlement.
On September 19, Circle announced that the service fully supports Arc, Base, and Polygon Proof-of-Stake (PoS) networks and builds payment processes based on the x402 protocol. In actual application scenarios, when an AI agent requests a data set, an API response, or a completed task from an online service, the server returns a quote including the amount, accepted payment method, blockchain network, and target address. As an open protocol based on the web standard 402 “payment required” status code, the x402 protocol provides a standardized communication language for buyers and sellers. When the server returns this status code, the buyer only needs to send proof of authorized payment, and subsequent fund transfers and blockchain operations are taken over by Circle's new service.
Notably, x402 itself does not directly handle fund transfers, but rather regulates the interaction process. The true exchange of value depends on the underlying infrastructure support provided by Circle.
In traditional blockchain transactions, every operation requires a gas fee, and usually requires the use of a native network token. This forces buyers with USDC to maintain additional gas wallets, increasing the complexity of key management and fund monitoring. Although developers can pay for gas through the relay system, they need to protect the signature key themselves and ensure that the wallet balance is sufficient. Circle integrates this tedious process into its escrow service, issuing transfer instructions and covering gas fees through a relay system; buyers only need to authorize USDC payments.
According to data compiled by Woofun AI, the process uses the EIP-3009 standard, which allows token holders to authorize transfers through off-chain signatures. The signature message clearly indicates the payment wallet, recipient, USDC amount, authorization expiration date, and nonce unique code to prevent repeated use. Before submission, Circle checks the validity of signatures, buyer balances, and consistency of receiving addresses, and securely reviews both parties' addresses, and records payment information to prevent repeated requests from incurring additional charges.
Despite being automated at the technical level, the signature only proves that the wallet approves the transfer and cannot ensure that the AI agent is acting within the budget or following the owner's instructions. Therefore, permission boundaries are still determined by people or application operators, and agent behavior can be restricted by using wallets with limited balances, programmatically limiting specific operations, limiting the scope of recipients, or setting spending limits. Circle makes it clear that its Facilitator service does not verify the specific purpose of the transaction or the scope of the agent's authorization; it only processes requests, signs USDC payment instructions, sets prices and target addresses, requests settlement and release paid resources, verifies the validity of the authorization, reviews identity, makes gas payments, and submits transfers.
Although this design reduces the probability of errors and shortens development time, it also makes sellers highly rely on Circle's ability to accept requests, review identity, relay system funding, and submit transactions. If the escrow service fails or refuses to process the request, the settlement process may be interrupted even if the underlying blockchain is running properly. This is an operational dependency rather than a fund storage issue. Circle emphasized that it does not hold or control buyers' funds, and that USDC remains in the buyer's wallet until the Token contract performs authorized operations. The formal production environment requires sellers to authenticate with Circle's API keys, and limited amounts of keyless testing only apply during the development phase.
Network-level risks still exist. Circle warns that payments on the Base and Polygon Proof-of-Stake (PoS) networks may be affected by blockchain restructuring, that is, newly generated blocks are replaced, resulting in non-final settlement results. By contrast, the Arc Network's settlement results are considered final. The Arc network currently hosts trading infrastructure such as the v2, v3, and v4 versions of Uniswap and the UniswapX platform, so that payment settlement and on-chain liquidity services are concentrated in the same ecosystem.
Although the two are not automatically connected, and there is no guarantee that a large number of AI agent transactions will occur, this integration enhances the importance of restricted wallets — restricted wallets can enhance the utility of autonomous payments, and unlimited signature keys may cause the smart body to suffer significant losses due to operational errors. Circle can verify the validity of signatures and send payments, but whether to authorize agents to sign signatures is ultimately still up to the app and its owner. This indicates that the AI agent economy must balance the ideal of decentralization with the convenience of centralization while pursuing efficiency.