Arc-native agent spend control
Budgets before autonomy
Policy controls for AI agents spending USDC on Arc. Approve, reject, or audit every autonomous payment before an agent can touch a budget.
Live on Arc Testnet
ArcAllowanceRegistry anchors agent registrations, policy hashes, spend requests, and spend decisions as audit proof. No custody.
Problem
Agents should not get unlimited wallets. Budgets, merchant allowlists, approval thresholds, policy checks, and audit receipts are the minimum operating layer for autonomous USDC spend.
How it works
An agent requests a payment, ArcAllowance evaluates its policy, and the flow either approves, rejects, or routes the request to a human approver before mock settlement.
Why Arc / USDC / Circle
USDC keeps budgets readable, Circle Wallets point toward controlled agent custody, Gateway/x402 supports small payments, and Arc memos make reconciliation native.
Mock mode today, Arc-native tomorrow
Built for Gateway/x402-style nanopayments, Arc transaction memos, and Circle Wallets.
The MVP is local and safe. It simulates authorization, settlement, memos, and receipts while making the upgrade path to Circle Wallets, Gateway/x402, Arc batching, and ERC-8004 agent identity explicit.
Agent
Autonomous request
Policy Engine
Budget and controls
x402/Gateway Authorization
Mock approval artifact
Arc Memo
Reconciliation ID
USDC Settlement
Mock mode today
Receipt Ledger
Audit trail
Demo scenarios
ResearchAgent buys a CPI dataset query for 0.03 USDC.
TradingAgent is blocked from paying an unknown alpha seller.
OpsAgent requests 45 USDC of compute and waits for approval.
Tiny API calls are batched into one mock Gateway settlement.