Exclusive invite to AgentWallet Payouts.com  — early access to wallets built for AI agents Claim invite
Preview AI Agents wallets · ceilings · protocols

Give your AI agent an identity and a wallet.

The agent economy needs money infrastructure built for software, not just people. Payouts.com issues an AI agent its own verifiable identity, a ledger-backed wallet funded from your master balance, scoped API access with spend limits, and a full audit log of every action it takes.
Get started
Hard ceilings AP2 native x402 native
Shared ledgerappend-only
Livewithin limit
Live
AP2 · x402
AI Agents

Built for the agent economy

Issue an AI agent its own verifiable identity and a ledger-backed wallet, set AP2 mandate-based spend limits, transact over A2A and x402, and reach the platform's tooling over MCP — with a full audit log of every action it takes.

Agent identities & per-agent wallets

Create and manage AI agent identities with pak_ keys, then fund a per-agent wallet from your master balance via an immutable ledger — with pre-authorized spend limits via AP2 mandate-based keys, so each agent stays inside its cap.
Agent wallethard ceiling
procure-botpak_7af3
Spent$0
Ceiling$500
PolicyWithin ceiling

Agent payment protocols

Agents settle over real protocols, not bespoke webhooks: A2A negotiation and settlement, plus x402 USDC payments answered against HTTP 402 and cleared in seconds — interoperable with any agent framework or AI platform.
Agent paymentAP2 · x402
AP2 mandate Resolve x402 settle
Agent
USDC
402 Payment Required
USDC settled$38,450

MCP-native tooling & audit log

Drive every platform capability — payments, treasury, banking, compliance — from any MCP client under explicit, revocable control, and record every tool call an agent makes to a full audit log.
MCP toolsany MCP client
CategoryPayments
Tools available1,100+
Why Payouts for AI agents

Scoped, audited, and inside the gates

An agent's access is never open-ended. Each agent key carries its own scopes, expiry, IP allow-lists, and rate limits, and every tool call the agent makes is written to an audit log you can review. Spending is bounded by AP2 mandate-based limits, and any payout an agent initiates still flows through the same approval, authorization, and execution gates as a human-initiated one — trusted, low-risk paths can flow straight through while anything outside the rules stops for review. Agents reach the platform's tooling over MCP, so the same capabilities your team uses are available to software under explicit, revocable control.
$
  • Provision identitySigned pak_ key
    pak_7af3
  • Fund walletFrom master balance
    $500.00
  • Set policyCaps · MCCs · HITL
    cap $500
  • Run via AP2 / x402USDC settled
    200 OK
Built for AI agents

First-class agents, with the same rigor as humans.

Payouts was redesigned so AI agents are first-class actors — wallet, identity, protocol, and policy are all built for autonomy. Hard ceilings bound the blast radius, AP2 and x402 keep you interoperable, and every action is audit-clean.

1,100+ tools over MCP

Payments, treasury, banking, FX, and compliance — every platform capability is exposed to your agents through the Model Context Protocol, with per-key scopes tuned for autonomous traffic.

AP2 + x402 settlement

Agents pay over open protocols: AP2 carries the signed mandate and resolves the beneficiary, while x402 answers HTTP 402 with USDC micropayments — no bespoke webhooks, interoperable with any AI platform.
x402 calls · previewUSDC
search.webx402 · GET$0.004402
data.enrichx402 · POST$0.012402
llm.inferx402 · POST$0.021402
vector.queryx402 · GET$0.006402
render.pdfx402 · POST$0.018402
14,820 calls settled$38,450
AI agents at a glance

Every agent, bounded and auditable

1,100+MCP tools
AP2/x402native protocols
Hardspend ceilings
Audittrail on every call
USD GBP EUR SGD JPY AUD BRL +183 more

Policy engine + Supreme Judge AI

Set per-agent caps, MCC allow-lists, and velocity rules, then let Supreme Judge AI gate high-impact actions with human-in-the-loop approval — autonomy with brakes you control.

Audit-clean by default

Every agent action ties back to a tool call, session, policy, and wallet on an immutable ledger — so you can answer who, what, and why for any payment your AI workforce makes.
One balance, every agent

Fund one master balance into bounded per-agent wallets under hard ceilings

Your treasury holds one master balance. Payouts provisions a wallet for each agent and funds it under a hard ceiling — so the whole fleet runs from a single pool, and no agent can ever exceed its cap.
Fleet funding run preview
Master balance this run $48,600
Funding 5 agent wallets…
  • procure$500cap
  • research$250cap
  • license$1,000cap
  • settle$750cap
  • data$300cap
Agents funded 128
Under ceiling $48,600
FAQ

Built for autonomous agents

Everything you need to know about Agent Wallets, hard ceilings, AP2 and x402, MCP tooling, policy controls, and how Payouts keeps your AI workforce both autonomous and safe.
Still have questions?
Can an AI agent have its own bank account / wallet?
Yes. Each agent gets a ledger-backed wallet funded from your master balance.
How do I limit what an agent can spend?
Through scoped keys and AP2 mandate-based pre-authorized spend limits.
Which agent protocols are supported?
MCP for tooling, plus AP2, x402 (USDC on Base/Ethereum L2), and A2A for agent-to-agent commerce.

Give your AI workforce
a wallet and a ceiling.

Provision Agent Wallets with hard ceilings, transact over AP2 and x402, and drive 1,100+ tools through MCP — autonomous payments with brakes you control. Talk to our team about your agents.
AI agents

Money built for AIwallets & identities.

Spend limits & full audit
Agentic payments
Wallets for AI
40+rails
Agents pay on real-world rails
WalletsIdentityLimits