What is RyeBot?
RyeBot is Rye's web agent for completing checkout flows on behalf of shoppers who have given explicit consent. Cloudflare classifies it as an agent in the AI assistant category, which fits its transactional purpose better than the label crawler.
Rye's allowlisting documentation says the agent retrieves offers and places orders. A visit can therefore move through product selection and checkout rather than stopping after a single page fetch. Developers adding shopping features through Rye's API do not need to allowlist the bot themselves; the guidance is written for merchants whose sites RyeBot visits.
This traffic is tied to a shopping task. Blocking it can prevent a consenting shopper's order from completing, while allowing it lets the merchant's normal catalog, fraud, inventory, payment, and account rules decide what happens next. A valid bot identity does not override those rules.
RyeBot does not build an AI search index, and its recorded purpose is not model training. Product access may affect whether a Rye-powered shopping experience can quote an offer or complete a purchase at that moment. It does not make the merchant more visible in general answer engines.
Rye documents RyeBot/1.0 inside a Firefox-style User-Agent string, with RyeBot as the stable token. Cloudflare's entry does not list a user-agent pattern or complete string, but it does publish Rye as the operator and points to the same allowlisting page. The text token is useful for logs and robots.txt, though another client can copy it.
RyeBot also signs requests through Web Bot Auth. Rye instructs sites to require the Signature-Agent value "https://rye.xyz", fetch the matching public key from https://rye.xyz/.well-known/http-message-signatures-directory, and verify the Signature header under RFC 9421. Cloudflare's bot directory marks followsRobotsTxt as false even though the bot's listing records true, so signature-aware edge policy is the firmer control.
