E-com Directors
Who need to add the "AI Agent" channel across multiple agent platforms without disrupting existing storefront operations.
IMPLEMENTATION SERVICES
Protocol Implementation:
Protocol Implementation:
UCP, MCP, A2A
AI agents need protocols to interact with your store. We implement UCP for Google AI Mode, MCP for tool-using agents like Claude and ChatGPT, and A2A for agent-to-agent commerce — so your products are transactable everywhere agents shop.
Get Implementation Estimate
THREE PROTOCOLS, ONE INTEGRATION PARTNER
The Protocols Powering Agent Commerce
Different agents use different protocols. A complete agent commerce strategy requires implementing all of them — and we handle the entire stack.
UCP
LiveUniversal Commerce Protocol
by Google
The protocol powering Google AI Mode checkout. Exposes discovery manifests, checkout sessions, payment handling, and order management to Google's agent ecosystem.
- Discovery Manifest (/.well-known/ucp)
- Checkout session management
- Payment handler integration
- Order tracking & post-purchase
- Identity linking (OAuth 2.0)
- Catalog sync with Google Merchant Center
MCP
LiveModel Context Protocol
by Anthropic
The protocol for exposing your commerce capabilities as tools that AI agents can invoke. Product search, inventory checks, cart operations, and checkout — all as callable functions.
- Tool definitions for commerce actions
- Product search & filtering
- Cart & checkout operations
- Inventory & pricing queries
- Secure authentication flows
- Streaming response support
A2A
EmergingAgent-to-Agent Protocol
by Google
The agent-to-agent communication protocol. Your commerce agent publishes an Agent Card declaring its capabilities, then negotiates with buyer agents to complete transactions.
- Agent Card publication
- Capability declaration
- Task negotiation & execution
- Multi-turn agent conversations
- Secure agent authentication
- Event-driven status updates
Agents can't buy from you without protocols in place.
Ideal Teams 01 02 03
Who Is This For?
Platform Architects
Who want clean, standards-based protocol integrations (UCP, MCP, A2A) rather than fragile custom API hacks for each agent.
Innovation Leads
Who are tasked with "solving AI commerce" and need a multi-protocol, production-ready solution, not a proof of concept.
Developer Experience
Integration in Lines, Not Monoliths
You don't need to rebuild your backend. UCP works as a lightweight layer on top of your existing infrastructure. Simply add structured metadata to your product pages or expose a standard API endpoint.
Zero-Config Discovery
Agents automatically scrape and index UCP-enhanced JSON-LD tags from your existing product pages.
Headless Capability
Decouple your inventory from your frontend. Let Gemini or ChatGPT become your new storefront.
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "Sony Alpha a7 IV",
/* UCP EXTENSION: Enables Agent Discovery */
"ucp:commerce": {
"inventory": {
"type": "RealTime",
"endpoint": "https://api.store.com/stock"
},
"checkout": {
"supported_protocols": ["AP2"]
}
}
}# Initiate an Agent Session
curl -X POST https://api.ucp.network/v1/sessions \
-H "Authorization: Bearer sk_test_..." \
-H "Content-Type: application/json" \
-d '{'
"agent_id": "gemini-pro-shopping",
"intent": {
"sku": "a7iv",
"action": "hold_inventory"
}
}'Simulator
See the data packets fly between User, Agent, and Merchant.
Live Transaction Simulator
Visualize the data path of an agentic purchase
User Intent
User asks: "Buy red running shoes, size 10."
AI Agent
Agent parses intent and queries UCP network.
UCP Layer
Protocol standardizes request & identity.
Merchant
Merchant API returns structured inventory.
Payment
Tokenized payment exchange via UCP.
Complete
Order confirmed & receipt generated.
Step 1 of 6
User asks: "Buy red running shoes, size 10."
Military-Grade Security
UCP replaces shared secrets (like passwords) with asymmetric cryptography. Explore the four defense layers below.
Layer 1
Secure Enclave
Device-Level Auth
Layer 2
AP2 Protocol
Cryptographic Binding
Layer 3
Tokenization
Data Anonymization
Layer 4
Merchant Registry
Anti-Phishing
Secure Enclave
Security Layer 1 of 4
Private keys never leave the user's device. Transaction signatures are generated inside the hardware Secure Enclave (e.g., Apple Secure Enclave, Android Titan M) only after a successful biometric challenge.
Technical Specifications
Elliptic Curve Cryptography (ECC)
Biometric Challenge
Hardware Isolation
PROTOCOL COMPARISON
UCP vs ACP — Feature Comparison
See how UCP's full-stack approach compares to the agent-only interaction layer.
| Feature | UCP (Universal) | ACP (Agentic) |
|---|---|---|
| Scope | Full merchant-side commerce stack | Agent interaction layer |
| Product Discovery | /.well-known/ucp manifest + catalog sync | Relies on external search APIs |
| Cart & Checkout | Native session management & AP2 payment | Delegates to merchant checkout |
| Payment Security | Tokenization, Secure Enclave, PCI-DSS L1 | Passes through to PSP |
| Order Management | Full lifecycle tracking & webhooks | Limited post-purchase support |
| Identity Linking | OAuth 2.0 customer account mapping | Agent-level auth only |
| Transport Options | REST, MCP, A2A | Primarily REST / HTTP |
| Merchant Registry | Decentralized identity verification | No built-in registry |
*While ACP focuses on the agent interaction layer, UCP provides the robust merchant-side infrastructure needed for full-scale operations.
DEEP DIVE
Interactive Architecture Explorer
Click any node to explore how the protocol layers connect. Each component plays a critical role in enabling AI-powered commerce.
Protocol Core
Market Impact
Merchants & Platforms
AI Agents
Payment Providers
Governance & Security
Transport Layer
CORE LAYER
Protocol Core
The protocol stack (UCP, MCP, A2A) is the central orchestration layer that standardizes how AI agents discover products, negotiate terms, and complete purchases across any merchant platform.
Key Highlights
- Platform-agnostic protocol layer
- Standardized discovery manifests
- Cryptographic transaction binding
- Real-time session management
"UCP acts as the universal translator, ensuring that any AI agent can discover, configure, and purchase products from any merchant."
STRAIGHT TALK
Before You Decide
"Can't our dev team implement UCP from the spec?"
Technically, yes — the spec is public. In practice, enterprise implementations require handling edge cases the spec doesn't cover: payment handler integration, inventory sync timing, error states, and multi-tenant checkout flows. Our team has shipped this across SFCC, Shopify Plus, and headless stacks. Your devs stay focused on your core product.
"What if the protocols change?"
They will — UCP, MCP, and A2A are all evolving. That's exactly why we offer managed services post-implementation. We track protocol changes across all three specs and apply updates proactively. Your implementation stays current without your team needing to monitor three separate protocol repos.
"We're already stretched thin on dev resources."
Most implementation work is done by our team. We need API access, a staging environment, and a technical point of contact for review and sign-off. Your developers are involved mainly at integration checkpoints — not carrying the implementation workload.
"Do we need all three protocols?"
Different agents use different protocols. UCP powers Google AI Mode checkout. MCP powers tool-using agents like Claude and ChatGPT. A2A enables agent-to-agent negotiation. Most clients implement UCP + MCP as a baseline, then add A2A for B2B use cases. We scope based on your audience and channels.
Implementation Packages
Scoped to your platform. Includes UCP implementation with MCP and A2A add-on options.
2-6 weeks
Shopify Plus
Native acceleration + multi-protocol optimization
- ✓ Readiness assessment
- ✓ Multi-protocol architecture
- ✓ Documentation & training
- ✓ 30-day post-launch support
6-14 weeks
SFCC / BigCommerce / Adobe Commerce
Plugin + full protocol integration
- ✓ Readiness assessment
- ✓ Multi-protocol architecture
- ✓ Documentation & training
- ✓ 30-day post-launch support
8-16 weeks
Headless / Custom
Custom SDK + multi-protocol agent layer
- ✓ Readiness assessment
- ✓ Multi-protocol architecture
- ✓ Documentation & training
- ✓ 30-day post-launch support
Not sure which package fits your stack? Start with the readiness assessment →
Or compare all pricing plans →
FAQ
Common Questions
What protocols do you implement? ▾
We implement Universal Commerce Protocol (UCP) for Google AI Mode checkout, Model Context Protocol (MCP) for tool-using agents like Claude and ChatGPT, and Agent-to-Agent Protocol (A2A) for agent-to-agent commerce. Most clients implement all three as part of a complete agentic commerce stack.
How long does implementation take? ▾
Timeline depends on platform: Shopify Plus takes 2–6 weeks, Salesforce Commerce Cloud and BigCommerce take 6–14 weeks, and headless or custom stacks take 8–16 weeks. We provide a precise estimate after the readiness assessment.
Do you have an open-source option for SFCC? ▾
Yes. ForkPoint maintains the first open-source UCP cartridge for Salesforce Commerce Cloud. Enterprise deployments typically still require customization, performance tuning, and multi-protocol enablement beyond the cartridge.
What is required from our team during implementation? ▾
We need API access, a technical point of contact for integration questions, and access to your staging environment. Most implementation work is done by our team — your developers are involved mainly for review and sign-off.
How much does protocol implementation cost? ▾
Shopify Plus starts at $1,000–$2,500. Salesforce Commerce Cloud, BigCommerce, and Adobe Commerce range from $2,500–$5,000. Headless and custom implementations start from $5,000. All prices are for the implementation only; ongoing support is available separately.