The financial backbone for autonomous software
Six tightly-integrated primitives — wallet, virtual card, principal, comms, MCP, controls — compose into one complete financial identity for any AI agent. Every primitive shares the same Company → Principal → Agent identity tree, the same signed AP2 mandate format, and the same trace ID. A USDC payment on Base, an ACH payout in the US, a Pix transfer in Brazil and a virtual-card swipe at any merchant all reconcile into one auditable row in one ledger — no joins across Mercury, Stripe and Coinbase, no reconciliation nightmares, no missing receipts. Provisioned in 412 ms with one POST /agents call. Free to start; you only pay for processed volume.
- 01 — Wallet. A multi-rail balance, native everywhere. Fiat and USDC side by side. Top up via card, ACH, SEPA, Pix, or a USDC transfer. Send to 208 countries on 9 outbound rails. The agent picks the rail; you pick what's allowed. Holds USD, EUR, GBP, BRL, INR, MXN and 85 more currencies native, plus USDC on Base.
- 02 — Virtual card. A real Visa or Mastercard issued per agent in seconds. Its own PAN, CVV and limits. PAN never leaves the PCI vault. Apple Pay / Google Pay tokenization for human-paired agents. Per-agent daily and monthly caps, per-merchant allowlists, MCC blocks (gambling, crypto exchanges, adult), country-level geofencing — all enforced server-side.
- 03 — Principal. Every action cryptographically signed. Every agent runs under a Principal — a verified human or service. Every transaction is signed, logged, attributable. One Principal can own many agents; agents can't sign for each other. Multi-sig 2-of-3 humans for high-value spend. Rotation on Principal change without re-provisioning agents. Verifiable signatures exposed via webhook + audit API. Your CFO can answer 'who authorized this' in court.
- 04 — Comms. Real comms, real identity. Every agent gets a deliverable email address (e.g. [email protected]), a phone number, a WhatsApp Business handle and a public profile page. Vendors call, banks 2FA, candidates DM — the agent answers, not you. SMS-verifiable phone numbers in US, UK, IL, BR and IN. WhatsApp Business with template approval handled. Inbox with structured extraction for invoices, receipts and OTPs. End-to-end log of every message in the Principal audit.
- 05 — MCP server. Plug. Pay. One MCP endpoint per wallet at mcp.agentwallet.ai/<wallet-id>. Any LLM, any agent framework, your homegrown agent — they all connect, sandbox and transact in 60 seconds with no SDK boilerplate. Tools: spend, refund, quote, balance, statement, contact, mandate.sign, x402.pay, and more. Capabilities map auto-injected into the agent's system prompt. Spend approvals streamed to Principal via webhook + WhatsApp. Idempotent — agent retries are safe.
- 06 — Controls. Caps that travel with the agent. Daily, weekly, monthly. Per merchant, per category, per country. Approval workflows for spend over threshold (tap-to-approve via WhatsApp or iOS push). Kill-switch in one click, resumable from the same wallet ID. Anomaly detection auto-freezes on out-of-policy patterns. Every guardrail you'd want around a 22-year-old new hire — applied to a model that processes 1,000 decisions an hour.
- How it composes — one POST /agents call provisions all six. The wallet binds to fiat rails (ACH, SEPA, Pix, UPI, Wire/SWIFT) and to USDC on Base / Polygon / Solana. The card binds to Visa or Mastercard issuing. The Principal binds to a verified human with WebAuthn signing. The comms binding allocates email, phone and WhatsApp. The MCP endpoint exposes the agent to any LLM. The controls layer applies caps, MCCs and geofences.
- Unified trace ledger — every fiat payout, card authorization and USDC settlement writes one row per payment keyed by trace_id. Filter by agent for a complete replay-safe history; join on mandate_id to replay exactly which AP2 mandate authorized a given spend.
- Built on Payouts.com — 17 fiat payout rails, KYB at the Company tier, regulated infrastructure. Built on Coinbase CDP — keys in Trusted Execution Environments, never on our servers. Built on AgentMail and AgentSim for comms. Open standards on every layer — MCP, AP2, x402, ACP.
Frequently asked questions
- What does the AgentWallet product actually include?
- Six primitives in one product: (1) Wallet — multi-rail fiat + USDC balance across 17 payout rails. (2) Virtual card — real PCI-vaulted Visa or Mastercard per agent. (3) Principal — verified human signer with WebAuthn. (4) Comms — real email, phone number, WhatsApp Business handle and public profile page per agent. (5) MCP server — per-agent endpoint with 14 typed tools for any LLM client. (6) Controls — per-call, daily, monthly, per-merchant, per-MCC, per-country caps with approval queues and anomaly auto-freeze.
- How is this different from issuing a card and a bank account separately?
- Three differences. (1) Identity tree — every primitive is bound to the same Principal-Agent-Company graph, so revoking a Principal pauses every primitive at once. (2) Trace ID — fiat, card and USDC settlements share one trace row, so reconciliation is one query, not a join across three vendors. (3) Policy gate — caps, MCCs, geofences and approval thresholds run in one Express process that signs the payment, so a breach is rejected before any rail is hit, never reconciled after the fact.
- Can I use just the wallet without the card or just the MCP without the card?
- Yes. Every primitive is independently nullable. You can provision an agent with only a USDC wallet, or only an MCP endpoint plus a fiat sub-account, or any combination. The MCP tool catalog adapts automatically to what's wired — an agent without card-issuing won't see card.* tools; an agent without crypto won't see x402.pay.
- How quickly does a new agent become live?
- 412 ms median, 800 ms p95, end-to-end. One POST /agents call provisions the agent row, the fiat sub-account at Payouts.com, the USDC wallet on Base via Coinbase CDP, the MCP endpoint, the AP2 keypair, the virtual card token at our issuer, the AgentMail inbox and the SMS/WhatsApp endpoints — all inside one Postgres transaction. When the 201 returns, every part is live and callable.