AgentWallet ·

Live demo — provision an agent wallet in your browser

Open a sandboxed AgentWallet in your browser. Type an agent name and caps, hit run, and watch the wallet, virtual card, USDC address, inbox, phone number, Principal binding and MCP endpoint come up — exactly as they would in production. Sign your first AP2 IntentMandate with a passkey, settle a real x402 USDC payment on Base Sepolia, and inspect the trace ledger end-to-end. No signup. No email. No real money. Full feature parity with prod. Reset whenever you want and try a different shape of agent. The same flow that takes our customers' engineers 60 seconds in the dashboard takes you 60 seconds in the browser — the only difference is the sandbox keys aren't yours to keep.

  • Mint a sandbox Principal and Agent in 30 seconds, no email or credit card required — the sandbox issues you a temporary Principal you can sign mandates from.
  • Type the agent name, choose a Principal, set the daily cap and geofence, select the rails (Card / ACH / SEPA / Pix / USDC / SWIFT) and the comms channels (Email / Phone / WhatsApp), then click Provision Wallet.
  • Watch the provisioning stream live in a terminal panel — wallet_id assigned (412 ms), virtual card issued (4242 0815 •••• 1126), USDC address minted on Base, email/phone/WhatsApp allocated, Principal verified with signature rights, caps and geofence applied, MCP endpoint spun up. Total elapsed: ~2.8 s.
  • Sign a real AP2 IntentMandate with WebAuthn — use the passkey on your laptop or phone, the same one you'd use for production. The signature is verified server-side and audited into ap2_mandate_audit.
  • Settle a real x402 payment on Base Sepolia. The sandbox merchant returns HTTP 402, your agent signs an EIP-3009 transferWithAuthorization for USDC, replays the request with the signed authorization in the X-PAYMENT header, the merchant settles, you see the on-chain transaction hash and the unified trace row.
  • Drop the per-agent MCP URL into a hosted Cursor or Claude Desktop session and call the 14 typed tools live — wallet.status, wallet.send_payment, wallet.send_usdc, wallet.x402_pay, identity.sign_mandate, comms.send_email, approvals.poll and more.
  • Inspect the unified trace ledger — every credit, debit, hold, release and refund as one row each, with trace_id, mandate_id and rail visible. Filter by agent for a complete chronological history.
  • Reset the sandbox at any time — every state is namespaced to your browser session and cleared when you close the tab. No real money, no real cards, no PII collected.
  • Graduate to production with one button — the same API surface, the same MCP tool catalog, the same AP2 chain. You get sandbox-to-prod feature parity, which means everything you tested in the demo behaves identically when you go live.

Frequently asked questions

Do I need to sign up to try AgentWallet?
No. The browser demo issues you a temporary sandbox Principal and Agent that work end-to-end without any email, password or credit card. If you want sandbox keys you can keep across sessions (for example, to wire up your own LLM via MCP), sign up at /sign-up — that gets you full sandbox keys in 30 seconds with no payment method required.
Is the demo using real money?
No. The fiat side uses Payouts.com sandbox endpoints — payouts settle to test recipients, never to real bank accounts. The USDC side uses Base Sepolia (the public Base testnet) — settlements are real on-chain transactions but use test USDC, not mainnet USDC. Virtual cards are tokenized at our issuer's sandbox; they cannot be charged at real merchants. You can reset and re-run as many times as you want.
Can I sign a real AP2 mandate with my own passkey?
Yes. The demo uses WebCrypto with a non-extractable keypair backed by your device's authenticator (Touch ID, Face ID, Windows Hello or a hardware security key). The signed JWS is verified server-side and written into ap2_mandate_audit just like production. The keypair never leaves your device.
Can I call the MCP endpoint from my own Cursor / Claude Desktop?
Yes, with sandbox keys. The hosted demo uses a temporary session that expires; to drop the per-agent MCP URL into your own MCP client, sign up at /sign-up (30 seconds) and the dashboard issues you persistent sandbox keys. The MCP tool catalog and behaviour are identical to production.
How fast is provisioning in the demo vs production?
Identical — median 412 ms, p95 800 ms for the POST /agents call itself. The demo adds a small UI animation on top (~2.8 s total wall-clock) so you can watch each provisioning step stream into the terminal panel. In production with no UI animation, every primitive (wallet, card, USDC, inbox, phone, Principal, MCP) is live by the time the API response returns.