Your Competitors Are Capturing Agentic Commerce Orders. Are You?
Rye
10 minutes read
400+ brands. 120,000+ orders per month. Zero engineering work. Here's how to evaluate Rye against UCP, ACP, Amazon Buy for Me, and the rest of the landscape.
TL;DR / Key Takeaways
400+ brands are connected to Rye's supply network. 120,000+ orders per month flow through Rye today, driven primarily by corporate and creator gifting platforms (Thnks, Throne), rewards platforms (Bilt), card issuers and payment platforms building for AI agents (Lithic), and Rye's own agent integrations.
Zero engineering lift for brands joining Rye. No feed endpoints, no checkout APIs, no conformance tests, no SLO commitments — Rye connects to your existing site.
Protocol-based alternatives cost real engineering time. Shopify Engineering's own UCP implementation guidance estimates 4–6 weeks to production in the best case, 4–8 weeks on Shopify, 6–12 weeks on Magento.
Every protocol is a single-ecosystem play. UCP gets you Google. ACP gets you ChatGPT. Amazon Buy for Me gets you Amazon. Full agentic coverage via protocols means stacking three or more independent integrations.
You stay merchant-of-record on Rye. Customer, data, post-purchase relationship — all yours. Google UCP matches this on paper. Amazon Buy for Me does not.
Use the 6-criterion rubric in Section 3 to evaluate Rye and every other platform in any vendor conversation.
If you're new to how agentic commerce works, start with our primer for merchants. If you're already past the "what is this" stage and you need to make a decision, keep reading.
Who's Actually Buying Through Rye Right Now
Before you evaluate any agentic commerce platform, you want to know the same thing every brand wants to know: is there real buy-side demand, and where's it coming from?
On Rye, the answer is concrete. Orders route through the network from four overlapping sources.
1. Corporate and creator gifting platforms — Rye's largest demand channel today. Gifting platforms use Rye's APIs to source real-time inventory and place orders at merchants at scale. Named customers include:
Thnks, one of the most recognized corporate gifting platforms in B2B, routes order volume through Rye's infrastructure. (Featured on rye.com.)
Throne routes creator-gifting volume to thousands of brands through Rye — including a long tail of stores Throne has no direct relationship with. After moving to Rye's network, Throne 4x'd the inventory its creators could pull from and cut order cancellations by 50%. (case study)
Gift Drive, a nonprofit donation platform, routes in-kind gift orders to partner retailers through Rye. 5,000 items donated and $50K raised in its launch season. (case study)
2. Rewards and loyalty platforms. Rewards networks use Rye's APIs to let members redeem points against real-world products at scale. Bilt Rewards — one of the largest consumer rewards networks in the US, built around point-earning on rent and daily spend — routes reward-redemption volume through Rye's infrastructure.
3. Card issuers and payment platforms building for AI agents. Companies providing the payment rails agents need to transact — programmable cards, issuer processing, payment controls — use Rye to handle the checkout layer their cards can't.
Lithic is a card issuing platform that provides programmable cards for AI agents to pay with. In a joint integration with Arcade (a secure agent workflow engine) and Rye, Lithic cards are generated on demand, routed through Arcade's workflow, and used to complete real purchases at merchants via Rye's Universal Checkout API. Lithic provides the payment method; Rye provides the checkout execution. "What Rye offers is essential to build the level of trust required for agentic commerce," says CPO Robin Gandhi. (case study)
4. Rye's native ChatGPT integration. Rye is also live inside ChatGPT as an MCP-based shopping tool, letting users discover and purchase products across Rye's connected brand network without leaving their conversation. Orders initiated through Rye's ChatGPT product route to the brand as the fulfillment destination.
These aren't brands. They're the buyers — the apps and surfaces placing orders at merchants. The brands connected to Rye are the destinations those orders land at. That's the side of the marketplace this post is about.
Across the full network: 400+ brands on the supply side, 120,000+ orders per month flowing through Rye.
What Joining Rye Actually Looks Like
Most brands assume entering agentic commerce means a checkout rebuild, a new fraud stack, and a multi-quarter engineering project. That's what it takes if you integrate directly to a protocol like OpenAI ACP or Google UCP. It's not what it takes on Rye.
Step 1 — Connection. Rye connects to your existing website and product data. You don't host a new feed endpoint. You don't implement a new checkout API. You don't change your fraud rules. There is no engineering work on your side.
Step 2 — Orders. Your catalog becomes accessible to the agent surfaces and apps in Rye's network. As demand matches your inventory, orders route through Rye's infrastructure to you as the fulfillment destination. You stay merchant-of-record. You keep the customer, the data, and the post-purchase relationship.
Step 3 — Operate. You fulfill agent-initiated orders like any other order, observe which categories pull demand, and refine fulfillment for the new traffic mix. Your brand stays in your control throughout.
Compare that to the direct-protocol path. Shopify Engineering's own blog on building UCP — the protocol Shopify co-developed with Google — estimates 4–6 weeks for basic production deployment, 4–8 weeks for Shopify pilots, and 6–12 weeks for Magento pilots. Legacy retailers can't even start the clock: Shopify notes UCP "requires a level of API maturity that many legacy retailers lack." And that engineering investment only buys you access to Google's surfaces. Not ChatGPT. Not the next agent ecosystem that launches next quarter.
How to Evaluate Any Agentic Commerce Platform: A 6-Criterion Rubric
Take this into any vendor conversation. It works for Rye. It works for whoever you're evaluating against Rye. Any vendor that can't answer these six questions cleanly isn't ready to serve you.
1. What's the true technical lift on my side?
Ask: "How many engineering weeks until we receive our first agent-initiated order? What do we have to build, staff, and maintain?"
This is where differences are largest and where marketing is most misleading.
Google UCP is marketed as "low-lift." In practice: 4–6 weeks to production best case, 4–8 weeks on Shopify, 6–12 weeks on Magento. The "3 REST endpoints" line conceals real-time inventory sync, webhook-based order management, tokenized payment flows, JWT session tokens, idempotency, replay protection, SLO targets, and Merchant Center approval.
OpenAI ACP (non-Shopify) requires a product feed endpoint with daily updates, 5 REST checkout endpoints, a Stripe integration using Shared Payment Tokens, and passing OpenAI conformance tests.
Stripe Agentic Commerce Suite is "low-code" — if you're already on Stripe and willing to connect a catalog feed.
Google AP2 is an enterprise engineering program: middleware, orchestration layers, Verifiable Digital Credentials, PCI-DSS reconciliation. Months to quarters.
Rye — zero engineering weeks on the brand side. No endpoints, no conformance tests, no SLO commitments. Rye connects to your existing site and catalog; you stay focused on fulfillment.
2. Do I stay merchant-of-record?
Ask: "After the sale, who owns the customer, the data, and the post-purchase relationship?"
This criterion matters more in agentic commerce than it did in traditional e-commerce, not less. Agent-driven traffic strips away most of the behavioral signal layer brands rely on today — no first-party cookies, no session replay, no pixel-based attribution. The customer relationship you preserve post-purchase is the only one you get.
Amazon Buy for Me routes the relationship through Amazon. Brands have publicly complained about being opted in without consent.
Google UCP explicitly preserves merchant-of-record. Credit where due — this matches Rye on paper.
ACP varies by flow.
Rye — you stay merchant-of-record. Full control of the customer, returns, and lifecycle comms.
3. How many ecosystems does one integration cover?
This is the criterion most merchants miss until they're three months in.
A single protocol integration only buys you one ecosystem.
Building UCP gets you Google AI Mode and Gemini.
Building ACP gets you ChatGPT and its partners.
Building to Amazon's feed gets you Amazon.
None of these overlap. If you want coverage across the agentic landscape, you integrate each protocol separately — then maintain each one as its spec evolves. That's three independent engineering projects, three vendor relationships, three SLO commitments, and three ongoing maintenance burdens. And that coverage doesn't extend to new agent ecosystems as they launch.
This is already how the biggest platforms are treating the landscape. Shopify co-developed UCP with Google and is a launch partner for ChatGPT's agentic commerce integration — not because Shopify couldn't pick one, but because each protocol only covers a single ecosystem, and a platform with Shopify's reach needs both to serve its merchants. If Shopify has to build both, you have to cover both (or more) to reach your own customers. Most brands don't have the engineering bench to build and maintain multiple protocol integrations in parallel.
Rye is one integration that covers corporate and creator gifting platforms, rewards and loyalty networks, card issuers and agent payment platforms, social commerce apps, cross-border marketplaces, and Rye's own ChatGPT integration. One hookup, every surface Rye serves. When Rye adds a new agent integration, brands on the network inherit it automatically — no rework, no new engineering.
4. What's the real order reliability number?
Ask for the SLA. Most vendors won't put a number on it.
Rye: 90%+ order reliability on browser-automated flows. In a published customer example, Throne — which routes creator-gifting volume through Rye's APIs — reduced order cancellations by 50% after moving to Rye's infrastructure.
Raw protocols: Demos that look great at product discovery regularly fall over at payment because fraud systems optimized to block bots also block legitimate agents. It's the exact problem Lithic and Arcade partnered with Rye to solve in production, per their published case study.
5. How fast is checkout? Will agents time out?
Agents are latency-sensitive. A 60-second checkout loses the sale.
Rye: 10-second checkout latency, sub-35-second offer resolution, 99.9% API uptime.
Legacy checkout paths routinely miss this bar and get abandoned mid-session.
6. How does it handle fraud without breaking your existing stack?
Agents look like bots to fraud systems. If your fraud vendor blocks them, you lose the order. If you whitelist indiscriminately, you eat the fraud.
Rye is integrated with Forter and Kasada and uses a trusted-agent model. Your existing fraud rules don't have to be rewritten.
Raw protocols leave this to you. Most merchants end up whitelisting IP ranges and hoping.
Three Reasons 400+ Brands Are on Rye
Three things, in order of importance:
1. Zero engineering work on the brand side. Not "low-code." Not "minutes if you're on Shopify." Not "4 weeks with a mature API team." Zero. Rye connects to your existing site and catalog; you keep doing what you already do.
2. One relationship, multiple surfaces. Rye maintains a single point of integration across the channels already in its network — corporate and creator gifting platforms, rewards and loyalty networks, card issuers and agent payment platforms, Rye's native ChatGPT integration, and more. You don't have to predict which protocol wins, and you don't have to build and maintain three of them in parallel.
3. You keep everything. Merchant-of-record status. Customer relationships. Brand control. Grayson Hogard, founder of Grove Cookie Company, put it plainly: "Working with Rye has been a huge asset for our small business. We have experienced other technology partners in the same realm as Rye who make it extremely difficult to integrate, do business with, and communicate with. Rye has been the exact opposite of that. Plus, we get a lot of orders, which is always good."
Frequently Asked Questions
Does joining Rye require any engineering work on my side?
No. Rye connects to your existing website and catalog — no new feed endpoints, no checkout API implementation, no conformance tests, no SLO commitments. This is the single biggest contrast with direct-protocol paths like Google UCP or OpenAI ACP, which each require building and maintaining multi-endpoint integrations on your side.
Do I stay merchant-of-record when agent orders come through Rye?
Yes. You retain full control of the customer relationship, customer data, returns, and all post-purchase communication. This is different from Amazon's Buy for Me, which routes the customer relationship through Amazon. Google UCP also preserves merchant-of-record — but unlike UCP, Rye requires no engineering lift to receive those orders.
Which AI agents and shopping apps will actually send orders to my brand?
Rye's largest demand channel today is corporate and creator gifting platforms routing volume through Rye's APIs — including Thnks (one of the most recognized corporate gifting platforms in B2B), Throne (creator gifting), and Gift Drive (nonprofit donations). Rewards and loyalty networks — including Bilt Rewards — let members redeem points against merchant products through Rye. Card issuers and payment platforms building for AI agents — including Lithic (in partnership with Arcade) — use Rye to execute agent-initiated checkout. Rye is additionally live inside ChatGPT via its own MCP-based shopping tool. Across the full network, 120,000+ orders per month flow through Rye.
How long does it take for a brand to go live on Rye?
There's no engineering project on the brand side — Rye connects to your existing website and catalog, so the timeline depends on fulfillment readiness and Rye's onboarding cadence, not on code you have to write. Compare that to Shopify Engineering's own UCP estimates of 4–6 weeks for basic production deployment and 6–12 weeks on Magento — and those are the engineering timelines for a single ecosystem.
How is Rye different from integrating directly with UCP or ACP?
Three things. First, integrating with a protocol is engineering work on your side; joining Rye isn't. Second, each protocol only covers one ecosystem (UCP = Google, ACP = ChatGPT), while Rye covers every major agent surface with a single relationship. Third, Rye handles fraud partner integrations (Forter, Kasada), order reliability, and checkout latency as part of the platform — with a protocol integration, you own all of those yourself.
What happens to my existing fraud rules?
They don't have to change. Rye is integrated with Forter and Kasada and uses a trusted-agent model that lets legitimate AI agents complete transactions without getting blocked by bot-detection systems. Merchants receiving orders through Rye don't have to rewrite their fraud stack.
Zero Engineering. One Network. Multiple Channels.
400+ brands are connected to Rye's supply network. 120,000+ orders per month flow through Rye today — driven by corporate and creator gifting platforms, rewards networks, card issuers and payment platforms building for AI agents, and Rye's native agent integrations. Joining the network doesn't require a single engineering week on your side. See how to get started:
New to the topic? Start with our primer on agentic commerce for merchants.