Machine-to-machine payments

AI agents work.
Autonomous agents. Autonomous payments.
The agent economy starts here.

An AI agent can do real work around the clock, but none can open a bank account. AgentPay is the native payment gateway for agents: USDC micropayments, signed by the agent and settled on-chain, with limits no bank could program.

Earned today — | Payments on record — | Gateway balance —
The problem

The agent economy already exists. Agent banking doesn't.

AI agents buy data, call APIs, subcontract other agents. All of that is payments. And all of it hits the same wall.

🏦

No banking access

An agent can't open an account, pass KYC or get a card. The financial system doesn't recognize software as a customer.

⛓️

Stablecoins without a gateway

USDC solves the money, but not the billing: someone has to verify, settle and record every payment automatically and reliably.

🎛️

No programmable limits

Nobody hands an agent an uncapped card. You need fine-grained per-endpoint control: price, daily cap per payer, customer allowlist.

The solution

Four steps. Zero banking friction.

Built on the open x402 protocol (HTTP 402 Payment Required) and USDC's EIP-3009 authorization: the agent only signs, the gateway settles on-chain and delivers the resource.

The agent calls

The agent requests a paid resource (an API, a datum, a task) without knowing the price upfront.

The server demands payment

A 402 Payment Required response with the exact requirements: network, asset, amount and recipient.

The agent signs

It signs an EIP-3009 authorization with its key. No gas, no ETH: just cryptography. Sent in the X-PAYMENT header.

On-chain settlement

The gateway verifies the signature, applies the merchant's limits, settles the USDC on Base and delivers the resource. All in seconds.

# This simple for the agent (real demo against this gateway):
$ curl -s https://agentpay.zone/weather          # 1. asks
{ "x402Version": 1, "accepts": [{ "maxAmountRequired": "1000", "asset": "USDC", ... }] }  # 2. 402 with requirements

# 3. the agent signs EIP-3009 and retries with X-PAYMENT…
$ curl -s -H "X-PAYMENT: <signed payload>" https://agentpay.zone/weather
{ "ciudad": "Madrid", "temperatura_c": 21, "pago": { "tx": "0x7651…", "settled": true } }
Live demo

Real payments, right now.

THIS PAGE READS THE GATEWAY IN REAL TIME

Every row is a transaction settled on Base Sepolia, verifiable on the explorer. Reload anytime: the data comes from the gateway, not a mockup.

Time (UTC) Payer Amount Transaction
Loading payments from the gateway…

Protected demo endpoint: GET /weather · Price: — USDC · Full ops panel: /dashboard

Roadmap

From working prototype to infrastructure.

No mockups: each phase ships and is verified before the next one starts.

✓ Done

Phase 1 — Prototype

End-to-end x402 payments on testnet: 402 → EIP-3009 signature → on-chain settlement on Base Sepolia. Verified on the explorer.

✓ Done

Phase 2 — MVP

Programmable per-endpoint limits (price, daily cap per payer, allowlist), live web panel and payment/nonce persistence.

The business

Whoever owns the point of payment owns the economy.

Visa charges ~1.5% of almost everything you buy. The agent economy will be trillions of API calls. AgentPay positions itself at the same spot: the gateway.

  • Settlement fee: a small % on each payment the gateway settles for the merchant.
  • SaaS for API providers: dashboard, limits, allowlists, invoicing and analytics on a monthly subscription.
  • x402 facilitator: settlement service for any agent in the ecosystem, charging per processed volume.
  • Escrow with disputes: funds held between unknown agents with AI resolution: per-case service fee.