Rye
Rye is agentic commerce infrastructure - a Universal Checkout API that turns any product URL into a completed order without redirecting the shopper. Developers pass a product URL and buyer details and receive price, tax, shipping and delivery estimates, then confirm with a tokenized payment method (Stripe, Basis Theory, pre-funded drawdown balance, or x402/USDC) to place the order across thousands of merchants including Shopify stores and Amazon. Rye combines AI browser automation with fraud-mitigation and caches successful flows as deterministic workflows, advertising 90%+ order reliability, sub-35s offer resolution, and 99.9% uptime. The platform ships official TypeScript, Python, and Java SDKs, HMAC-signed webhooks, a staging sandbox with test products and simulated shipment/return helpers, Rewards UI React components, and a returns/refunds lifecycle. Rye is an a16z portfolio company.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Rye the way a machine reads it — 47 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Rye scores 63.4/100 (strong), with a separate agent-readiness read of 38/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Rye's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/rye/"
title="Rye on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/rye.svg"
alt="Rye Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/rye/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/rye/"
title="Rye on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/rye/card.svg"
alt="Rye Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Rye
Each block below is one kind of artifact we hold for Rye. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Rye Betas API
The Betas API from Rye — 1 operation(s) for betas.
Rye Billing API
The Billing API from Rye — 6 operation(s) for billing.
Rye Brands API
The Brands API from Rye — 1 operation(s) for brands.
Rye Checkout Intents API
The Checkout Intents API from Rye — 6 operation(s) for checkout intents.
Rye Commissions API
The Commissions API from Rye — 2 operation(s) for commissions.
Rye Events API
The Events API from Rye — 3 operation(s) for events.
Rye Merchant Connectors API
The Merchant Connectors API from Rye — 1 operation(s) for merchant connectors.
Rye Orders API
The Orders API from Rye — 3 operation(s) for orders.
Rye Payment Gateways API
The Payment Gateways API from Rye — 1 operation(s) for payment gateways.
Rye Products API
The Products API from Rye — 4 operation(s) for products.
Rye Returns API
The Returns API from Rye — 2 operation(s) for returns.
Rye Shipments API
The Shipments API from Rye — 2 operation(s) for shipments.
Rye Test Helpers API
The Test Helpers API from Rye — 6 operation(s) for test helpers.
Scroll within the panel for all 13 ·
Postman Collections 13
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Universal Checkout Betas API
POSTMANScroll within the panel for all 13 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONUniversal Checkout Betas API
OPEN COLLECTIONUniversal Checkout Betas Billing API
OPEN COLLECTIONUniversal Checkout Betas Brands API
OPEN COLLECTIONUniversal Checkout Betas Checkout Intents API
OPEN COLLECTIONUniversal Checkout Betas Commissions API
OPEN COLLECTIONUniversal Checkout Betas Events API
OPEN COLLECTIONUniversal Checkout Betas Merchant Connectors API
OPEN COLLECTIONUniversal Checkout Betas Orders API
OPEN COLLECTIONUniversal Checkout Betas Payment Gateways API
OPEN COLLECTIONUniversal Checkout Betas Products API
OPEN COLLECTIONUniversal Checkout Betas Returns API
OPEN COLLECTIONUniversal Checkout Betas Shipments API
OPEN COLLECTIONUniversal Checkout Betas Test Helpers API
OPEN COLLECTIONScroll within the panel for all 14 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rye Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Rye Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Rye — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/rye · machine-readable index on apis.io
This is an independent, third-party profile of Rye, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.