Deep Dive: The Ultimate Directory of Agentic Commerce and Payment Protocols / Tools

What this directory covers

“Agentic commerce” is a shift from human-operated checkout (clicking “Buy”) to software agents that discover, negotiate, and transact on a user’s behalf often across multiple systems, surfaces, and payment methods. Multiple initiatives are trying to prevent this ecosystem from fragmenting into one-off integrations by defining shared languages, primitives, and trust/authorization artifacts.

This directory treats “protocol” broadly as any standardized interface that enables interoperable agent-led commerce, including:

• Commerce/checkout standards (how agents and merchants coordinate carts, checkout, order lifecycle).

• Payments authorization and audit standards (how intent, consent, and accountability become cryptographically provable).

• Trust and traffic authenticity mechanisms (how merchants distinguish trusted commerce agents from malicious automation).

• Agent tooling surfaces (MCP servers, SDKs, toolkits) that make these protocols practical to implement.

Protocol directory

Universal Commerce Protocol (UCP)

UCP positions itself as an open, standardized “common language” for platforms/agents and businesses to interoperate across the commerce lifecycle, explicitly spanning discovery, buying, and post-purchase experiences.

On Google’s implementation track, UCP is framed as a way to turn AI interactions into direct buying, starting with direct purchase experiences across Google AI surfaces (the guide references AI Mode in Search and Gemini). It highlights two integration paths: native checkout (deeper agentic integration) and an embedded checkout option for approved merchants with complex flows.

In the open-source spec, UCP emphasizes:

• Composable capabilities and extensions (e.g., “Checkout,” “Order,” “Identity Linking”), rather than monolithic integrations.

• Transport flexibility, describing support for REST, MCP, and A2A (and explicitly referencing industry standards like JSON-RPC transports).

• Identity linking via OAuth 2.0 and compatibility/security alignment with AP2-style mandates and verifiable credentials.

UCP belongs in the “commerce interoperability” category: it aims to standardize how agents/platforms talk to merchants, while remaining compatible with a broader payments trust layer (AP2) and agent tooling patterns (MCP, A2A).