Every payment rail.
One programmable wallet.
Signets wallets sit across HTTP-native x402 payments, stablecoin transfers, and traditional bank rails. Fund once, spend anywhere — with the same policy controls layered on top of all three.
Wallet
HTTP-native payments
x402 is an open protocol for machine-to-machine payments over HTTP. An agent hits an endpoint, receives a 402 status with a payment request, pays inline, and retries — all in one request cycle. No invoices, no out-of-band auth.
On-chain stable payments
Fund wallets with USDC or USDT. Agents spend directly from on-chain balances — no fiat conversion, no bank account required. Transfers settle in seconds on supported L2 networks.
Bank transfers
Connect a bank account to fund wallets via ACH, wire, FPS, or SEPA. Issue virtual cards backed by those funds, or push payouts to vendors. Standard banking rails with a programmable control layer on top.
Wallet Features
The same control plane across all three rails. Fund, allocate, monitor, and freeze from a single API.
Multi-rail routing
One wallet, multiple payment rails. Route spend to the cheapest or fastest rail based on merchant, amount, or agent policy.
Balance isolation
Create sub-wallets scoped to agents, teams, or campaigns. Each gets its own balance and controls — overspend in one never bleeds into another.
Real-time balance
Check balances and pending transactions via API at any time. Webhooks fire on every debit, credit, and authorization event.
Programmable top-ups
Define auto-funding rules: refill to $X when balance drops below $Y. Keep agents running without manual intervention.
Audit trail
Every wallet event — fund, spend, refund, freeze — is logged with timestamps, agent metadata, and rail info. Exportable as CSV or via API.
Freeze & revoke
Freeze a wallet or sub-wallet instantly. Unspent balance stays locked until you release it. Full control at any depth of the hierarchy.
Wallet Hierarchy
Fund a wallet. Pick a rail.
Start with bank or stablecoin — add x402 when your agents are ready for it.