The payment API built around agents.
Agents, principals, allocations, cards, payouts and approvals are first-class resources. Your backend uses REST; your agents use MCP; your systems get signed webhooks.
AgentWallet is invite-only. Request access and we will follow up.
An agent payment API lets software create and govern agents that can spend. AgentWallet exposes REST endpoints under /api, MCP servers for agents and owners, OpenAI-compatible tool endpoints, OAuth for MCP clients and HMAC-signed webhooks.
Integrate in five steps.
Get a key
Create a
pak_API key in the dashboard for agent-facing endpoints.Model your org
Create principals and agents.
Fund and limit
Allocate budgets and set caps and card policy.
Connect the agent
Point your agent at its MCP endpoint, or call OpenAI tool endpoints.
Listen
Register a webhook endpoint and verify signatures.
API surface
Resources
Accounts, principals, agents, resources, ledger, approvals, payouts, webhooks.
Agent and owner servers
/mcp/agent and /mcp/owner, discoverable via /.well-known/mcp.json.
Tool calling
/api/openai-tools/tools and /api/openai-tools/call.
Sessions, keys and OAuth
Management endpoints use the dashboard session; agent endpoints use pak_ keys; MCP clients can use OAuth 2.0 with device flow and dynamic client registration.
Idempotency
Idempotency-Key on payment routes.
Webhooks
Signed, retried with backoff, dead-lettered, redeliverable.
Who integrates the API
Agent framework builders
Add a pay tool to every agent created in your framework.
SaaS with AI features
Let in-product agents buy on behalf of customers within plan limits.
Finance and ops teams
Automate payouts with approvals wired into existing tools.
Agent-to-agent protocols
Use A2A tasks, AP2 mandates and x402 for machine commerce.
Verify every webhook.
Deliveries include event ID, type and a timestamped HMAC signature.
- Headers:
X-Payouts-Signature,X-Payouts-Event-Id,X-Payouts-Event-Type - Events include
purchase.succeeded,purchase.failed,purchase.confirmed - Inspect with
GET /api/webhook-endpoints/:id/deliveries - Redeliver with
POST /api/webhook-deliveries/:id/redeliver
# Register a webhook endpoint (dashboard session) curl -X POST https://agentwallet.ai/api/webhook-endpoints \ -H "Content-Type: application/json" \ -d '{"url":"https://example.com/hooks/aw", "eventTypes":"purchase.succeeded,purchase.failed"}' # Verify: X-Payouts-Signature: t=…,v1=… # v1 = HMAC-SHA256(secret, t + "." + body)
Secure by construction.
Hashed keys
Only a hash of each API key is stored.
Scoped MCP
Agent MCP access is scoped to one agent.
Signed events
Timestamped signatures resist replay.
Policy enforced server-side
Gated payment tools run limit checks; the generic x402.pay_url tool only honours maxAmountAtomic.
Questions developers ask
What is an agent payment API?
An API for creating AI agents that can hold and spend money, with limits, approvals and events built in.
Is there an OpenAPI spec?
Yes, published at /openapi.json.
Does it work with Claude, Cursor or OpenAI?
Agents can connect via MCP, and OpenAI-style tool calling is available through dedicated endpoints.
Who can use AgentWallet today?
Access is invite-only while we onboard teams. Request access from any page; sign-up is enabled per email or domain once you are approved.
Do you guarantee availability in my country or a specific settlement time?
No. Supported rails, currencies and timing depend on the underlying banking, card and payout partners for your account. We confirm what is available for your account during onboarding rather than promising it upfront.
AI agent financial infrastructure
Every page in this set covers one layer. Start at the hub for the full map.