Back to vendors
R

Rye

Also known as: Rye.com, Rye Universal Checkout, Sell Anything API

Visit site
Entry priceDeveloper plan at $149 per month including fifteen hundred orders, then $0.05 per additional order, with a thirty day free trialFull pricing detail

Agentic commerce infrastructure whose Universal Checkout API turns a product URL and tokenized payment into a placed order on the merchant's site, with a confirmation hold, price limits, and returns and product data APIs.

Rye is agentic commerce infrastructure. Its Universal Checkout API turns a product URL and a tokenized payment method into a placed order on the merchant's own site. A developer creates a checkout intent. RyeBot, Rye's web agent, retrieves the live offer with real price, tax and shipping, and the intent waits for confirmation so the shopper can see the final cost before anything is charged.

On confirmation Rye completes the checkout through AI browser automation and returns the order status, with a single step Purchase endpoint for fire and forget flows. Maximum price thresholds keep orders within budget, card data stays tokenized and never reaches the agent, and merchants remain merchant of record. Direct routes cover Amazon, Shopify and Best Buy, and the automation works across other web stores. Rye caches successful flows for speed. A Returns API files returns and tracks refunds, and a Product Data API reads product details from most product URLs.

The API has SDKs, webhooks, separate staging and production environments and a docs MCP server. Current limits include US only ordering (other regions on request for enterprise), physical goods, guest checkout and one product per checkout. The console has no team accounts, and Rye keeps a trust center at trust.rye.com.

Rye was founded in 2021 and moved into agentic commerce infrastructure in 2025.

Vendor details

Canonical URL

https://rye.com

Category

Agent infrastructure

Subcategory

Universal checkout execution layer for agentic commerce

Funding status

Not stated on the first party pages read.

Company status

independent

Use cases & customers

Primary use cases

Programmatic checkout for AI shopping and agent appsTurning any product URL into a completed orderProgrammatic returns and refunds for agentic commercePre purchase product data lookup across merchants

Target customers

Developers building AI shopping appsAgentic commerce platformsChat commerce and shopping assistant buildersGifting, procurement, and dropshipping tools

Deployment options

Cloud

Integrations

The Universal Checkout API places orders on any web store reachable by a product URL, with direct routes for Amazon, Shopify and Best Buy. Payments use tokenized cards from Stripe and other gateways. The Returns API files returns with merchants, and the Product Data API reads product details from URLs. SDKs for npm and pip, webhooks and a docs MCP server support integration.

In practice

An AI shopping app creates a checkout intent from a product URL, shows the shopper Rye's resolved price, tax and shipping, and confirms with a tokenized card to place the order.

An agent is allowed to buy only below a maximum price, so Rye places nothing that exceeds the budget.

A shopper returns an agent bought item through the Returns API and the app follows the return to the refund.

Agentic Index coverage score

5.0 / 14 capabilities · 36%

Integrations & Tool Calling Full

The Universal Checkout API places a real order on any web store reachable by a product URL, with direct routes for Amazon, Shopify and Best Buy (Best Buy after approval). It pays through tokenized cards from Stripe and other gateways and files returns with the merchant through the Returns API. The Product Data API reads product details from most product URLs.

SourceRye, rye.com/docs llms-full.txt (API Comparison, Submit Orders to Best Buy, Returns, Confirm checkout intent) and rye.comread 2026-09-25

Workflow Orchestration Partial

A Checkout Intent moves through a fixed lifecycle of retrieving_offer, awaiting_confirmation, placing_order and completed or failed. A single step Purchase endpoint runs offer retrieval, payment authorization and order placement asynchronously. The sequence is Rye's own checkout, and customers cannot compose steps, branches or agents.

SourceRye, rye.com/docs llms-full.txt (Checkout Intent Lifecycle, Single Step Checkout)read 2026-09-25

Knowledge Grounding & RAG Not documented

The Product Data API returns details for a product URL on request by looking up merchants' public pages. Rye describes no maintained index or retrieval structure over the customer's own knowledge.

SourceRye, rye.com/docs llms-full.txt (Product Data)read 2026-09-25

Human Oversight & Guardrails Full

A Checkout Intent stops at awaiting_confirmation once the live offer (price, tax, shipping) is ready. Rye holds the order and places nothing until the intent is confirmed with payment, so the shopper can see the final landed cost before the charge. The single step endpoint is the opt out for fire and forget flows. Maximum price thresholds mean an order is only placed within budget.

SourceRye, rye.com/docs llms-full.txt (Checkout Intent Lifecycle, Confirm checkout intent, Price Constraints)read 2026-09-25

Security, Identity & Governance Not documented

The Rye console does not support team accounts, and Rye suggests sharing one login through a password manager. There are no roles, and Google sign in only authenticates a single account. Payments are tokenized only, merchants stay merchant of record, and developers get PCI DSS scope reduction. Rye has a trust center at trust.rye.com.

SourceRye, rye.com/docs llms-full.txt (Account Registration, Team accounts), rye.com (Security and Compliance) and trust.rye.comread 2026-09-25

Observability & Auditability Partial

Each checkout intent and return exposes its current state through the API. Webhooks send thin event notifications with deterministic ids so the latest state can be fetched. Customers see where an order stands, and Rye describes no trace of what RyeBot did step by step on the merchant site.

SourceRye, rye.com/docs llms-full.txt (Webhooks, Checkout Intent Lifecycle, Returns)read 2026-09-25

Memory & State Persistence Not documented

Successful checkout flows are cached as deterministic workflows for speed, and the automation replays them mechanically. Promo codes are cached to cut cost. Rye describes no memory an agent keeps.

SourceRye, rye.com (home) and rye.com/docs llms-full.txt (Promo Codes)read 2026-09-25

Deployment & Data Residency Not documented

Rye runs as a hosted API. Staging and production are separate, isolated environments of that hosted service. Ordering is US only, with other regions on request for enterprise, and that limit covers where goods ship. Rye names no data residency or customer environment option.

SourceRye, rye.com/docs llms-full.txt (Environments, API Limitations)read 2026-09-25

Prebuilt Agents, Templates & Packs Not documented

Customers build with Rye's API primitives, and Rye ships no prebuilt agents. Example flows and tutorials (a chat storefront with Stripe in Next.js, an app built with Lovable) and a config that turns a coding assistant into a Rye integration helper are guides the customer builds from. Rye's products also include Rye in ChatGPT and Rye for OpenClaw, and Rye does not present either as an agent a customer adopts.

SourceRye, rye.com/docs llms-full.txt (example flows) and rye.com (products menu)read 2026-09-25

Triggers & Channel Coverage Not documented

A checkout starts when the developer's app creates or submits a checkout intent. Webhooks go outward to report state and do not start work.

SourceRye, rye.com/docs llms-full.txt (Checkout Intent Lifecycle, Webhooks)read 2026-09-25

Model Flexibility & Routing Not documented

The AI browser automation runs on models Rye selects and does not name. The customer calls a checkout API and never picks or routes a model.

SourceRye, rye.com (home) and rye.com/docs llms-full.txtread 2026-09-25

APIs, SDKs & MCP Extensibility Full

The public REST API covers checkout intents, purchase, products, returns and payment gateway tokenization credentials. It comes with an OpenAPI reference, API key auth, rate limits, error handling and staging and production environments. SDKs (checkout-intents for npm and pip), webhooks and a docs MCP server at docs.rye.com/mcp sit beside it.

SourceRye, rye.com/docs llms.txt and llms-full.txt (API reference, Authorization, Environments, Webhooks)read 2026-09-25

Testing, Debugging & Optimization Not documented

The staging environment lets a developer test an integration against Rye without real orders. Reliability and latency figures are Rye's own performance claims. Rye describes no way to evaluate the agent's behavior.

SourceRye, rye.com/docs llms-full.txt (Environments) and rye.comread 2026-09-25

Browser & Computer Use Full

RyeBot, Rye's web agent, retrieves offers and performs checkout flows on merchant sites on behalf of shoppers, so Rye's own agent drives real merchant checkouts. Merchants can allowlist it by its user agent. The AI browser automation, with fraud mitigation, works across any web store.

SourceRye, rye.com/docs llms-full.txt (RyeBot Allowlisting) and rye.com (home)read 2026-09-25

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Pricing

Developer plan at $149 per month including fifteen hundred orders, then $0.05 per additional order, with a thirty day free trial

monthly subscription with included order volume plus per order overage; separately per request pricing for x402 stablecoin payments

Trial available

What is public

Developer plan price, monthly credit, per order and per product fetch fees, the free trial and the Enterprise inclusions.

Billing mechanics

Monthly Developer subscription with $50 in credits, then $0.05 per order placed and $0.02 per product fetch; Enterprise volume pricing.

Cost watchouts

Per order and per product fetch fees sit on top of the monthly plan once the $50 credit is used, and third party platform costs pass through; x402 payments through AgentCash are priced per request separately.

Variable cost rationale

Cost scales directly with order volume: the Developer plan includes fifteen hundred orders and charges $0.05 per additional order, and on the x402 path each intent and confirmation carries a per request fee, with product price and payment processing passing through on top. Spend tracks transactions placed, so a busy agent's bill grows with usage.

Additional watchouts

The $149 plan covers fifteen hundred orders; product price and payment processing are separate pass through costs, so total spend depends heavily on order volume and average order value, not the subscription alone.

Sales call required

Mixed (some tiers require a call)

Free / trial

Thirty day free trial on the Developer plan

Lowest paid plan

Developer, $149/month

Key ambiguities

The plan changed since July: the 1,500 included orders are gone, replaced by $50 in monthly credits and per call fees.

Missing data

Enterprise tier rates and volume thresholds are not published, and per order economics at very high volume beyond the $0.05 overage are not detailed.

Agentic Index verified 2026-09-25

Alternatives to Rye

The closest documented capability profiles to Rye among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

  • Skyfire4.5 / 14Adds documented Security, Identity & Governance
  • Lightpanda6.0 / 14Adds documented Deployment & Data Residency and Model Flexibility & Routing
  • Browserless8.5 / 14Adds documented Security, Identity & Governance and Deployment & Data Residency, among others
  • Catalog4.5 / 14Adds documented Knowledge Grounding & RAG and Triggers & Channel Coverage
  • Circuit & Chisel4.5 / 14Adds documented Memory & State Persistence and Model Flexibility & RoutingRye vs Circuit & Chisel →
  • Kernel8.5 / 14Adds documented Security, Identity & Governance and Deployment & Data Residency, among others

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.