Rye

Agents take authenticated action in outside systems. 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), 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

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

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

No retrieval structure over the customer's knowledge. The Product Data API returns details for a product URL on request, which is a lookup of merchants' public pages, not a maintained index of the customer's corpus.

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

Rye holds the order until someone confirms it. A Checkout Intent stops at awaiting_confirmation once the live offer (price, tax, shipping) is ready, and Rye places nothing until the intent is confirmed with payment, so a buyer can see 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

There is no team access model: the docs say the Rye console does not support team accounts and suggest sharing one login through a password manager, so there is no role surface (Google sign in only authenticates a single account). The homepage's security points (tokenized payments only, merchants stay merchant of record, PCI DSS scope reduction for developers) are payment handling, not an attestation of Rye's own. A trust center sits at trust.rye.com, but its contents load only in a browser, so which attestations Rye holds is unconfirmed.

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

State per order, not a trace of the agent's work. Each checkout intent and return exposes its current state through the API, and webhooks send thin event notifications with deterministic ids so the latest state can be fetched. That shows where an order stands, not 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

Rye caches successful checkout flows as deterministic workflows for speed, but that is a replay cache the automation applies mechanically, not memory an agent keeps. Promo code caching is cost optimization.

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

Hosted API with no residency or customer environment option. Staging and production are separate, isolated environments of Rye's hosted service, not deployment choices; ordering is US only, with other regions on request for enterprise, which is where goods ship, not where data lives.

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

API primitives, not prebuilt agents. The docs give 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; those are guides the customer builds from. The site also lists Rye in ChatGPT and Rye for OpenClaw; neither is described as an agent a buyer adopts.

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

Work begins only when the caller asks: a checkout starts when the developer's app creates or submits a checkout intent, and webhooks go outward to report state without starting work.

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

No model choice. Rye's 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

A documented public API for Rye's own platform. The REST API (checkout intents, purchase, products, returns, payment gateway tokenization credentials) is published with an OpenAPI reference, API key auth, rate limits, error handling and staging and production environments, with SDKs (checkout-intents for npm and pip), webhooks, and a docs MCP server at docs.rye.com/mcp.

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

No evaluation surface. The staging environment lets a developer test an integration without real orders, which tests the customer's own code against Rye, not an agent's behavior; the homepage reliability and latency figures are the vendor's own performance claims.

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

Rye's own agent drives real merchant checkouts. RyeBot is Rye's web agent that retrieves offers and performs checkout flows on merchant sites on behalf of shoppers (merchants can allowlist it by its user agent), and the homepage describes AI browser automation with fraud mitigation working across any web store.

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