Browserbase
Browserbase and Anchor Browser: the cloud browsers behind many AI agents
Browserbase and Anchor Browser run cloud browsers for AI agents. What their traffic is, how to recognise signed sessions, and what store owners should do.
Fetches pages for a user
Anchor Browser provides cloud browser sessions that AI agents and automation tools control to browse websites, sign in to web apps and complete tasks. Each session is driven by one of Anchor's customers. When a customer turns on Web Bot Auth for a session, Anchor signs its requests so a site can verify they come from Anchor Browser.
Anchor Browser's docs do not say whether sessions read robots.txt. What a session visits is decided by the customer's agent.
Sill does not publish website figures for Anchor Browser.
Browserbase
Browserbase and Anchor Browser run cloud browsers for AI agents. What their traffic is, how to recognise signed sessions, and what store owners should do.
Check for a valid Web Bot Auth signature, usually through your CDN such as Cloudflare. Anchor signs requests only when a customer turns the option on for a session, and it does not document a fixed user agent or IP list for site owners.
Blocking the platform blocks every customer using it, including agents working for real people. A fairer rule is to allow sessions with a valid signature and judge the rest by behaviour, such as request rates.