Yes, but only if you use an agent wallet that supports gas abstraction. In a regular wallet with only USDC and no ETH, you cannot even send a single transaction.
I made this mistake when I first started running agents. I loaded 500 USDC into an agent wallet and excitedly told it to call an on-chain data API. It returned "insufficient funds for gas * gas price + value". I wondered how 500 USDC was not enough. Later I realized the wallet did not even have 0.001 ETH, so it could not pay gas.
Why Traditional Wallets Must Hold Native Tokens
The rule for ordinary EOA wallets (such as a regular MetaMask account) is: whoever sends the transaction pays the gas, and it must be paid in the chain's native token. On Ethereum it is ETH, on BNB Chain it is BNB, and on Polygon it is POL.
This design works for normal transfers, but it creates problems for AI agents:
Agents run automatically and will not go to an exchange to buy gas
Agents doing cross-chain operations need to prepare a different native token for each chain
Once gas runs out, the agent simply stops, and you may not know when it died
Solution Comparison: How AI Agent Wallets Solve This
| Solution | How it works | Typical tools |
|---|---|---|
| Gas Abstraction (Paymaster) | The agent pays in USDC, and a Paymaster contract converts USDC into native tokens behind the scenes to cover gas | ERC-4337 wallets, Coinbase Agentic Wallet, Polygon Agent CLI |
| Native stablecoin gas pricing | The chain itself directly supports charges and settlement in USDC, with no conversion step | Circle Arc, Injective (x402) |
| Gas sponsorship | Developers or dApps cover gas for users (agents) through a Paymaster, so users do not need to manage it | Project marketing campaigns, membership services |
Sources:
ERC-4337 Paymaster model
Circle Agent Stack: supports stablecoin gas abstraction, USDC micropayments as low as $0.000001, no gas fee
Polygon Agent CLI: stablecoin native payments, agents do not need to hold POL or any native gas token to execute on-chain operations
How to Do It in Practice
Case A: You Use a Toolkit That Supports Gas Abstraction
Polygon Agent CLI supports native stablecoin payments from the start. When an agent performs on-chain operations such as sending, swapping, and bridging, the underlying gas abstraction layer automatically handles fee conversion, so the agent only needs to hold USDC.
Coinbase Agentic Wallet also supports gasless operations. Agents can hold USDC and send, trade, or pay for services without holding native gas tokens.
What to do:
Install the corresponding CLI tool (for example,
npm install -g @polygonlabs/agent-cli)When creating the agent wallet, gas abstraction is automatically configured
Send USDC directly to the wallet address. You do not need to buy POL or ETH separately
What success looks like: After the agent completes an on-chain transaction, the wallet's USDC balance has decreased by the amount plus fees, but no native token was spent.
Case B: You Run an Agent from a Regular Wallet
If you use a traditional EOA wallet without gas abstraction, you must hold native tokens.
Minimum gas reserve suggestions:
Ethereum mainnet: reserve at least 0.01–0.02 ETH for gas fluctuations
Base/Arbitrum/Optimism: 0.001–0.005 ETH (gas on these L2s is much cheaper)
Polygon: 0.1–0.5 POL
This gas budget cannot be skipped. If the network suddenly becomes congested and gas runs out, the agent will get stuck.
Case C: You Call Paid APIs on the x402 Protocol
The x402 protocol itself is designed for machine-to-machine payments. Agents only need to hold USDC, and no native gas is required.
Injective's x402 implementation already allows AI agents to pay on-chain fees on their own at sub-cent costs. Coinbase Agentic Wallet's x402 integration also supports settlement in USDC, with no gas needed.
What to do:
When the agent calls an API and receives a 402 payment request, it signs the payment directly with USDC
Underlying settlement is completed through infrastructure such as Circle Arc, and gas is handled by the protocol layer
What success looks like: The agent successfully called an API that requires x402 payment, returned data, and only USDC was deducted from the wallet.
Common Reasons for Failure
1. Assuming you can run transactions in a regular wallet just by depositing stablecoins. Ordinary EOA wallets do not support gas abstraction. You must pre-fund native tokens, otherwise all transactions will get stuck with "insufficient funds".
2. Only preparing gas for one chain when doing cross-chain operations. If an agent runs operations on Ethereum but the wallet only has BNB, it still cannot send transactions. You need to prepare the corresponding native token for each chain separately, unless you use cross-chain gas abstraction tools.
3. Not accounting for gas price fluctuations. During network congestion, gas prices can rise several times. If the reserved gas is not enough, the transaction fails even though fees were already deducted at the simulation stage.
High-risk reminder: If your agent wallet supports gas abstraction, check whether this feature is enabled by default. Some wallets are created in normal mode by default. You may need to manually turn on the Paymaster or gas abstraction switch in settings; otherwise the agent will try to pay gas with the native token and fail. Check your tool's documentation to see whether parameters like
--gaslessor--paymasterneed to be explicitly enabled.
How to Verify the Operation Worked
Run a simple test transaction—have the agent send 0.1 USDC to a known address.
If the transaction succeeds, check the gas payer for this transaction in a block explorer. If gas was paid by a Paymaster contract, the transaction details will show a
Sponsored byfield.If the transaction fails, the error message will clearly indicate whether gas is insufficient or the gas abstraction configuration is wrong.
Verification channel: After a successful transaction, check the wallet's USDC deduction record and whether the native token balance changed. If the native token balance did not change, gas abstraction is really working.
