A spending box for your AI agent
Put USDC in a box that only you control. Your agent pays for things by itself, but only inside your rules: at most so much per payment, so many payments a day, only to the services you pick, until a date you choose. Stop it or take your money back at any time.
No admin key · No fee · No account or sign-up · New boxes require a clean payee verdict · v2 factory
Create a box
Open a box by its address
Start in four steps
- Get free USDC on Arc: claim three times a day, no gas, no sign-up.
- Create a box above, put USDC in and name the agent that may spend it.
- Connect your agent to our tools (MCP:
https://apexfaucet.xyz/api/mcp/arc) and give it the box address: it pays x402 from the box, inside your rules. - Watch it in Agent City: every agent in Arc’s registry has a tower there.
Why a box and not a wallet
Giving an agent its own wallet means trusting it with everything in it. Limits written in an agent's software or on someone's server hold only as long as that software and that server do. Here the limits are checked by the contract on Arc on every payment, so a buggy agent, a leaked agent key or a bad prompt can never move more than your rules allow: at most the per-payment limit, at most so many times a day, only to your list, and never after the end date.
| Managed agent wallet | Mandate box | |
|---|---|---|
| Who checks the limits | the provider’s policy service | the contract on Arc, on every payment |
| What you need | an account with the provider | your own wallet and one confirmation |
| Who can change your rules | you, through the provider’s service | only you, from your own wallet: the contract has no admin key |
| Fee | set by the provider | none |
| Pays x402 | depends on the provider | yes: EIP-1271 signature, or the box’s pay() |
One limit nobody can remove: USDC’s issuer can pause USDC or block an address, and that would stop owner and agent alike.
For agents and developers
The agent pays in one of two ways, both checked against the same rules and the same daily count:
Standard x402. The agent signs a normal EIP-3009 USDC authorization with the box as the payer. Arc's USDC asks the box whether to allow it (EIP-1271), and the box says yes only when the agent signed exactly that payment and it fits the rules. On a new box the bytes the seller submits also carry the PayeeVerdict and the attester's signature. pay() spends that verdict once. An x402 payment can reuse one unexpired verdict on each free daily slot until it expires; the daily count still applies. A box from the older factory does not read a verdict. The seller's x402 checkout must check the payer with EIP-1271 and settle with the bytes-signature version of the transfer; ours does. A checkout that only checks plain wallet signatures turns a box payment away.
Direct. On a new box the agent calls pay(to, amount, slot, ref, verdict, signature). The verdict is the APEX PayeeVerdict, the payer on it is the box, and that call spends the verdict once. A box from the older factory still uses pay(to, amount, slot, ref) and does not read a verdict.
import { x402Fetch } from './sdk/mandate.mjs';
// pays a 402 on Arc from the box, inside the owner's rules.
// On arc-mandate-2 the SDK fetches a PayeeVerdict with payer = the box and refuses anything that is not clean.
// On arc-mandate-1 the call is the same and the box does not read a verdict.
const res = await x402Fetch('https://apexfaucet.xyz/api/x402/arc-gold',
{ pub, account: agentKey, box: '0xYourBox', maxUsd: 0.01 });
Proof: our own agent uses one
Our demo agent spends from our own v1 box (our money, at most 0.01 USDC per payment, 20 payments a day, only to our shop). That box does not read a payee verdict. On 7 October 2026 it bought gold data twice and was refused once, all on Arc mainnet:
- standard x402, signed by the agent, approved by the box: 0.003 USDC paid
- direct payment through the box: 0.003 USDC paid
- 0.010001 USDC, one millionth over its limit: refused by the box (Refused: over the per-payment limit)
Our own v2 box 0x3c95f7e8…8bb9 (our money, owner and agent are our operator) paid 0.01 USDC to our receive wallet on 3 Nov 2026: tx 0x9c7d6ed6…16cd7. Before that payment, a verdict that was not clean reverted. The same verdict could not pay the next free slot.
New boxes use factory 0x91957bd6…af9d3 (arc-mandate-2, box code 0x9684274b…f548). Every agent payment needs a clean PayeeVerdict whose payer is the box. pay() spends that verdict once. An x402 payment can reuse one unexpired verdict on each free daily slot; the daily count still applies. Existing boxes stay on factory 0x69e444f7…6b26 and do not read a verdict. No admin, no fee, no upgrade. v1 source is verified on the Arc explorer. The v2 factory and the v2 implementation are Sourcify exact matches (factory, implementation). Code, tests and the agent SDK: github.com/apexfaucet-hub/arc-mandate. Not audited by a security firm, so put in what you would give the agent anyway.
Each payment uses one of today's numbered slots, and a slot is a USDC authorization nonce. Arc's USDC records the slots spent by x402, the box records the ones spent by a direct payment, and each path checks both, so no slot is used twice. Days are UTC days: an authorization signed for today is refused after midnight UTC. A box holds USDC; any other token sent to it can be taken out by the owner.