In the first two weeks of January 2026, Google, Microsoft, OpenAI, and Shopify all announced major agentic commerce infrastructure. The rails for AI agents to shop on your behalf are being built at breakneck speed. Discovery protocols. Checkout flows. Payment authorization. Agent-to-agent communication.
But there’s a gap in the stack that nobody has solved: when an AI agent shows up to complete a purchase, how do you know which agent it is? How do you verify it’s the same agent that earned that 4.9-star rating last month?
The answer, right now, is you don’t. At least not in any interoperable way.
The January 2026 Protocol Explosion
On January 8, Microsoft launched Copilot Checkout — letting shoppers complete purchases directly inside Copilot’s chat interface without leaving to external sites. PayPal powers the payments. Shopify provides checkout infrastructure.
Three days later, Google CEO Sundar Pichai announced the Universal Commerce Protocol (UCP) at the National Retail Federation conference. Co-developed with Shopify, Walmart, Target, Wayfair, and Etsy, and endorsed by Visa, Mastercard, Stripe, American Express, and 20+ other companies. UCP creates a common language for AI agents to handle the full shopping journey — discovery, cart management, checkout, post-purchase support.
OpenAI and Stripe’s Agentic Commerce Protocol (ACP) is already live, powering “Instant Checkout” in ChatGPT with over a million Shopify merchants participating. Instacart’s integration became the first fully embedded grocery shopping experience within ChatGPT.
Shopify positioned itself as the universal middleware with Agentic Storefronts — configure once, syndicate products across ChatGPT, Google AI Mode, and Microsoft Copilot simultaneously. President Harley Finkelstein revealed Shopify has seen a 14x increase in orders sourced from AI agents over the past 12 months.
Meanwhile, payment networks launched their own agent infrastructure. Visa’s Trusted Agent Protocol (TAP) uses cryptographic signatures to verify agents at the network edge. Mastercard’s Agent Pay issues “Agentic Tokens” uniquely tied to users.
And in China, Alibaba’s Qwen chatbot now completes purchases through Taobao and Alipay without leaving the conversation. ByteDance’s Doubao can navigate multiple shopping apps autonomously — though major platforms blocked its capabilities after launch.
The Market Is Moving Fast
The projections vary but share a common direction:
- Deloitte: Up to $17.5 trillion in global commerce “influenced” by AI agents by 2030
- McKinsey: $3-5 trillion globally, with up to $1 trillion in US retail
- Bain: 15-25% of US online retail by 2030
- Morgan Stanley: $190-385 billion US by 2030
Current adoption metrics support the trajectory. Adobe reported AI-driven traffic to seller sites grew 693% during the 2025 holiday season. Shopify’s AI-attributed orders are up 14x year-over-year. The infrastructure is getting built because the demand is real.
What’s Being Built
The agentic commerce protocol stack has organized into clear layers:
Communication: Google’s Agent-to-Agent (A2A) protocol handles agent discovery and coordination. Anthropic’s Model Context Protocol (MCP) handles agent-to-tool connections. Both are now under the Linux Foundation.
Payments: Google’s Agent Payments Protocol (AP2) introduces Verifiable Digital Credentials for authorization. Coinbase’s x402 protocol uses the HTTP 402 “Payment Required” status code for cryptocurrency micropayments — it’s processed 35M+ transactions since summer 2025.
Commerce: Google/Shopify’s UCP covers the full journey. OpenAI/Stripe’s ACP focuses on checkout. Microsoft is adopting ACP for Copilot Checkout.
This is real infrastructure. Production systems. Millions of merchants. Billions of products.
What’s Missing: The Identity Layer
Here’s the gap. When an AI agent completes a purchase on your behalf, the current infrastructure can verify:
- That the agent has valid payment authorization
- That the user consented to this specific transaction
- That the merchant’s inventory and pricing are accurate
- That the checkout flow completed successfully
But it cannot verify, in any universal way:
- Which specific agent this is
- Whether this agent is the same one you interacted with before
- What this agent’s history looks like across platforms
- Whether the agent’s identity has changed hands
The identity verification approaches that do exist are fragmented across competing frameworks with no interoperability.
Six Identity Frameworks, Zero Interoperability
The agent identity space isn’t empty — it’s crowded with incompatible solutions:
Microsoft Entra Agent ID offers enterprise-grade identity management with OAuth 2.0/OpenID Connect support, conditional access policies, and lifecycle governance. But it’s designed for corporate AI deployments, not consumer-facing agents.
Visa’s Trusted Agent Protocol cryptographically verifies agents using HTTP Message Signatures. Agents register in Visa’s directory and sign each request. But a Visa-verified agent isn’t automatically trusted by Mastercard’s system.
Mastercard Agent Pay uses similar architecture with “Agentic Tokens” and Web Bot Auth compliance. But it’s a separate registry, separate credentials, separate verification.
Trulioo + PayOS launched “Know Your Agent (KYA)” with a “Digital Agent Passport” — verifying developer identity, locking source code, capturing user consent. But it’s a centralized verification service, not a portable identity standard.
HUMAN Security’s AgenticTrust and DataDome’s Agent Trust Management focus on behavioral verification and bot management — detecting bad agents rather than credentialing good ones.
Cloudflare is partnering with Visa and Mastercard on Web Bot Auth implementation at the CDN layer — but that’s verification at the network edge, not portable identity.
Each of these solves a real problem. None of them talk to each other.
The SSL/TLS Analogy
In the early days of e-commerce, every website had its own approach to security. Then SSL/TLS emerged as a universal standard. Certificate authorities provided third-party verification. Browsers displayed the padlock icon. Consumers learned to look for HTTPS.
The agentic commerce ecosystem doesn’t have its equivalent yet. There’s no universal agent certificate authority. No cross-platform credential portability. No consumer-facing indicator that says “this agent’s identity has been verified.”
The closest candidate is Web Bot Auth (an IETF draft for HTTP Message Signatures), but Visa, Mastercard, Microsoft, and the identity vendors are implementing it in incompatible silos.
Why This Matters
Without interoperable agent identity, several problems emerge:
Reputation doesn’t travel. An agent that’s completed 10,000 successful purchases through ChatGPT has no way to prove that history when it shows up at a new merchant through Google AI Mode.
Fraud is harder to detect. HUMAN Security research indicates AI-powered bot traffic surged 300% in the past year, with 25+ billion AI bot requests hitting the commerce industry in just two months. Bad agents can impersonate good ones across platforms.
Consumer trust lags adoption. Only 24% of consumers are comfortable letting AI complete a purchase on their behalf. The infrastructure exists, but the trust layer hasn’t caught up.
Identity can be sold or rented. If agent reputation exists only within platform silos, there’s no way to detect when an “established” agent is actually being operated by someone who bought or rented access to it.
What Would a Solution Look Like?
A real agent identity layer would need several properties:
Universal registry. A place where any agent can register an identity that’s recognized across platforms — not locked into Visa’s system or Microsoft’s system or any single vendor.
Non-transferable credentials. Identity that can’t be sold on a secondary market. If reputation is valuable, someone will try to buy it. The system needs to make that impossible or at least transparent.
Portable history. Transaction records and reputation signals that travel with the agent, not locked in platform silos.
Transparency over trust scores. Rather than opaque algorithms that output a number, systems that show the actual history and let counterparties decide how to interpret it.
Some approaches are emerging. Blockchain-based identity standards like ERC-8004 (for agent discovery) combined with ERC-5192 (soulbound tokens that can’t be transferred) offer one architectural path. But these are early — ERC-8004 is still in draft, with mainnet deployment expected Q2 2026.
The Race to Become the Certificate Authority
Whoever solves agent identity interoperability will control a critical layer of infrastructure. If Deloitte’s projections are right, that layer could mediate trillions in annual commerce by 2030.
The payment networks (Visa, Mastercard) have distribution but are building proprietary systems. The tech giants (Microsoft, Google) have reach but are focused on their own ecosystems. The identity specialists (Trulioo, HUMAN Security) have expertise but lack the network effects.
The gap remains: an open, interoperable standard for agent identity that works across platforms, makes reputation portable, and prevents identity from becoming a tradeable asset.
The rails are here. The trust layer isn’t. Whoever builds it will shape how AI agents participate in economic life for the next decade.
Further Reading
- ERC-8004 + ERC-5192: The Complete Identity Stack — How blockchain standards could solve the interoperability problem
- The Identity Rental Problem — Why non-transferable identity still has loopholes
- Every Company Building AI Agent Identity in 2026 — The competitive landscape
We’re building transparent, non-transferable identity infrastructure for AI agents at RNWY — the identity layer the agentic commerce stack is missing.