Agent Commerce Gateway icon
Agent Commerce Gateway icon

Agent Commerce Gateway

Self-hosted, non-custodial gateway between the API you already run and the protocols AI agents use to discover, call and pay for it.

Agent Commerce Gateway screenshot 1

Cost / License

Platforms

  • Self-Hosted
  • Docker
Agent Commerce Gateway screenshot 1
Agent Commerce Gateway screenshot 2
+2
Agent Commerce Gateway screenshot 3
Alternatives  
0likes
1alternative
0articles
Save

Features

Properties

  1.  WEB3

No features, maybe you want to suggest one?

 Tags

Agent Commerce Gateway News & Activities

Highlights All activities

Recent activities

Agent Commerce Gateway information

GitHub repository

  •  32 Stars
  •  1 Forks
  •  4 Open Issues
  •   Updated  
View on GitHub

Popular alternatives

View all
Agent Commerce Gateway was added to AlternativeTo by Dmitry Sergeev on and this page was last updated .

No comments or reviews, maybe you want to be first?

Official Links

AppStores & Other Links

What is Agent Commerce Gateway?

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.

ACG also includes Doctor, a diagnostic layer that checks configuration, storage, payment routes, dependencies, and exposed capabilities before going live.

Key ideas: one backend integration, multiple agent protocols, merchant-controlled settlement, replay protection and receipts, protocol and payment adapters, self-hosted deployment, open-source architecture.