Rye

75M+ x402 transactions in the last 30 days. $24M+ in volume. Almost none of it for physical products. Today, that changes. We're partnering with AgentCash to bring native x402 payments to physical commerce. AgentCash's MCP wallet is now the preferred client for x402 on Rye's Universal Checkout API. → One install. One wallet. Buy across 15,000+ merchant sites. → USDC on Base, Solana, and Tempo — signed over HTTP, no card vault, no PCI surface. → The wallet signature is the credential. No payment provider account to maintain. → x402.rye.com is live in production today. AgentCash is the client. Rye is the checkout. x402 is the rail. https://lnkd.in/gR74_DTS

Agentic commerce is three problems, not one. Identity. Payments. Checkout execution. Pull any one out and the loop breaks. An agent with a verified identity and no execution layer is a trusted visitor stuck on page two of checkout. An execution layer without identity is a session that dies at the WAF before it ever sees the cart. Skyfire and Rye just closed that loop. KYA rides along with every Rye Universal Checkout request. The merchant edge verifies it. Universal Checkout completes the purchase with tokenized payment and per-agent spend controls. One integration. Thousands of merchants. Read our Co-Founder Craig DeWitt on how the architecture fits together: https://lnkd.in/gSp2deFw

For 30 years, merchant security has been built around one goal: keep bots out. AI agents break that assumption — and merchant fraud systems can't tell the difference between a scalper and a customer's AI assistant. The agents that make it through? The ones carrying verified credentials. We're partnering with Skyfire to make that the default. Skyfire's Know Your Agent (KYA) is now the identity layer underneath Rye's Universal Checkout API. → KYA gives agents a cryptographically signed identity chain — tying the traffic, the agent instance, and the human principal together → Already recognized natively by F5 Distributed Cloud Bot Defense (80%+ of the Fortune Global 500) → Developers integrate Rye. One SDK. Verified identity attached at the merchant edge automatically. → Both layers running in production today. Not a roadmap. Identity gets the agent past the door. Universal Checkout completes the purchase. Full stack, single integration. https://lnkd.in/gBVjcFbH

Agents can now pay over HTTP. 75M+ x402 transactions in the last 30 days. $24M+ in volume. Stripe, Cloudflare, Amazon Web Services (AWS), and Vercel — all building around it. Stablecoins for APIs, compute, and digital services. No accounts. No card vaults. No credentials to rotate. Almost none of those transactions were for physical products. Rye is closing that gap. Announcement soon.

Rye's checkout API is three calls. Product URL in, confirmed order out. Our SDK wraps those three calls with everything production actually needs: automatic retries with backoff, idempotency keys on every mutation, polling helpers that replace hand-rolled loops, typed errors with recovery paths. No duplicate charges. No silent failures. No state machines for your team to maintain. Available in TypeScript, Python, Ruby, and Java. The standard we've landed on for agent-era infrastructure: small API surface, aggressive SDK defaults, production hardening baked in at the client layer. Full post: why we built an SDK for a three-endpoint API. https://lnkd.in/gVaB92qg

Rye's checkout API is three calls. Product URL in, confirmed order out. Our SDK wraps those three calls with everything production actually needs: automatic retries with backoff, idempotency keys on every mutation, polling helpers that replace hand-rolled loops, typed errors with recovery paths. No duplicate charges. No silent failures. No state machines for your team to maintain. Available in TypeScript, Python, Ruby, and Java. The standard we've landed on for agent-era infrastructure: small API surface, aggressive SDK defaults, production hardening baked in at the client layer. Full post: why we built an SDK for a three-endpoint API. https://lnkd.in/gVaB92qg

Agentic commerce is here.

Agentic checkout has retries, rollbacks, and pauses for browser agents baked into every order. Stitching that together with queues, webhooks, and custom state management is how you get silent failures at 2 AM. We moved the entire checkout workflow onto durable execution. One function. Each step is atomic, retriable, and persisted by the runtime. Agent fallback is a single suspend-resume call. Rollbacks are just another step. Full post: architecture, code sample, and the lessons we'd tell our past selves. https://lnkd.in/g-jAq6jk

Most agentic commerce in 2026 is still announcements and demos. Rye is in production. Build on Rye today.

We build agentic commerce infrastructure. We also build it with agents. Claude Code is embedded in our daily engineering workflow across three patterns: → Building — we encode repeatable workflows as Claude Code skills. Our hero, `/fix-product-data-extraction`, turns a failed scrape into a verified, tested PR with one command. → Investigating — Claude stitches together logs across four systems during incidents, correlating signals and building a working hypothesis in minutes instead of an afternoon. → Operating — `/i-hate-pushups` (yes, that's what we call it) keeps our Linear board aligned with our open GitHub PRs. Housekeeping eats engineering hours. We reclaimed them. A few rules we've landed on: → Goal-based prompting beats spec-based prompting. Give Claude an outcome, not a procedure. → Encode the loop, not the task. A one-off fix is a prompt. A workflow you keep running is a skill. → Verification is non-negotiable. Every skill we trust has a built-in "did this actually work?" step. We build Rye with agents because we built Rye for agents. If you're building with one, point it at Rye. https://lnkd.in/gfnmwmxW