Six primitives.
One agent identity.
AgentWallet is six tightly-integrated primitives — wallet, card, principal, comms, MCP, controls — that compose into a complete financial identity for any AI agent.
A multi-rail balance,
native everywhere.
Allocated fiat balances and configured USDC signing integrations serve different payment paths. Resource and payment availability depends on account eligibility, provider configuration and the selected route.
- → USD, EUR, GBP, BRL, INR, MXN + 85 more — held native
- → USDC on configured networks; no automatic bridging promised
- → Pay-in account eligibility varies by provider
- → Settlement timing depends on the provider and route
A card per agent.
Issued through eligible provider flows.
Eligible agents can be assigned card resources with provider-specific controls. Issuance and merchant acceptance depend on the configured program.
- → Card issuance depends on the configured program
- → Per-agent daily / monthly caps · per-merchant allowlists
- → MCC blocks (gambling, crypto exchanges, adult)
- → Geofencing — country / region allowlists
- → Apple Pay / Google Pay tokenization for human-paired agents
Agent activity,
cryptographically signed.
Agents are associated with principals for ownership and policy management. Mandate signatures and activity records vary by payment path.
- → 1 principal → 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
Real comms.
Real identity.
Communication resources can be configured for an agent through supported providers. Email, phone and messaging availability are separate from wallet creation.
- → SMS-verifiable phone numbers in US, UK, IL, BR, IN
- → WhatsApp Business with template approval handled
- → Inbox with structured extract (invoices, receipts, OTPs)
- → End-to-end log for every message in the principal audit
Plug.
Pay.
Connect a compatible MCP client to the per-agent endpoint. Available tools depend on permissions and configured resources; setup time is not guaranteed.
- → Tools: spend, refund, quote, balance, statement, contact
- → Capabilities map auto-injected into agent system prompt
- → Spend approvals streamed to principal via webhook + WhatsApp
- → Idempotent — agent retries are safe
Caps that travel
with the agent.
Supported spend-gated routes check per-transaction, daily and monthly caps and can require approval. Generic x402.pay_url has an optional per-call maximum, not the mandate-bound spend gate.
- → Spend caps · MCC blocks · geofences · merchant allowlists
- → Tap-to-approve via WhatsApp / iOS push for spend ≥ threshold
- → Use supported card controls and review their provider-specific enforcement
- → One-click freeze · resumable from same wallet ID