Introducing The Protocol: A New Standard for Agentic Commerce
Rye
4 minutes read
Today we're announcing a universal, open protocol for agentic commerce — already adopted by every merchant, every agent, and every payment provider on the planet.
TL;DR / Key Takeaways
The agentic commerce ecosystem is fragmenting across competing protocols (ACP, UCP, TAP) — each requiring merchant integration, catalog reformatting, and months of onboarding.
There's already a universal protocol adopted by every merchant on the planet: the World Wide Web. Over 200 million endpoints, 30+ years of battle-testing, supported by every browser, device, and country.
Rye's Universal Checkout doesn't wait for protocol adoption — give it any product URL and it returns a confirmed order with real-time pricing, inventory, and payment processing.
The protocols will serve the head of the market, but the long tail of millions of merchants already speaks HTTP.
Today, we're announcing a universal, open protocol for agentic commerce — one that enables seamless transactions between AI agents, consumers, and businesses across the entire commerce lifecycle.
Not another proposal. Not a draft specification seeking industry feedback. Not a standard that requires merchant integration, catalog reformatting, or a six-month onboarding process.
A protocol that is already universally adopted.
The Problem
The agentic commerce ecosystem is early, and the infrastructure is fragmenting fast.
Stripe and OpenAI codeveloped the Agentic Commerce Protocol. Google and Shopify launched the Universal Commerce Protocol. Visa introduced the Trusted Agent Protocol. Mastercard shipped Agent Pay. Every major platform is publishing its own standard for how AI agents should discover products, initiate checkout, and complete transactions.
These are serious efforts by serious companies. ACP brings merchant-friendly payment primitives. UCP provides a common language across consumer surfaces. Both move the ecosystem forward.
But adoption takes time. Merchants need to integrate. Catalogs need to be reformatted. Agents need to support multiple protocols simultaneously. And while the standards compete and converge, the vast majority of merchants — millions of them — remain unreachable by any AI agent.
So we asked a different question: what if there were a protocol that every merchant had already adopted?
The Protocol
The protocol we're announcing today has several properties that distinguish it from existing standards:
Universal adoption. Every merchant on the internet already supports it. Not thousands. Not the Shopify ecosystem. Every single one — from Fortune 500 retailers to independent boutiques to a furniture store in rural Ohio that last updated its website in 2019. Total endpoint count: over 200 million.
Battle-tested at scale. The protocol has been in continuous production for over 30 years. It processes trillions of dollars in annual transaction volume. It has survived every major shift in computing — mobile, cloud, social, and now AI.
Multi-language, multi-currency, multi-geography. The protocol operates natively in every country, every language, and every currency on earth. No localization layer required.
Full commerce lifecycle support. Product discovery, real-time pricing, inventory availability, shipping calculation, tax resolution, payment processing, order confirmation, shipment tracking, returns, and customer support — all natively supported.
Rich product data. Structured and unstructured product information — images, descriptions, specifications, reviews, variant selection, size guides, compatibility matrices — all accessible through the protocol's native data formats.
No merchant integration required. Zero. Merchants don't need to opt in, reformat their catalogs, expose new API endpoints, or even know the protocol is being used. It works with their existing infrastructure, as-is.
Open standard. Maintained by an international governance body. Fully documented. Implemented by every major technology company on the planet.
Endorsed by the entire ecosystem. Google. Apple. Microsoft. Amazon. Shopify. Stripe. Visa. Mastercard. PayPal. Adyen. Every browser vendor. Every payment processor. Every device manufacturer. Every merchant platform.
No other protocol in agentic commerce can make any of these claims.
Technical Architecture
The protocol is built on a layered architecture designed for extensibility and resilience:
Transport layer: Operates over TCP/IP with TLS encryption standard on all commercial endpoints
Data format: Supports HTML, JSON, XML, and binary payloads with full multimedia capability
Authentication: Native support for tokenized payments, session management, and delegated authorization
Discovery: Built-in indexing, search, and semantic retrieval across the entire merchant corpus
State management: Stateful transaction flows with confirmation, receipt generation, and audit trails
The specification is maintained at ietf.org and has been ratified by every major standards body.
Introducing The Protocol
The protocol is the World Wide Web.
HTTP/HTTPS. The thing you're reading this on.
Every merchant already has an endpoint. It's called a website.
Why This Matters
The agentic commerce ecosystem is converging on a real problem: how do you enable AI agents to purchase products from any merchant? The protocol-first approach says: get merchants to adopt a new standard. The web-first approach says: meet merchants where they already are.
At Rye, we built the Universal Checkout API to do exactly that. Give us a product URL — any URL, any merchant — and we return a confirmed order. Real-time pricing. Real inventory. Tokenized payments. Shipping and tax resolved. No merchant integration. No protocol adoption. No catalog reformatting.
The protocols will mature. Adoption will grow. ACP and UCP will serve the head of the market well. But the long tail — the millions of merchants who will never integrate with any protocol — already speaks HTTP.
We just built the infrastructure to listen.
Product
Resources