Set transfer limits and address rules on your agent wallet to control how it can move USDC and interact with contracts.
Spending policies cap the USDC and EURC your agent wallet moves and restrict the
wallet to specific recipient or contract addresses. When a policy applies,
Circle rejects requests that exceed a limit or violate an address rule. Policies
apply to mainnet agent wallets only. When no custom transfer limit applies, the
default limit is 100 USDC per month.For the recommended setup, set a global transfer limit, then add a contract
allowlist on every blockchain your agent uses.
Use Circle CLI 1.4.0 or later to set, view, or reset global transfer limits. Run
circle update to
update your CLI.
Spending policies require a mainnet agent wallet. Testnet is not supported.
Setting a policy triggers a second email OTP to confirm the change. The OTP is
used once and not stored.
Choose the policy type that matches your goal.
Transfer limits
Allowlists and blocklists
Setup
Transfer limits cap the USDC and EURC your agent moves through Circle. A global
limit applies on every supported Ethereum Virtual Machine (EVM) mainnet, but it
doesn’t restrict which contracts your agent calls. Pair it with a contract
allowlist on the Allowlists and blocklists tab.Token approvals count at their full amount when submitted, so a swap or bridge
counts once, at its approval step. Approve only the amount each spender needs.
Steps
1
Set the limits
Run circle wallet limit set without --chain to set a global limit. All
four caps are required: per-transaction, daily, weekly, and monthly.
Circle sends an email OTP to your agent session email to confirm the policy
change. Limits must satisfy: per-transaction ≤ daily ≤ weekly ≤ monthly.To set a limit for one blockchain, add --chain ARC. When global and
blockchain limits both apply, the stricter value wins for each cap. A
blockchain with neither limit uses the 100 USDC monthly default.circle wallet limit set creates a new rule and fails if that rule already
exists in the same scope. To change an existing limit, run
circle wallet limit reset
for that scope first.
2
Verify the policy
View the global limit, then check the limits on Arc:
Check Scope to see if a rule covers All EVM chains or one blockchain.
Check Origin for CUSTOM or DEFAULT.
Setup
Allowlists and blocklists apply to one blockchain and require --chain.
Contract rules match the contract your agent calls. Recipient rules match
transfer recipients and, for USDC and EURC approvals, the spender address.Add a contract allowlist on every blockchain your agent uses, alongside your
transfer limit. Each allowlist limits contract calls through Circle to the
addresses you approve on that blockchain.Plain transfers with circle wallet transfer and fast Gateway deposits with
circle gateway deposit --method eco don’t require the USDC contract on the
contract allowlist. Transfer limits and recipient rules still apply.
The USDC contract on the allowlist
Effect
Excluded
Blocks the USDC approval step used by swaps, bridges, and direct Gateway deposits that need a new approval.
Included
Allows USDC approvals to any spender unless a recipient rule restricts it. Add contracts only for the swaps, bridges, or Gateway deposits you need.
The contract allowlist checks the called contract, not an approval’s spender
argument. Allowing a token contract permits approvals to any spender unless a
recipient rule restricts it. These policies check requests sent through Circle
and don’t revoke existing allowances. A spender can use an existing allowance
outside Circle without these checks.
Include every contract your agent calls on a blockchain in that blockchain’s
allowlist:
Run circle contract address usdc --chain <chain> and circle contract address gateway --chain <chain>. Select GatewayWallet at 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE.
Run circle contract address usdc --chain <chain> and add 0xB3FA262d0fB521cc93bE83d87b322b8A23DAf3F0. circle contract address doesn’t list Bridge Kit contracts.
The ERC-20 token you sell and Circle’s Swap Kit adapter contract
Look up USDC or EURC with circle contract address <usdc|eurc> --chain <chain>, or check your sell token’s address. Also add 0x7FB8c7260b63934d8da38aF902f87ae6e284a845.
Include every contract your agent calls on that blockchain. The
contracts table lists Bridge Kit, Swap Kit,
and GatewayWallet addresses.
2
Set the rule
Run circle wallet limit set with --chain, --rule-type, and a
bracketed, comma-separated --targets list of every approved address on
that blockchain.For contract rules, the CLI sets --policy-type contract automatically. For
example, to allow Arc USDC and GatewayWallet for direct Gateway deposits
while keeping your transfer limit in place:
circle wallet limit set \ --address 0xYourWalletAddress \ --chain ARC \ --rule-type contract-allowlist \ --targets "[0x3600000000000000000000000000000000000000,0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE]"
Repeat this command on every blockchain your agent uses, with that
blockchain’s approved contract addresses.For recipient rules, include --policy-type stablecoin. For example, to
block two recipient or spender addresses on Arc:
circle wallet limit set \ --address 0xYourWalletAddress \ --chain ARC \ --policy-type stablecoin \ --rule-type recipient-blocklist \ --targets "[0xBAD1,0xBAD2]"
--rule-type accepts:
contract-allowlist or contract-blocklist: allow or block contract
calls to specific contract addresses.
recipient-allowlist or recipient-blocklist: allow or block transfers
to specific recipients and USDC or EURC approvals to specific spenders.
Circle sends an email OTP to confirm each rule. To add or remove addresses
in an existing list later, run
circle wallet limit reset
with --chain first, then re-apply the rules you want to keep on that
blockchain.
3
Verify the policy
Confirm your effective limits and address rules on that blockchain:
circle wallet limit --address 0xYourWalletAddress --chain ARC