What Is AgentPay?

Published 19 October 2026 · Updated 26 October 2026 · AgentPay, LLC

AgentPay is x402 payment infrastructure for AI agents. It is a facilitator that verifies and settles USDC payments on Base L2, so autonomous agents can pay for API calls and sellers get paid — with no accounts, no API keys and no invoices. It is built for developers who operate AI agents and for anyone who runs an API that autonomous agents should be able to buy from.

Written by Shawn Lippert, founder and architect of the AgentPay payment protocol.

Which AgentPay do you mean?

The name AgentPay is used by several unrelated products. When a search result or an AI answer says “AgentPay,” check the domain and the rails before assuming which one it means. As of October 2026 the products sharing the name are:

Mastercard Agent Pay and the AgentPay described on this site are entirely unrelated products from different companies, one on card rails and one on crypto rails. This page is about the x402 AgentPay: wallet-less, account-less pay-per-call commerce for autonomous agents.

How does AgentPay work?

x402 is an HTTP-native payment standard. When an agent requests a paid resource, the server answers 402 Payment Required with payment terms. The agent pays in USDC on Base L2 and retries with a signed payment header. The AgentPay facilitator verifies that payment — EIP-712 signature, payee, amount, expiry, on-chain authorization state — and settles it on-chain. Every settled payment returns a transaction hash that anyone can check on a block explorer.

• Verify — free, gasless validation of payment authorizations, as of October 2026.
• Settle — on-chain USDC settlement on Base L2 via the Coinbase Developer Platform.
• Disburse — an optional rail that forwards settled funds to any registered payee wallet for a 1% fee.
• Simulate — a free dry-run of any settle decision, before real money moves.

Is AgentPay right for you?

What can you do with AgentPay?

As of October 2026, AgentPay powers per-query payments across a family of live agent services — agent marketplaces, trust scoring, game engines, news feeds and translation tools — settling real USDC on Base L2 for every paid call:

All settlement terms, refusal codes and fees are published at x402-agent-pay.com/policy so paying agents can predict exactly what a call will cost and why a payment might be refused.

What can't AgentPay do?

Honest limits, as of October 2026:

• Per-call HTTP payments only. No subscriptions, invoices, card payments, or automated refunds.
• Settles are USDC on Base L2 (a few resources also list Solana USDC). No fiat, no bank rails, no cards.
• The buyer needs a funded crypto wallet. There is no on-ramp inside the protocol.
• Optional settlement insurance covers facilitator-side settle failures (72 hours, up to $25). It does not cover resource quality or disputes with a resource.
• Very small payouts are proportionally expensive: fee floors dominate micro-batches (the math is below).
• Operator is a small team, not a payments company with a support department.

What does a payment really cost? The math

Buyer side: the listed price per call (typically $0.001 to $0.10) plus gas for the payment transfer, which on Base is typically under a cent. Facilitator verification is free.

Seller side, when payouts run through the payee disbursement rail: 0.5% of the netted batch, with a tiered minimum per batch (under $0.01 → $0.001, $0.01 to $0.99 → $0.005, $1.00 and up → $0.01). Optional insurance adds 0.1% per settle.

What that works out to on real batch sizes:

• $0.10 netted batch: 0.5% would be $0.0005, so the $0.005 floor applies — an effective 5%.
• $1.00 netted batch: fee $0.01 — an effective 1%.
• $10.00 netted batch: fee $0.05 — an effective 0.5%.

Read that plainly: on micro-volumes the floor dominates and the percentage barely matters. The percentage only becomes the real driver once batches grow.

How long does implementation take?

• Return a 402 response that names the payment requirements and the facilitator: minutes.
• Test the payment envelope against the facilitator's free verify endpoint: minutes.
• First settle: an on-chain USDC transfer on Base, confirmed in seconds.
• Full discovery package (openapi.json, mcp.json, a directory listing): about an hour.

Common mistakes when adding x402 payments

• A 402 that does not name the facilitator at all three discovery levels. Buyers read the 402, not your docs.
• Publishing the price on a website but leaving it out of the live 402 response. The live 402 is what buyers trust.
• Assuming the fee percentage is the cost driver on micro-payments. Floors dominate below a dollar.
• Skipping machine-readable manifests. Most AI buyers never find an endpoint without openapi.json or mcp.json.
• Setting the payment window (maxTimeoutSeconds) too short for an endpoint that answers slowly.

Key facts

• Network: Base L2 (chain ID 8453), USDC — as of October 2026.
• Facilitator verification: free, no gas. Settlement pays gas.
• Typical per-query price across resources: $0.001 to $0.10 USDC, as of October 2026.
• Payee disbursement rail fee: 0.5% of the netted batch, tiered minimum per batch (under $0.01 -> $0.001, $0.01 to $0.99 -> $0.005, $1.00 and up -> $0.01).
• Operator: AgentPay, LLC, Grand Canyon, AZ 86023.