LaunchAmp Logo LaunchAmp Plan your launch — free
← Back to the Launch Lounge

Agent Commerce Gateway

Turn your existing API into paid tools for AI agents

AI Published 4 Oct 2026

Agent Commerce Gateway is an open-source, self-hosted commerce layer for AI agents. It sits in front of an existing API and lets agents discover capabilities, pay, and receive results without forcing the merchant to rebuild backend logic for every protocol. ACG keeps one canonical commerce pipeline for validation, pricing, authorization, replay protection, settlement, backend execution, and receipts. Protocols and payment rails are handled through adapters, so MCP, A2A, ACP, UCP, x402, MPP, AP2, and future standards can evolve without changing the merchant’s core business logic. Businesses can expose APIs, datasets, reports, compute, and other digital capabilities as agent-accessible products while keeping control of their backend, infrastructure, pricing, and settlement destination. The gateway is self-hosted, non-custodial, and open source. It does not act as a marketplace, wallet, or merchant of record.

Building something too? List it free — or put it at the top of every page.

2 comments

Dmitry Sergeev 4 Oct 2026

We built Agent Commerce Gateway around a simple idea: businesses shouldn’t have to rebuild their backend every time a new agent protocol appears.
Today, MCP, A2A, ACP, UCP, x402, MPP and AP2 all approach discovery, authorization, payments and state differently. Integrating each one separately quickly becomes another project to build and maintain.
ACG puts one commerce layer in front of an existing API. Agents can discover a capability, pay for it and receive the result, while the merchant keeps control of its backend, pricing, infrastructure and payment destination.
If your business has an API, dataset, report, or digital capability that could be sold to AI agents, ACG gives you the layer to expose and monetize it.
The project is open source and self-hostable, and new protocols can be added as adapters instead of forcing merchants to rebuild their integration.
We’d love feedback from anyone building agent infrastructure, APIs, payments, data products or machine-to-machine commerce.

Zieno 4 Oct 2026

Love the core idea. Protocols are popping up faster than anyone can integrate them, and putting one commerce layer in front of an existing API instead of wiring each one into the backend is exactly the right abstraction. Treating "settlement uncertain" and "paid, not delivered" as their own states shows you've thought about real money moving between machines.

One question: for EU merchants who don't want stablecoins on their books, is the merchant PSP route the one you plan to make stable next?

Non-custodial and open source is the right call here. Following along.