Agentic Commerce: Protocols, Standards, and Reference Architectures

The Future of AI-Powered Commerce

AGENTIC COMMERCE

Protocols, Standards, and Reference Architectures

for Agent-Based Commerce

Abstract

This comprehensive whitepaper provides developers with an in-depth guide to

the Agentic Commerce ecosystem. Discover how AI agents are revolutionizing

digital commerce through standardized protocols (UCP, AXP, A2A, ACP, AP2).

Learn implementation strategies, explore technical specifications, study real-

world API examples, and understand how to build the future of autonomous

commerce.

Author

Version & Date

Stefan Hamann

Co-CEO, Shopware

v1.0

Founding Member, Agentic Commerce Alliance

2026-01-14

www.agentic-commerce.dev

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

Contents

1 Introduction: The Dawn of Agentic Commerce 5

1.1 The Strategic Imperative for Developers . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 Overview of the Protocol Ecosystem . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Expanded Protocol Breakdown 8

2.1 UCP: Universal Commerce Protocol . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1.1 Co-Developers and Industry Adoption . . . . . . . . . . . . . . . . . . . . 9

2.1.2 Core Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1.3 Key Features and Capabilities . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1.4 Deployment Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.5 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.6 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.7 Performance Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.8 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.9 API Examples (Expanded) . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1.10 Implementation in Shopware . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.2 AXP: Agentic Experience Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2.1 Core Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2.2 UCP Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2.3 Product Data Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2.4 Quality Data Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2.5 Experience Embedding Capabilities . . . . . . . . . . . . . . . . . . . . . 15

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.2.6 Supported Transports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2.7 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.8 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.9 Performance Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.10 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.2.11 API Examples (Expanded) . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.2.12 Implementation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.3 A2A: Agent2Agent Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3.1 Why A2A? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3.2 Key Features and Capabilities (Expanded) . . . . . . . . . . . . . . . . . 19

2.3.3 Available SDKs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.4 Agent Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.5 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.6 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.7 Performance Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3.8 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3.9 API Examples (Expanded) . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3.10 Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.3.11 Implementation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.4 ACP: Agentic Commerce Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.4.1 Value Proposition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.4.2 Key Features and Capabilities (Expanded) . . . . . . . . . . . . . . . . . 23

2.4.3 Reference Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.4.4 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.4.5 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4.6 Performance Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4.7 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4.8 Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.4.9 Implementation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.5 AP2: Agent Payments Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.5.1 Key Features and Capabilities (Expanded) . . . . . . . . . . . . . . . . . 26

2.5.2 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.5.3 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.5.4 Performance Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.5.5 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.5.6 API Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.5.7 Implementation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6 PayPal Agentic Commerce & Store Sync . . . . . . . . . . . . . . . . . . . . . . . 28

2.6.1 Store Sync: The Core of PayPal’s Agentic Commerce . . . . . . . . . . . 28

2.6.2 Benefits for Merchants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.6.3 Strategic Partnerships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.6.4 Key Differentiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.6.5 Cart Orchestration API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.6.6 Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.6.7 System Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.6.8 Product Feed Integration Options . . . . . . . . . . . . . . . . . . . . . . . 31

2.6.9 API Example: Cart Creation . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.6.10 Protocol Collaborations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.6.11 Security & Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.6.12 Implementation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3 Industry Endorsements and Ecosystem 34

3.1 UCP Endorsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.2 ACP Partnerships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.3 A2A Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.4 PayPal Partnerships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 The Integrated Workflow: Symbiotic Protocol Interactions 36

5 Roadmap, Challenges, and Conclusion 37

5.1 Future Developments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.2 Protocol Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.3 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.4.1 Actionable Steps for eCommerce Developers . . . . . . . . . . . . . . . . 38

5.4.2 Join the Agentic Commerce Community . . . . . . . . . . . . . . . . . . . 39

5.4.3 The Path Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

1 INTRODUCTION: THE DAWN OF AGENTIC COMMERCE

In the rapidly evolving world of digital commerce as of January 2026, AI agents are revolu-

tionizing how transactions occur. Moving beyond human-centric interfaces, agentic commerce

empowers autonomous agents to handle discovery, evaluation, negotiation, and purchases.

This whitepaper, authored by Stefan Hamann, expands on the protocol ecosystem, providing

comprehensive coverage of each protocol with detailed technical specifications, implementa-

tion guides, and practical examples.

1.1 The Strategic Imperative for Developers

Agentic commerce is projected to drive $190–$385 billion in U.S. online spending by 2030 (Mor-

gan Stanley). Developers must focus on agent interfaces, leveraging the Agentic Commerce

Alliance’s open protocols for interoperability.

Challenges include LLM hallucinations, state management, and trust—solved by structured

protocols.

1.2 Overview of the Protocol Ecosystem

The agentic commerce ecosystem comprises multiple interoperating protocols, each address-

ing specific aspects of autonomous commerce. The major protocols and their maintainers are:

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

Table 1: Agentic Commerce Protocol Overview

The stack includes six major protocols, layered for comprehensive coverage. The foundation is

built on communication standards (MCP, A2A), upon which commerce-specific protocols (UCP,

AP2, ACP) operate, with AXP providing the richest experience layer.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

Structured product data, quality signals, embeddings

AXP Layer 5: Rich Experiences

Checkout flows between agents and merchants

ACP Layer 4: Checkout Orchestration

Discovery, transactions, verifiable payments

UCP AP2 Layer 3: Commerce & Payments

Inter-agent coordination and task delegation

A2A Layer 2: Agent Communication

Model context exchange between systems

MCP Layer 1: Context Transport

Figure 1: Agentic Commerce Protocol Stack – MCP and A2A form the communication foundation upon which commerce protocols (UCP, AP2, ACP) and experience layers (AXP) are built.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2 EXPANDED PROTOCOL BREAKDOWN

The agentic commerce ecosystem consists of multiple protocols, each designed for specific use

cases and integration scenarios. The following table provides an overview of each protocol’s

primary purpose and application:

Protocol Primary Use Case & Application

UCP Universal Commerce Protocol — The foundational protocol for

agentic commerce. Enables product discovery, checkout ses-

sions, identity linking, and order management. Designed for inter-

operability across platforms, agents, and businesses. Supports

both native and embedded checkout flows.

AXP Agentic Experience Protocol — Extends UCP with rich prod-

uct experiences. Provides structured product data (variants, con-

figurators, subscriptions), quality signals (reviews, returns, trust

scores), and sandboxed experience embeddings (3D viewers,

AR, configurators).

A2A Agent-to-Agent Protocol — Enables communication and collab-

oration between AI agents. Supports multi-agent coordination,

task delegation, and inter-agent negotiation. Essential for com-

plex purchasing decisions requiring multiple specialized agents.

ACP Agentic Commerce Protocol — Interaction model for connect-

ing buyers, AI agents, and businesses. Enables seamless check-

out flows in AI assistants (e.g., ChatGPT) with secure payment

token delegation. Focuses on instant checkout experiences.

AP2 Agent Payments Protocol — Provides verifiable and auditable

payment mandates. Uses cryptographic proofs (ES256) for pay-

ment authorization. Supports Intent/Cart/Payment verifiable cre-

dentials (VDCs) for secure agent-driven transactions.

Table 2: Protocol Use Cases and Applications

2.1 UCP: Universal Commerce Protocol

Status: Industry Standard (Apache 2.0)

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

Website: https: // ucp. dev

GitHub: https: // github. com/ google/ ucp

UCP is the common language for platforms, agents, and businesses. It defines building blocks

for agentic commerce—from discovering and buying to post-purchase experiences—allowing

the ecosystem to interoperate through one standard without custom builds. UCP was built by

the industry, for the industry to solve fragmented commerce journeys that lead to abandoned

carts and frustrated shoppers, and to enable agentic commerce.

2.1.1 Co-Developers and Industry Adoption

UCP was co-developed by industry leaders including:

• Co-Developers: Google, Shopify, Etsy, Wayfair, Target, Walmart

• PayPal Involvement: PayPal collaborates on UCP and AP2, providing payment infras-

tructure and standards contributions

• Endorsed by: Adyen, American Express, Ant International, Best Buy, Carrefour, Chewy,

Commerce, Flipkart, Gap, Kroger, Lowe’s, Macy’s, Mastercard, PayPal, Salesforce,

Sephora, Shopee, Stripe, The Home Depot, Ulta, Visa, Worldpay, Zalando

2.1.2 Core Capabilities

UCP focuses on three core capabilities in its initial launch:

• Checkout: Support complex cart logic, dynamic pricing, tax calculations, and more

across millions of businesses through unified checkout sessions.

• Identity Linking: OAuth 2.0 standard enables agents to maintain secure, authorized

relationships without sharing credentials.

• Order Management: From purchase confirmation to delivery. Real-time webhooks power

status updates, shipment tracking, and return processing.

2.1.3 Key Features and Capabilities

UCP is built for flexibility, security, and scale, designed to facilitate the entire commerce lifecycle:

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• Built on Industry Standards: REST and JSON-RPC transports with built-in support for

Agent Payments Protocol (AP2), Agent2Agent (A2A), and Model Context Protocol (MCP),

enabling different systems to work together without custom integration.

• Scalable and Universal: Surface-agnostic design that can scale to support any com-

merce entity (from small businesses to enterprise scale) and all modalities (chat, visual

commerce, voice, etc.).

• Businesses at the Center: Built to facilitate commerce, ensuring retailers retain control

of their business rules and remain the Merchant of Record with full ownership of the

customer relationship.

• Open and Extensible: Open and extensible by design, enabling development of

community-driven capabilities and extensions across verticals.

• Secure and Private: Built on proven security standards for account linking (OAuth 2.0)

and secure payment (AP2) via payment mandates and verifiable credentials.

• Frictionless Payments: Open wallet ecosystem with interoperability between providers

to ensure buyers can pay with their preferred payment methods.

2.1.4 Deployment Options

UCP supports two primary integration patterns:

• Native Checkout: Integrate and negotiate directly with a seller’s checkout API to power

native UI and workflows for your platform. This approach gives you full control over the

checkout experience while leveraging UCP’s standardized APIs.

• Embedded Checkout: Embed and render business checkout UI to support complex

checkout flows, with advanced capabilities like bidirectional communication, and pay-

ment and shipping address delegation. This approach allows businesses to maintain

their branded checkout experience within your platform.

2.1.5 Use Cases

• Agent discovering products via semantic search across multiple merchants.

• Handling subscriptions with recurring mandates.

• Multi-agent coordination for complex purchasing decisions.

• Voice-commerce through conversational interfaces.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.1.6 Security Considerations

• HTTPS required for all communications.

• OAuth 2.0 with short-lived tokens to mitigate session hijacking.

• AP2 integration for cryptographic payment proofs.

• Verifiable credentials backed by cryptographic proof of user consent.

2.1.7 Performance Optimizations

• Cache catalog data with appropriate TTL.

• Use GraphQL for efficient queries with precise data fetching.

• Implement webhook-based updates instead of polling.

2.1.8 Architecture Overview

OAuth + Queries Data Sync

AI Agent UCP Endpoint

/.well-known/ucp Merchant Backend

Extends

Extensions

(e.g., Vertical)

Figure 2: Expanded UCP Architecture.

2.1.9 API Examples (Expanded)

Checkout session:

Listing 1: UCP Checkout with Subscriptions

1 {

2 "line_items": [

3 {

4 "price_id": "price_1ABC",

5 "quantity": 1,

6 " adjustable_quantity ": true

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

7 }

8 ],

9 "mode": "subscription",

10 " billing_address_collection ": "required",

11 "success_url": "https :// agent.example/success"

12 }

Order update webhook payload:

Listing 2: UCP Webhook Example

1 {

2 "event": "order.updated",

3 "data": {

4 "order_id": "ord_123",

5 "status": "shipped",

6 "tracking_url": "https :// shipper.example/track/xyz"

7 }

8 }

2.1.10 Implementation in Shopware

Shopware provides a reference implementation of UCP through the SwagUcp plugin, available

as open source on GitHub.

Installation:

1. Clone the repository: git clone https://github.com/agentic-commerce-lab/SwagUcp.git

2. Copy to plugins directory: cp -r SwagUcp custom/plugins/SwagUcp/

3. Install dependencies: composer install

4. Install and activate: bin/console plugin:refresh && bin/console plugin:install

–activate SwagUcp

5. Run migrations: bin/console database:migrate –all SwagUcp

6. Clear cache: bin/console cache:clear

Features:

• UCP Discovery Profile at /.well-known/ucp

• Checkout Session API (Create, Get, Update, Complete, Cancel)

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• JWK Signing Keys for Webhook Verification

• Agent Domain Whitelist Security

• Request Signature Verification (ES256)

• Automatic Key Generation

Documentation: https://github.com/agentic-commerce-lab/SwagUcp

Developer Tip

For local testing, use Docker with Shopware 6.7 and ngrok. Monitor logs for OAuth errors.

The plugin automatically generates cryptographic keys on first access to the discovery

endpoint.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.2 AXP: Agentic Experience Protocol

Status: Prototype (Protocol Version: 2026-01-13)

GitHub: https: // github. com/ agentic-commerce-lab/ AXP-protocol

Maintainers: Shopware, Agentic Commerce Alliance

The Agentic Experience Protocol (AXP) extends UCP to enable rich product experiences in

agentic commerce interfaces. AXP is based on A2A, ACP, and UCP standards, and uses the

same security protocols (ES256 signatures) as UCP. AXP is maintained by Shopware and the

Agentic Commerce Alliance, providing structured product data, quality signals, and sandboxed

experience embeddings for AI agents.

2.2.1 Core Requirements

AXP addresses three core requirements for modern agentic commerce:

1. Product Data: Structured product information supporting complex types (variants, con-

figurators, events, subscriptions).

2. Quality Data: Trust signals including reviews, returns, intent information, and merchant

reputation.

3. Experience Embedding: Sandboxed live experiences from merchants (3D viewers, con-

figurators, AR).

2.2.2 UCP Compatibility

AXP is designed to work as an addon within UCP or as a standalone protocol:

Mode Discovery Endpoint Description

UCP Addon /.well-known/ucp AXP capabilities in UCP profile

Standalone /.well-known/axp Independent AXP discovery

Both Both endpoints Maximum compatibility

Table 3: AXP Deployment Options

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.2.3 Product Data Capabilities

• dev.axp.product_data — Base product data access

• dev.axp.product_data.variants — Variant product support

• dev.axp.product_data.configurator — Complex product configurators

• dev.axp.product_data.events — Event/ticket products

• dev.axp.product_data.subscriptions — Subscription products

• dev.axp.product_data.bundles — Product bundles

2.2.4 Quality Data Capabilities

• dev.axp.quality_data.reviews — Product reviews and ratings

• dev.axp.quality_data.returns — Return statistics and reasons

• dev.axp.quality_data.intent — Purchase intent signals

• dev.axp.quality_data.trust — Merchant and product trust

2.2.5 Experience Embedding Capabilities

• dev.axp.experience_embedding.viewer_3d — 3D product viewers

• dev.axp.experience_embedding.configurator — Visual configurators

• dev.axp.experience_embedding.ar — Augmented reality experiences

• dev.axp.experience_embedding.video — Interactive video

• dev.axp.experience_embedding.custom — Custom merchant experiences

2.2.6 Supported Transports

• REST API: OpenAPI 3.1 specification

• MCP: Model Context Protocol for AI agents

• A2A: Agent-to-Agent protocol

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• GraphQL: Query language support

• WebSocket: Real-time updates

2.2.7 Use Cases

• Agent evaluating product fit via AR embedding before purchase.

• Analyzing aggregated reviews for sentiment-based recommendations.

• Configuring complex products (e.g., custom laptops) with real-time pricing.

• Assessing merchant trust scores for purchase decisions.

2.2.8 Security Considerations

• Uses same ES256 signing algorithm as UCP.

• Sandbox iframes for embedded experiences to prevent XSS.

• Content Security Policy (CSP) strictly applied.

• Resource limits enforced (memory, CPU, network).

• Experience content signing for integrity verification.

2.2.9 Performance Optimizations

• Compress JSON responses with gzip/brotli.

• Use CDNs for media and experience assets.

• Lazy-load 3D/AR content.

• Cache quality data aggregates.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.2.10 Architecture Overview

Agentic Interface

Sandboxed

AXP Layer

Experiences

Quality

UCP Layer

Data

Merchant Backend

Figure 3: AXP Architecture with Experience Embeddings and Quality Data.

2.2.11 API Examples (Expanded)

Review aggregate response:

Listing 3: AXP Review Aggregate

1 {

2 "reviews": {

3 "aggregate": {

4 "rating": 4.3,

5 "count": 1247,

6 " recommendation_percentage ": 94,

7 " verified_purchase_count ": 1089

8 },

9 " aspect_ratings": [

10 {"aspect": "quality", "rating": 4.5},

11 {"aspect": "value", "rating": 4.1}

12 ]

13 }

14 }

Merchant trust data:

Listing 4: AXP Merchant Trust

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

1 {

2 " merchant_trust": {

3 "trust_score": {"score": 94, "tier": "gold"},

4 "verification": {

5 " business_verified ": true,

6 " address_verified ": true

7 },

8 " performance_metrics ": {

9 " on_time_delivery_rate ": 97.3,

10 " resolution_rate ": 99.1,

11 " response_time_hours ": 2.4

12 }

13 }

14 }

2.2.12 Implementation Notes

• Deploy standalone or as UCP addon (shared signing keys).

• Use /.well-known/axp for standalone discovery.

• AXP products can be directly used in UCP checkout sessions via

/api/axp/products/{id}/ucp-item.

• In Shopware, use custom fields for trust signals and product quality data.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.3 A2A: Agent2Agent Protocol

Status: v0.3.0 (Apache 2.0, Linux Foundation, 21.4k+ GitHub stars)

Website: https: // a2a-protocol. org

GitHub: https: // github. com/ a2aproject/ A2A

The Agent2Agent (A2A) Protocol addresses a critical challenge in the AI landscape: enabling

gen AI agents, built on diverse frameworks by different companies running on separate servers,

to communicate and collaborate effectively—as agents, not just as tools. A2A provides a com-

mon language for agents, fostering a more interconnected, powerful, and innovative AI ecosys-

tem.

2.3.1 Why A2A?

As AI agents become more prevalent, their ability to interoperate is crucial for building complex,

multi-functional applications:

• Break Down Silos: Connect agents across different ecosystems.

• Enable Complex Collaboration: Allow specialized agents to work together on tasks that

a single agent cannot handle alone.

• Promote Open Standards: Foster community-driven approach to agent communication.

• Preserve Opacity: Allow agents to collaborate without sharing internal memory, propri-

etary logic, or specific tool implementations.

2.3.2 Key Features and Capabilities (Expanded)

• Standardized Communication: JSON-RPC 2.0 over HTTP(S).

• Agent Discovery: Via “Agent Cards” detailing capabilities and connection info.

• Flexible Interaction: Supports synchronous request/response, streaming (SSE), and

asynchronous push notifications.

• Rich Data Exchange: Handles text, files, and structured JSON data.

• Enterprise-Ready: Designed with security, authentication, and observability in mind.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.3.3 Available SDKs

A2A provides official SDKs for multiple languages:

• Python: pip install a2a-sdk

• Go: go get github.com/a2aproject/a2a-go

• JavaScript: npm install @a2a-js/sdk

• Java: Available via Maven

• .NET: dotnet add package A2A

2.3.4 Agent Capabilities

With A2A, agents can:

• Discover each other’s capabilities.

• Negotiate interaction modalities (text, forms, media).

• Securely collaborate on long-running tasks.

• Operate without exposing their internal state, memory, or tools.

2.3.5 Use Cases

• Real-time price negotiations between buyer and seller agents.

• Multi-agent coordination for supply chain optimization.

• Collaborative research across specialized knowledge agents.

• Cross-platform task delegation and completion.

2.3.6 Security Considerations

• OIDC-based authentication for agent identity.

• Encrypted message transport for sensitive data.

• Authorization schemes defined in Agent Cards.

• Audit logging for compliance and debugging.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.3.7 Performance Optimizations

• WebSockets for low-latency bidirectional communication.

• SSE for efficient streaming of updates.

• Long-Running Operations (LRO) support for complex tasks.

2.3.8 Architecture Overview

Target

Client

A2A

JSON-RPC Forward

Agent

Agent

Server

OIDC OIDC

Auth

Server

Figure 4: A2A Protocol: Agent Communication with Authentication.

2.3.9 API Examples (Expanded)

Task creation example:

Listing 5: A2A Task Creation

1 {

2 "jsonrpc": "2.0",

3 "method": "tasks/send",

4 "params": {

5 "message": {

6 "role": "user",

7 "parts": [{"text": "Find best price for laptop"}]

8 }

9 },

10 "id": 1

11 }

Agent Card discovery: Query /.well-known/agent.json

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.3.10 Roadmap

• Agent Discovery: Formalize authorization schemes in AgentCard.

• Agent Collaboration: Investigate QuerySkill() for dynamic capability checking.

• Task Lifecycle: Support dynamic UX negotiation within tasks.

• Transport: Improvements to streaming reliability and push notifications.

2.3.11 Implementation Notes

• Publish Agent Cards at well-known endpoints.

• Handle async operations with appropriate timeouts.

• The protocol is an open source project under the Linux Foundation.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.4 ACP: Agentic Commerce Protocol

Status: Draft (Apache 2.0, Maintained by OpenAI and Stripe)

Website: https: // agenticcommerce. dev

GitHub: https: // github. com/ agentic-commerce-protocol/ agentic-commerce-protocol

The Agentic Commerce Protocol (ACP) is an interaction model and open standard for con-

necting buyers, their AI agents, and businesses to complete purchases seamlessly. It enables

commerce transactions through AI agents while maintaining security and trust.

2.4.1 Value Proposition

• For Businesses: Reach more customers. Sell to high-intent buyers by making products

and services available for purchase through AI agents—all while using existing commerce

infrastructure.

• For AI Agents: Embed commerce into applications. Let users discover and transact

directly with businesses without being the merchant of record.

• For Payment Providers: Grow volume. Process agentic transactions by passing secure

payment tokens between buyers and businesses through AI agents.

2.4.2 Key Features and Capabilities (Expanded)

• Specifications: OpenAPI (YAML) for HTTP API spec, JSON Schema for data models.

• Agentic Checkout API: Standardized checkout endpoints for agent integration.

• Delegate Payment: Secure payment delegation between agents and payment providers.

• RFCs: Human-readable design documents with rationale, flows, and rollout plans.

• Examples: Sample requests and responses for quick implementation.

2.4.3 Reference Implementations

ACP has been first implemented by both OpenAI and Stripe:

• OpenAI: Integration with ChatGPT and other AI agent surfaces.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• Stripe: Leverage existing payment and merchant tooling.

2.4.4 Use Cases

• Instant checkouts in ChatGPT and other AI assistants.

• Agent-managed subscriptions and recurring payments.

• Cross-platform commerce through multiple AI agent surfaces.

• Seamless payment token handling without exposing card details.

2.4.5 Security Considerations

• Tokenize all payment credentials (SharedPaymentToken).

• Never store raw card data in agent systems.

• PCI DSS compliance through payment provider integration.

• Cryptographic verification of transaction authorization.

2.4.6 Performance Optimizations

• Batch requests for high-volume scenarios.

• Async processing for long-running transactions.

• Caching of merchant capability profiles.

2.4.7 Architecture Overview

AI Agent

Business

Intent Checkout API

Buyer

(ChatGPT, etc.)

(Merchant)

Delegate Payment

Settlement

Payment Provider

(Stripe, etc.)

Figure 5: ACP Architecture: Buyer, Agent, Business, and Payment Provider Interactions.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.4.8 Governance

ACP is jointly governed by OpenAI and Stripe as Founding Maintainers, with a clear path toward

broader community governance and neutral foundation stewardship as the ecosystem matures.

2.4.9 Implementation Notes

• Review OpenAPI specs and JSON Schemas from the repository.

• Choose reference implementation (OpenAI or Stripe).

• Follow documentation guides for integration.

• Test using provided examples.

• All changes must include updated OpenAPI/JSON Schemas, examples, and changelog

entries.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.5 AP2: Agent Payments Protocol

Status: v0.1.0 (Google, 2.7k stars)

AP2 for verifiable payments.

2.5.1 Key Features and Capabilities (Expanded)

• Mandates: Intent/Cart/Payment VDCs.

• Types: Cards, crypto, transfers.

• Flows: Human-present/not-present.

2.5.2 Use Cases

- Authorizing agent purchases under limits. - Auditing transactions.

2.5.3 Security Considerations

Cryptographic signing (ES256); store mandates securely.

2.5.4 Performance Optimizations

Pre-validate mandates.

2.5.5 Architecture Overview

Payment

Cart

Authorize Create Execute

User Intent

Mandate

Mandate

Mandate

Settle

Merchant

Figure 6: AP2 Mandate Flow: Verifiable Credentials for Agent Payments.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.5.6 API Examples

Intent Mandate JWT (truncated): eyJhbGciOiJFUzI1NiJ9...

2.5.7 Implementation Notes

Use JWK for keys.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.6 PayPal Agentic Commerce & Store Sync

Status: Production

Website: https: // www. paypal. com/ us/ business/ ai

Documentation: https: // developer. paypal. com/ docs/ agentic-commerce/

Built on PayPal’s trusted commerce infrastructure, PayPal’s agentic commerce services are a

suite of solutions that unlock agentic shopping experiences for buyers, sellers, and AI agents

through natural-language interactions. These services power customers’ ability to discover

products, manage shopping carts, process payments, and complete transactions seamlessly

across multiple merchant partners and commerce platforms.

2.6.1 Store Sync: The Core of PayPal’s Agentic Commerce

Store Sync is PayPal’s flagship agentic commerce service that makes any merchant’s prod-

uct data discoverable within leading AI channels while seamlessly dropping orders to existing

fulfillment and management systems. Store Sync consists of two core components:

1. Product Feed Integration

• Automatically synchronizes product catalogs from multiple merchant partners and e-

commerce platforms

• Maintains near-real-time inventory data, pricing information, and product attributes

• Enables AI agents to access comprehensive product information for intelligent shopping

recommendations

• Supports Google Shopping CSV format with required fields: id, item_group_id, title,

description, link, image_link, price, availability, brand

2. Cart Orchestration

• Streamlines the entire shopping journey from product discovery to checkout completion

• AI agents can create and manage shopping carts, apply discounts and coupons, handle

shipping options

• Coordinates payment flows across different merchant systems

• Headless checkout architecture enables seamless integration with any AI surface

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.6.2 Benefits for Merchants

• Fast Integration: Product catalogs become discoverable through strategic partners in-

cluding Wix, Cymbio, Commerce (BigCommerce & Feedonomics), and Shopware

• Increased Discovery & Conversion: Products are discoverable within AI shopping sur-

faces, driving conversions with intent-driven shopping

• Preserve Customer Relationships: Merchants remain the merchant of record and re-

tain control of brand visibility and customer communications

• One-to-Many Compatibility: A single PayPal integration enables merchants to be seen

across multiple AI shopping surfaces including Perplexity and the PayPal app shopping

agent

2.6.3 Strategic Partnerships

PayPal has established major partnerships for agentic commerce:

• OpenAI: Powers instant checkout and agentic commerce in ChatGPT

• Perplexity: Launched Instant Buy ahead of Black Friday

• Microsoft: Powers Microsoft’s launch of Copilot Checkout

• Google Cloud: Agentic commerce solution for merchants

• Mastercard: Partnership for agentic commerce standards

Platform Integration Partners:

• Shopware: Deep integration for Store Sync and Cart Orchestration

• Wix: E-commerce platform integration

• Cymbio: Multi-channel commerce enablement

• Commerce (BigCommerce & Feedonomics): Enterprise commerce integration

2.6.4 Key Differentiators

• Global Scale: Leveraging 400M+ active accounts, providing reach to 200+ markets

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• Foundational Trust: 25+ years of PayPal innovation in fraud prevention, identity verifica-

tion, and buyer-seller protection

• Smart Wallet: Vaulted payment experience enabling seamless checkout without redirects

2.6.5 Cart Orchestration API

The Cart API provides three core endpoints for the complete cart lifecycle:

Table 4: PayPal Cart Orchestration API Endpoints

Cart Status Values:

• CREATED — Cart successfully created with payment token, ready for payment

• INCOMPLETE — Cart has validation issues (check validation_issues)

• READY — Previously incomplete cart is now ready for payment

• COMPLETED — Order finished, payment captured

2.6.6 Architecture Overview

“Buy shirt” Search Cart API

Buyer AI Agent PayPal

Commerce Platform Merchant API

PayPal

PayPal Catalog

PayPal

Orders API

(Product Feed)

Smart Wallet

Figure 7: PayPal Store Sync Architecture: From buyer intent through AI agent to merchant fulfillment.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

2.6.7 System Flow

The complete agentic commerce flow with Store Sync:

1. Product Discovery: Buyer asks AI agent for a product →Agent searches PayPal Catalog

2. Cart Creation: Agent sends POST /merchant-cart with items and shipping address

3. Cart Validation: Merchant API validates inventory, calculates taxes, returns cart with

totals

4. Payment Approval: PayPal Smart Wallet handles payment (no redirect needed)

5. Checkout Completion: Agent sends POST /merchant-cart/{id}/checkout with pay-

ment token

6. Order Fulfillment: Merchant processes order, PayPal captures payment

2.6.8 Product Feed Integration Options

PayPal supports multiple ingestion methods for merchant product feeds:

• SFTP/FTP Server: Host files on your server, share credentials with PayPal

• Cloud Storage (Your Bucket): Google Cloud Storage or Amazon S3 with read access

• Cloud Storage (PayPal Bucket): Upload to PayPal-provisioned GCS path

• API Access: Expose paginated catalog API for daily synchronization

• Direct URL: Publicly accessible HTTPS URLs with consistent naming

2.6.9 API Example: Cart Creation

Listing 6: PayPal Store Sync Cart Creation Request

1 {

2 "items": [

3 {

4 "variant_id": "SHIRT -BLUE -M",

5 "quantity": 1,

6 "name": "Blue Cotton T-Shirt (Medium)",

7 "price": {"currency_code": "USD", "value": "25.00"}

8 }

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

9 ],

10 " shipping_address ": {

11 " address_line_1": "123 Main Street",

12 "admin_area_2": "San Jose",

13 "admin_area_1": "CA",

14 "postal_code": "95131",

15 "country_code": "US"

16 },

17 " payment_method": {"type": "paypal"}

18 }

Listing 7: PayPal Store Sync Cart Response

1 {

2 "id": "CART -ABC123",

3 "status": "CREATED",

4 " payment_method": {

5 "type": "PAYPAL",

6 "token": "EC -7 U8939823K567"

7 },

8 "totals": {

9 "subtotal": {"currency_code": "USD", "value": "25.00"},

10 "shipping": {"currency_code": "USD", "value": "5.99"},

11 "tax": {"currency_code": "USD", "value": "2.70"},

12 "total": {"currency_code": "USD", "value": "33.69"}

13 },

14 " validation_issues ": []

15 }

2.6.10 Protocol Collaborations

PayPal is actively involved in multiple agentic commerce protocols:

• UCP: Endorsed and contributing to Universal Commerce Protocol development

• AP2: Collaborating with Google on the Agent Payments Protocol for verifiable, auditable

transactions

• Standards: Working with Mastercard and other partners on agentic commerce standards

2.6.11 Security & Trust

• JWT Authentication: PayPal-issued tokens for all API calls

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• Tokenized Payments: Never expose raw card data

• Purchase Protection: Available on eligible transactions

• Seller Protection: Available on eligible purchases

• PCI DSS Compliance: Enterprise-grade security infrastructure

2.6.12 Implementation Steps

1. Request Access: Contact PayPal AI team to enable Store Sync

2. Product Feed Setup: Configure product feed ingestion (SFTP, Cloud, API, or URL)

3. Merchant Manifest: Provide merchant metadata (storeName, storeUrl, currency, coun-

try)

4. Cart API Integration: Implement /merchant-cart endpoints for cart lifecycle

5. PayPal Orders Integration: Connect Cart API with PayPal Orders API v2 for payment

processing

6. Testing: Validate integration with test scenarios before go-live

Developer Tip

Store Sync requires completing the product feed integration before setting up cart orches-

tration. Use PayPal’s JWT tokens for authentication—tokens are generated and managed

by PayPal, not merchants. The Cart API uses PUT for complete replacement of cart data,

not incremental updates.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

3 INDUSTRY ENDORSEMENTS AND ECOSYSTEM

The agentic commerce ecosystem has gained significant industry support, with major players

across retail, payments, and technology endorsing and implementing these standards.

3.1 UCP Endorsers

The Universal Commerce Protocol is endorsed across the ecosystem:

Retailers & Marketplaces:

• Best Buy

• Kroger

• The Home Depot

• Carrefour

• Lowe’s

• Ulta

• Chewy

• Macy’s

• Walmart

• Etsy

• Sephora

• Wayfair

• Flipkart

• Shopee

• Zalando

• Gap

• Target

Payment Providers & Networks:

• Adyen

• Mastercard

• Visa

• American Express

• PayPal

• Worldpay

• Ant International

• Stripe

Technology & Platforms:

• Google

• Shopify

• Salesforce

• Commerce

3.2 ACP Partnerships

The Agentic Commerce Protocol has production implementations from:

• OpenAI: ChatGPT commerce integration

• Stripe: Payment infrastructure for agentic transactions

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

3.3 A2A Community

The Agent2Agent Protocol is an open source project under the Linux Foundation with:

• 21,400+ GitHub stars

• 2,200+ forks

• 134+ contributors

• Active community discussions

3.4 PayPal Partnerships

PayPal’s agentic commerce initiative includes partnerships with:

• OpenAI: Instant checkout in ChatGPT

• Microsoft: Copilot Checkout integration

• Google Cloud: Merchant solutions

• Mastercard: Agentic commerce standards

• Perplexity: Instant Buy features

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

4 THE INTEGRATED WORKFLOW: SYMBIOTIC PROTOCOL INTER-

ACTIONS

The agentic commerce protocols work together to enable seamless end-to-end transactions.

Each protocol handles a specific aspect of the commerce journey.

1. Discovery (UCP/PayPal): Agent discovers products via UCP endpoints or PayPal’s com-

merce APIs.

2. Evaluation (AXP): Agent retrieves quality data, reviews, and trust signals.

3. Negotiation (A2A): Multi-agent coordination for complex decisions.

4. Checkout Orchestration (ACP): Checkout flow management between agent and mer-

chant.

5. Settlement (AP2): Cryptographically verifiable payment mandates.

6. Post-Purchase (UCP webhooks): Order tracking and fulfillment updates.

User AI Agent Merchant Payment

1. Prompt

2. Discovery 3. Evaluation 4. Negotiation 5. Checkout

6. Settlement 7. Post-Purchase

Orchestration

Figure 8: Complete Agentic Commerce Flow: From User Intent to Post-Purchase.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

5 ROADMAP, CHALLENGES, AND CONCLUSION

5.1 Future Developments

• Q1 2026: AXP moves to stable release; broader UCP adoption.

• Q2 2026: B2B extensions in A2A; enhanced agent discovery.

• Q3 2026: Cross-protocol interoperability improvements.

• 2027: Path toward W3C standards; neutral foundation governance.

5.2 Protocol Evolution

• UCP: Continued expansion of capabilities and vertical extensions.

• ACP: Moving from draft to stable with broader merchant adoption.

• A2A: Enhanced agent discovery and dynamic skill querying.

• AXP: Production-ready experience embedding and quality signals.

• AP2: Expanded payment method support and mandate types.

5.3 Resources

• UCP: https://ucp.dev | https://github.com/google/ucp

• ACP: https://agenticcommerce.dev | https://github.com/

agentic-commerce-protocol/agentic-commerce-protocol

• A2A: https://a2a-protocol.org | https://github.com/a2aproject/A2A

• AXP: https://github.com/agentic-commerce-lab/AXP-protocol

• PayPal: https://www.paypal.com/us/business/ai

• Agentic Commerce Alliance: https://agentic-commerce.dev

• Shopware UCP Plugin: https://github.com/agentic-commerce-lab/SwagUcp

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

5.4 Conclusion

Agentic commerce represents a fundamental shift in how transactions occur in the digital econ-

omy. The protocols described in this whitepaper—UCP, ACP, A2A, AXP, AP2, and PayPal’s

agentic commerce services—form a comprehensive ecosystem that enables AI agents to dis-

cover, evaluate, negotiate, and complete purchases autonomously.

5.4.1 Actionable Steps for eCommerce Developers

As an eCommerce developer, here’s how you can get started with agentic commerce today:

1. Implement UCP Foundation

• Start by implementing UCP discovery endpoints (/.well-known/ucp) to make your store

discoverable by AI agents.

• Set up checkout session APIs to enable agent-driven purchases.

• For Shopware users, leverage the open-source SwagUcp plugin as a reference imple-

mentation.

• Configure OAuth 2.0 for secure agent authentication and identity linking.

2. Enhance with AXP for Rich Experiences

• Implement AXP product data capabilities to provide structured product information with

variants, configurators, and subscriptions.

• Expose quality data endpoints (reviews, returns, trust signals) to help agents make in-

formed purchase decisions.

• Enable experience embedding for 3D viewers, AR experiences, and interactive configu-

rators.

• Use AXP as a UCP addon or standalone protocol, depending on your architecture.

3. Integrate Payment Protocols

• Implement AP2 mandates for verifiable, auditable agent payments.

• Support PayPal’s agentic commerce APIs for instant checkout experiences.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• Ensure cryptographic signing (ES256) for all payment-related operations.

• Store mandates securely and implement proper validation workflows.

4. Enable Multi-Agent Collaboration

• Publish Agent Cards at /.well-known/agent.json endpoints.

• Implement A2A protocol support for agent-to-agent communication.

• Enable ACP checkout flows for seamless integration with AI assistants like ChatGPT.

5. Security and Compliance

• Implement domain whitelisting for authorized AI agents.

• Use request signature verification (ES256) for high-security scenarios.

• Ensure all communications use HTTPS.

• Follow GDPR and privacy regulations for agent-driven transactions.

• Implement proper audit logging for compliance and debugging.

6. Testing and Validation

• Test with major AI platforms (OpenAI, Google Gemini, Anthropic).

• Use the Agentic Commerce Playground at https://agentic-commerce.dev for testing.

• Monitor API calls and implement proper error handling.

• Set up webhook endpoints for real-time order updates.

5.4.2 Join the Agentic Commerce Community

The agentic commerce ecosystem is built on open standards and thrives through community

contribution. Here’s how you can get involved:

Contribute to Protocol Development

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• AXP Protocol: Join the development of the Agentic Experience Protocol at https:

//github.com/agentic-commerce-lab/AXP-protocol. AXP is actively maintained by

Shopware and the Agentic Commerce Alliance, and we welcome contributions from the

community.

• UCP: Contribute to the Universal Commerce Protocol at https://github.com/google/

ucp.

• A2A: Participate in the Agent2Agent Protocol development under the Linux Foundation.

Join the Agentic Commerce Alliance

• Visit https://agentic-commerce.dev to learn more about the Alliance and its mission.

• Participate in working groups and contribute to protocol specifications.

• Share your implementation experiences and help improve documentation.

• Connect with other developers building agentic commerce solutions.

Share Your Implementation

• Open source your UCP/AXP implementations to help others learn.

• Contribute reference implementations and code examples.

• Write blog posts and tutorials about your agentic commerce journey.

• Present at conferences and meetups to spread awareness.

5.4.3 The Path Forward

The protocols described in this whitepaper are not just theoretical concepts—they are

production-ready standards being implemented by major retailers, payment providers, and

technology platforms today. As an eCommerce developer, you have the opportunity to:

• Be an Early Adopter: Position your business at the forefront of the agentic commerce

revolution.

• Shape the Standards: Contribute to protocol development and help define the future of

commerce.

www.agentic-commerce.dev Agentic Commerce for Developers | Technical Whitepaper

• Build Innovative Solutions: Leverage these protocols to create unique, AI-powered

shopping experiences.

• Join a Growing Ecosystem: Connect with developers, merchants, and platforms build-

ing the future of commerce together.

The future of commerce is agentic. The protocols are ready, the tools are available, and the

community is welcoming. Start implementing today, contribute to the standards, and help shape

the future of how AI agents and humans will shop together.

Get Started: Visit https://agentic-commerce.dev to explore the protocols, access the

developer playground, and join the Alliance. Contribute to AXP at https://github.com/

agentic-commerce-lab/AXP-protocol and help build the future of agentic commerce.