Circuit & Chisel vs Rye (2026)

A catalog of pay per call MCP servers gives an agent web search, crawl, X live search, a filestore, image, music and video generation, sandboxed code execution, contact lookup, x402 payments and email it sends and receives from its own address. The ATXP client can call any ATXP enabled MCP server, and developers can put their own MCP servers behind per call payment.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Tools, Email, Monetize MCP Tools, @atxp/client)read 2026-09-25

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

ATXP gives an agent an account, a wallet, a model gateway and paid tools. The agent's own framework, such as Vercel AI, Cloudflare Agents, LangChain, CrewAI or the OpenAI Agents SDK, decides the steps. ATXP manages the payment lifecycle and names no workflow model of its own.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Build Agents, SDK overview)read 2026-09-25

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

Work reaches ATXP only when the agent calls the gateway or a tool. Each agent has an inbox at its own address, and the agent checks it on request. ATXP names no event, webhook or schedule that starts the agent when mail arrives.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Email, CLI)read 2026-09-25

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

The search, crawl and X search tools query the public web, not the customer's corpus. The filestore keeps files but does not index them for retrieval. ATXP names no retrieval structure over the customer's knowledge.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Tools)read 2026-09-25

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

The Filestore MCP server lets an agent store, retrieve and delete files under its own account, and its inbox keeps mail it can read later. That way an agent can carry material from one session to the next. ATXP states no scope, lifetime or review surface for what the agent keeps.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Filestore, Email)read 2026-09-25

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

Pre funded credits (IOU tokens) set a structural ceiling on what an agent can spend. The ATXP client takes an approvePayment callback that runs before each payment, which the developer can use to auto approve small amounts and send larger ones for confirmation. The confirmation step itself is the developer's code, and ATXP names no approval screen of its own.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (@atxp/client) and atxp.ai/llms.txt (IOU tokens and spending limits)read 2026-09-25

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

Each agent gets its own account with a connection token, a wallet and an email address, which keeps credentials separate for each agent. ATXP names no roles, SSO or permissions for the account portal, and no attestation or trust page is published.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Agent quickstart, CLI, troubleshooting)read 2026-09-25

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

The npx atxp transactions command lists an account's recent payments, and the account portal shows usage and balance. The client's onPayment and onPaymentFailure callbacks let a developer record each payment. These report what was paid for, one payment at a time, and ATXP names no view of an agent's steps or tool calls as a run.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (CLI, @atxp/client, Account Portal)read 2026-09-25

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

The gateway (llm.atxp.ai), tools and accounts run as ATXP's hosted service. No hosting region is published, and ATXP names no option to run in the customer's environment. The Redis and SQLite packages store OAuth tokens for a developer's own paid MCP server, which the developer deploys.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (@atxp/redis, @atxp/sqlite, LLM Gateway)read 2026-09-25

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

ATXP offers no prebuilt agents or templates for a customer to adopt. The ATXP Skill gives an existing agent access to the paid tools as a tool bundle. The consumer apps atxp.chat, atxp.music and atxp.pics are built for people, and clowd.bot (beta) hosts OpenClaw, an open source runtime ATXP did not build.

SourceATXP by Circuit & Chisel, atxp.ai and docs.atxp.ai llms-full.txt (ATXP Skill)read 2026-09-25

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

The caller chooses the model. ATXP's LLM Gateway at llm.atxp.ai/v1 is OpenAI compatible and serves GPT, Claude, Gemini, Llama, Qwen and other models from a published catalog with per token pricing. Each request names its model, and desktop apps such as Goose use the gateway as a provider.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (LLM Gateway, Available models and pricing, Use the LLM Gateway in apps)read 2026-09-25

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

SDKs and a CLI drive ATXP itself. The API reference covers the @atxp/client, server, express, base, common, redis, sqlite and solana packages. The CLI registers and funds agents, checks balances, lists transactions and calls tools. The gateway is an OpenAI compatible HTTP endpoint, and the docs are served as an MCP server. SDKs and reference servers are published at github.com/atxp-dev.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (API Reference, CLI) and docs.atxp.ai/llms.txtread 2026-09-25

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

ATXP covers accounts, payments, a gateway and tools, and names no way to test or score agent output. The company's Pareto benchmark harness on GitHub belongs to Unbiased, its separate model product.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt and circuitandchisel.comread 2026-09-25

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

The Crawl tool fetches web pages as one of the paid tools, and the code tool runs code in a sandbox. ATXP names no agent that operates a browser or desktop.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Crawl, Code)read 2026-09-25

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