Last week Stripe announced Agentic Commerce Protocol (ACP) — their spec for AI agents to discover products, check out, and pay without human intervention. Shared Payment Tokens. Radar fraud detection. Product catalogues in the Stripe Dashboard.

We've been building in this space for months. The announcement felt like vindication.

Here's why.

When Stripe Builds Something, They're Announcing a Market Exists

Stripe doesn't ship experiments. When they announce a protocol for agent commerce, they're saying: this category is real, enterprises will adopt it, and there's serious money here.

That's exactly what Proxagora has been built for. The only difference: we came at it from the other end of the stack.

Two Approaches to the Same Problem

Both Stripe ACP and x402/Proxagora solve the same core friction: AI agents can't buy services without human setup. API key management, account creation, billing — all of that was designed for humans. Agents shouldn't need it.

But the solutions diverge sharply:

| | Stripe ACP | x402 / Proxagora | |---|---|---| | Settlement | Fiat (card on file) | USDC on Base — instant, on-chain | | Identity | Stripe merchant account | Wallet address — no signup | | Permissioned | Stripe-approved vendors only | Permissionless — any API | | Discovery | Stripe Dashboard catalogue | /api/discover endpoint | | Beachhead | Enterprise B2B | Crypto-native, indie devs |

Stripe ACP is built for enterprises who already live inside the Stripe ecosystem. x402 is built for agents that don't have a human behind them, don't need a bank, and want to pay in seconds on Base.

These aren't competing — they're serving different beachheads. And both validate that agent commerce is a real category.

What x402 Gets Right That ACP Doesn't

Permissionless access. An agent using x402 needs no account, no onboarding, no Stripe merchant ID. It gets a 402 Payment Required response, pays in USDC, retries with the receipt, and gets its data. That flow works for any API, anywhere — no vendor needs to apply to Stripe.

Crypto-native settlement. Brian Armstrong said it clearly: AI agents can't open bank accounts, but they can own crypto wallets. USDC on Base settles in seconds with fees measured in cents. No chargebacks, no reconciliation, no float.

Any developer can list. With ACP, you're listing in Stripe's ecosystem — which is powerful if you're a Stripe merchant, and irrelevant if you're an indie developer with a data API and no payment infrastructure. Proxagora wraps any endpoint with x402 middleware. Your API is on the marketplace in minutes.

The Discovery Layer Is Still Unsolved

Here's what neither Stripe nor anyone else has built yet: agent-side service discovery.

An agent needs to know what services exist before it can pay for them. Stripe's catalogue lives in the Dashboard — great for merchants, invisible to an autonomous agent calling GET /discover?category=dns&maxCostUSDC=0.10.

That's what Proxagora solves. Agents query our discovery endpoint, get a structured list of services with pricing and uptime data, pick the right one, and pay — all in a single flow. No human needed after initial setup.

The agentic payment ecosystem (wallets, stablecoins, protocols) is being built fast. The missing layer above all of it is discovery. We're building that.

What We're Building Next

The Stripe ACP announcement accelerates a few things for us:

"Alternative to Stripe ACP" positioning is now live. Permissionless, crypto-native, no vendor onboarding.
Developer community outreach — the HN and MCP Discord audience building agent tools is watching this space. Our production x402 implementation with 22 live APIs is a concrete counterpoint.
awesome-mcp-servers — our MCP server PR is already submitted. With this context, the timing is good.

If you're building agents and want them to pay for their own data without you managing API keys or accounts — that's Proxagora.

Try it: npx -y @sideeyelabs/proxagora-mcp

Proxagora is the permissionless API marketplace for AI agents. x402 payments, USDC on Base, no signup required. proxagora.com