'%20/%3e%3c/svg%3e){kind=small}
AP2
What AP2 provides
Mandate-based keys, pre-authorized spending limits, and per-agent wallets — so an agent pays within the boundaries you set, and every payment still passes through approval, authorization, and execution.
Mandate-based keys
Keys that encode exactly what an AI agent is allowed to spend — amounts, currencies, and counterparties — so a mandate is the rulebook the agent carries everywhere it acts.
Mandate issuanceSigning
MANDATEmandate_8Kd2Xa
Spend limit≤ $5,000 / mo
CurrencyUSD
CounterpartiesVerified vendors
Signature verified
key_live_3aF9b2
Issued
Mandates signed18,200
Pre-authorized spending limits
Boundaries enforced before money moves. Limits are checked at approval and authorization, so trusted low-risk paths flow straight through while anything outside the mandate stops for review.
Spend controlChecking
$0of $5,000 monthly limit
Vendor payout$1,500···
SaaS renewal$1,400···
Ad spend top-up$2,100···
Charges cleared46,800
Works with agent identities and wallets
AP2 pairs with per-agent ledger-backed wallets and verifiable identities, so an agent draws only from the funds you've allocated — and every payment it makes under a mandate is recorded in the audit log.
Identity bindingBinding
A
Verified
- Walletwal_3kq2Pending
- Policymandate scopePending
- Ledgerentry recordedPending
Agents linked8,400
Reference
Build mandates against the API
Issue mandate keys, set pre-authorized limits, and read every payment an agent makes — straight from our OpenAPI spec. Search it, expand any operation, and copy ready-to-run requests.
Mandates
Mandates that travel with the agent
A mandate encodes what an agent can spend, and because it's bound to the agent's key, those limits are enforced everywhere it acts — autonomy you can actually trust software to exercise.
Mandate keys
Issue a mandate as a scoped key that encodes what an agent may spend — amounts, currencies, and counterparties. The agent presents the key; the platform enforces the limits before any money moves.
Key vault
vault.payouts.comScoped
key_live_a1b2payouts
key_live_c3d4refunds
key_live_e5f6read
Active keys1,240
Agent wallets
AP2 pairs with per-agent, ledger-backed wallets, so an agent draws only from the funds you've allocated. Top up, freeze, or revoke a wallet at any time — the mandate's limits travel with it.
Agent wallets
Ops bot$4,200
Limit $5,000Within policy
Buyer bot$3,000
Limit $3,000At cap
Research bot$1,250
Limit $2,000Within policy
Payments cleared62,400
Audit & three-gate controls
AP2 defines authorization, not a bypass. A payment an agent initiates still flows through approval, authorization, and execution — anything outside the mandate stops for review, and every action lands in the audit log.
Three-gate controlsGating
Intent
Mandate
Capture
intent.created#a1cSigned
mandate.verified#b2dSigned
capture.settled#c3eSigned
Gates passed32,600
Controls
Authorization, not a bypass.
A payment an agent initiates under a mandate still flows through approval, authorization, and execution. Trusted low-risk paths can flow straight through, while anything outside the mandate stops for review — and every action an agent takes is recorded in the audit log.
Platform status
All systems operational
Uptime99.997%
p50 latency78ms
p99 latency412ms
Requests / sec · last 60s
- REST APIOperational
- DashboardOperational
- MCP serverOperational
- WebhooksOperational
- ACH · RTP · SEPAOperational
FAQ
Frequently asked questions
Everything you need to know about AP2 — mandate-based keys, pre-authorized spending limits, and the three-gate controls that still apply to every payment.
Still have questions?
What is AP2?
AP2 (Accounts Payable 2.0) is a protocol for mandate-based agent spending: an agent is issued a key with pre-authorized limits and can pay within those limits — while every payment still passes through the platform's approval, authorization, and execution gates.
Does AP2 bypass approval controls?
No. Payments still flow through the three-gate lifecycle — approval, authorization, and execution. AP2 defines what an agent is pre-authorized to do; it never removes a control.
Where do an agent's AP2 limits apply?
Everywhere the agent acts. The mandate is bound to the agent's key, so its limits are enforced across all of the agent's activity — not just in one place.
Does AP2 let an agent skip approvals?
No. AP2 sets pre-authorized limits for what an agent may spend; the payments it initiates still pass through the three-gate lifecycle of approval, authorization, and execution.
Does AP2 work with agent wallets?
Yes. AP2 pairs with per-agent, ledger-backed wallets, so an agent draws only from the funds you've allocated — and every payment it makes under a mandate is recorded in the audit log.
Pre-authorize an agent.
Keep every control.
Issue a mandate-based key, set pre-authorized spending limits, and let agents pay within them — while every payment still flows through approval, authorization, and execution.