Rye Is an Approved Agent in Stripe's Agentic Commerce Suite
Arjun Bhargava
Co-founder and CEO @ Rye
3 minutes read
Merchants on Stripe's Agentic Commerce Suite connect to Rye once and reach every app built on it.
TL;DR / Key Takeaways
Rye is now an approved agent in Stripe's Agentic Commerce Suite.
Merchants live on the Suite can connect their catalog to Rye directly through Stripe.
Once a merchant connects, its products become transactable across every application built on Rye's APIs — no new integration for the developer, no agent for the merchant to build.
Rye stays what it has always been: the checkout layer that completes the order.
Agentic commerce only works when two things are true at the same time. An agent has to reach a merchant's catalog, and it has to actually complete the purchase. Stripe's Agentic Commerce Suite, announced at Stripe Sessions, gives merchants a sanctioned way to make their products available to AI agents. Rye is now an approved agent in that Suite.
What the Agentic Commerce Suite is
The Agentic Commerce Suite is Stripe's connective layer between merchants and the agents that want to sell their products. A merchant enables the Suite, chooses which agents to work with, and Stripe handles the handshake — protocol-agnostic on the merchant's behalf. If you want the protocol detail underneath agentic checkout, we covered it in How to Implement UCP and What Is Agentic Checkout. For the category itself, start with our guide to agentic commerce.
Rye is now an approved agent inside it.
What being an approved agent unlocks
A merchant live on the Suite requests to connect its catalog to Rye through Stripe, and Rye approves the connection. The merchant initiates it and stays in control of who sells its products; Rye approves the merchants it works with.
From there, the merchant's products are available to Rye — and through Rye, to every developer building agentic commerce on our APIs. The merchant gets agent distribution without building or maintaining its own agent. The developer gets merchant-approved catalog and checkout coverage without standing up a new integration; the products simply become transactable through the same Universal Checkout API they already use.
One connection on the merchant side. Zero new work on the developer side.
Where Rye fits
Rye is the transaction layer. A developer's application or agent handles discovery — it decides what to buy and which merchant to buy it from. Rye completes the order through the Universal Checkout API: payment, real shipping and tax, and the order placed on the merchant.
Rye's role is the same. The Suite adds a sanctioned on-ramp for the merchants that want their catalog in front of agents, and extends Rye's coverage to every developer already building on it.
For developers building on Rye
Merchant catalogs that connect to Rye through the Suite become available through your existing integration. No code change.
You keep building discovery and the buying experience your users see. Rye completes the order underneath.
Coverage grows as more merchants enable the Suite and connect to Rye — without you wiring up each one.
Frequently Asked Questions
How does a merchant connect its catalog to Rye?
From the Agentic Commerce Suite, a merchant selects Rye as an agent it wants to work with. The connection is merchant-initiated, and once it's live the catalog is available to Rye automatically.
How does this relate to UCP or ACP?
The Suite is protocol-agnostic — Stripe handles whichever protocol a connection uses, and Rye works across them, plus the merchants that don't speak any protocol. For the protocol detail, see What Is Agentic Checkout.
Can a merchant work with other agents too?
Yes. Merchants on the Suite choose which agents to enable, and Rye is one option they can turn on alongside others.
Start building
Rye completes the order, wherever your agent finds it.
Universal Checkout API — rye.com/products/universal-checkout-api
Read the docs — rye.com/docs/api-v2/introduction
Get an API key — console.rye.com