Build agents that
actually transact.

The per-agent MCP server.

Each agent has its own MCP endpoint at /mcp/agent, scoped to one row in agent_identities. Drop the URL and the agent's pak_… key into any MCP-compatible client and the agent is online — wallet, card, channels, AP2 signing, x402, all surfaced as tools.

Bootstrap an MCP client

Drop the URL + key into any MCP-compatible client (any LLM client, coding agent, or your own host). The server auto-advertises its tool catalog via JSON-RPC tools/list:

{"mcpServers": {"agentwallet": {"url": "https://api.agentwallet.ai/mcp/agent","headers": {"Authorization": "Bearer pak_live_a1f9c2…"}}}}

Tool call shape

// Request{"jsonrpc": "2.0", "id": 42,"method": "tools/call","params": {"name": "wallet.send_payment","arguments": {"recipient_handle": "[email protected]","amount_cents": 12500,"currency": "USD","memo": "Invoice #INV-208"}}}// Response — auto-approved (under per-txn cap){"jsonrpc": "2.0", "id": 42,"result": {"content": [{ "type": "text","text": "Sent $125.00 USD via ACH. ref=pay_01J…" }],"isError": false}}

Per-agent tool catalog

Three external rails. One mandate per payment.

Outbound payments leave through one of three protocol stacks. The choice is decided by the merchant's capability advertisement (or by the rail the agent's policy permits).

x402 over EIP-3009

The merchant returns HTTP 402 Payment Required with a payment offer. The agent signs an EIP-3009 transferWithAuthorization (USDC on Base) for the offered amount and replays the request with the signed authorization in the X-PAYMENT header.

// 1. Agent's first requestGET /api/dataset/v1 HTTP/1.1 Host: data.example Authorization: Bearer pak_…// 2. Merchant returns 402 with offerHTTP/1.1 402 Payment Required Content-Type: application/json{"x402": {"amount": "0.10", "currency": "USDC","network": "base","recipient": "0xabc…","validBefore": 1746349200}}// 3. Agent signs EIP-3009 (CDP-managed key) and replaysGET /api/dataset/v1 HTTP/1.1 Host: data.example X-PAYMENT: eyJ0eXAiOiJ4NDAyIiwiYWxnIjoi… // signed auth

Shared Payment Tokens (SPT)

For card-rail payments to merchants that accept network-issued single-use tokens. The agent requests an SPT, scoped to a single use and to a specific merchant + amount. The token expires; replay is structurally impossible.

const spt = await issuer.paymentTokens.create({type: 'card', card: { vault_alias: card.vaultAlias }, single_use: true, restrictions: {amount: cartTotalCents, merchant: merchantId, expires_at: Math.floor(Date.now() / 1000) + 300}});// Persist for auditawait db.insert(acpSptIssuances).values({agentIdentityId, tokenId: spt.id, cartMandateId, amountCents: cartTotalCents});

PCI-vaulted card tokens — when the merchant only takes a PAN

For merchants without modern token APIs, the agent gets a vault-tokenized card alias that the outbound proxy substitutes back to a real PAN at the network edge. The agent never sees the PAN; the application server never holds it.

Discovery · /.well-known/agent.json

The ACP standard defines how an agent publishes its capabilities, rails, and AP2 public keys. Merchants and counterparty agents fetch this before transacting.

{"agent_id": "did:agentwallet:ag_01J9…","name": "Acme Procurement Agent","public_keys": [{ "kid": "ag_01J9…#k1", "alg": "ES256","jwk": { "kty": "EC", "crv": "P-256", "x": "…", "y": "…" }}],"endpoints": {"ap2_inbound": "https://agent.acme.example/ap2/v1/payment","a2a": "https://agent.acme.example/a2a/v1"},"accepts": ["x402_usdc_base", "spt", "ach"],"erc8004": { "chainId": 8453, "tokenId": "42" }}

Portal API & Auth.

The frontend dashboard is driven entirely by the /api/agent-portal router. It is RBAC-gated and distinct from the MCP and Admin endpoints.

Agent Portal API Endpoints

Auth flow: Magic-link OTP

We removed passwords in v0.4.4. Principals authenticate via a 6-digit code sent to their email.

• Request. Principal submits email. Server generates 6-digit code, hashes it, stores in agent_portal_otps, sends email.
• Verify. Principal submits code. Server hashes, compares, issues 30-day HttpOnly sliding cookie.
• Session. Row in agent_portal_sessions tracks device, IP, last seen. Revocable.