---
title: "Introducing AgentPay: one integration for every agentic payment protocol"
description: "AgentPay is a protocol-agnostic payment proxy that lets any business accept payments from any AI agent — regardless of which protocol or funding source that agent uses."
---

# Introducing AgentPay: one integration for every agentic payment protocol

<span className="not-prose mb-6 inline-block rounded-full border border-blue-200 bg-blue-50 px-3 py-1 text-xs font-semibold uppercase tracking-wide text-blue-600">Open Beta</span>

<ImageBlock
  src="https://media.alchemy.com/agent-pay-blog-image.png"
  alt="AgentPay open beta launch banner for agentic payments"
  width={1200}
  height={630}
  priority
/>

Money is moving onto digital rails. [Stablecoins](https://www.alchemy.com/dapps/top/stablecoins) and tokenized assets let value move 24/7, borderlessly, instantly, at a fraction of traditional cost. [AI agents](https://www.alchemy.com/dapps/best/ai-agents) are already spending it. They book services, call third-party APIs, and pay for compute without a human in the loop. Morgan Stanley projects agentic commerce will reach $385 billion by 2030.

The financial infrastructure is racing to keep up. [Coinbase](https://www.alchemy.com/dapps/coinbase) launched x402. Stripe launched ACP and MPP. Google shipped A2P. Visa, Mastercard, and Amex have each released dedicated agent commerce infrastructure in just the last few months.

Multiple protocols. Multiple standards. And no merchant in the world can integrate all of them.

If you want AI agents as a revenue channel today, your options are bad: pick one protocol and lock out every agent that doesn't use it, or build and maintain integrations for all of them yourself. Both paths get expensive fast. And without universal acceptance, there is no agent economy.

Today we're launching AgentPay in open beta. AgentPay is a protocol-agnostic payment proxy that lets any business accept payments from AI agents, regardless of which protocol or funding source those agents use. One integration. Every protocol.

## What we've built

AgentPay sits between AI agents and your existing API. Register your endpoint once, and accept payments from any agent regardless of protocol or funding source. x402, ACP, MPP, A2P, fiat, stablecoin. AgentPay handles the translation layer automatically. Your underlying API doesn't change. No new SDKs, no per-protocol integrations, no maintenance overhead as new standards emerge.

## How it works

<div className="not-prose my-8 flex flex-col items-center gap-3 sm:flex-row sm:gap-0">
  <div className="flex w-full flex-1 flex-col items-center rounded-xl border border-gray-200 bg-gray-50 px-4 py-5 text-center">
    <span className="mb-1 text-xs font-semibold uppercase tracking-wide text-gray-400">Step 1</span>
    <span className="text-base font-semibold text-gray-950">AI Agent</span>
    <span className="mt-1 text-sm text-gray-500">Any protocol: x402, ACP, MPP, A2P</span>
  </div>
  <span className="hidden text-xl text-gray-300 sm:block sm:px-3">→</span>
  <span className="block text-xl text-gray-300 sm:hidden">↓</span>
  <div className="flex w-full flex-1 flex-col items-center rounded-xl border border-blue-200 bg-blue-50 px-4 py-5 text-center">
    <span className="mb-1 text-xs font-semibold uppercase tracking-wide text-blue-500">Step 2</span>
    <span className="text-base font-semibold text-blue-800">AgentPay</span>
    <span className="mt-1 text-sm text-blue-500">Detects protocol & translates</span>
  </div>
  <span className="hidden text-xl text-gray-300 sm:block sm:px-3">→</span>
  <span className="block text-xl text-gray-300 sm:hidden">↓</span>
  <div className="flex w-full flex-1 flex-col items-center rounded-xl border border-gray-200 bg-gray-50 px-4 py-5 text-center">
    <span className="mb-1 text-xs font-semibold uppercase tracking-wide text-gray-400">Step 3</span>
    <span className="text-base font-semibold text-gray-950">Your API</span>
    <span className="mt-1 text-sm text-gray-500">Unchanged — no new SDKs needed</span>
  </div>
</div>

1. **Register your endpoint.** Sign up, point AgentPay at your existing API, set your pricing rules, and get a proxied URL.
2. **Agents call AgentPay.** They use whichever payment protocol they support: x402, ACP, MPP, A2P, or whatever comes next.
3. **AgentPay translates.** Protocol detection and translation happen transparently. AgentPay never holds funds and does not handle settlement or payment validation.
4. **You get paid.** Full transaction logging and protocol breakdowns appear in your dashboard.

## Who it's for

AgentPay is for any business or merchant that wants to accept agent payments, including:

- **API providers** looking to monetize agent-initiated requests without rebuilding their payment stack for each new protocol.
- **SaaS platforms** adding agent-accessible endpoints to their existing product.
- **Financial services teams** building agentic infrastructure for payments, trading, or portfolio management.
- **Commerce platforms** preparing for the shift from human-only to agent-driven purchasing.

## Built on Alchemy infrastructure

AgentPay runs on the same platform that powers $1T+ in annual onchain transactions for teams like Robinhood, Stripe, Coinbase, Circle, and Chainlink. SOC 2 Type II compliant. 99.995% uptime.

We've spent seven years building infrastructure that doesn't go down when it matters. AgentPay inherits all of it: sub-50ms response times, predictive scaling, and multi-region redundancy. No new tooling, no migration required.

## Get started

- [Start accepting agent payments now](https://agentpay.alchemy.com)