Short answer
Browserbase and Anchor Browser rent out cloud browsers that AI agents and automation tools use to visit websites. Their traffic comes from many different customers, not from one company's bot. Both can sign requests with Web Bot Auth so a site can verify them, but signing is an option the customer turns on, so unsigned sessions look like ordinary browser visits.
Key takeaways
- Both companies run real browsers in the cloud for other people's agents.
- Signed sessions can be verified; signing is opt-in per customer or session.
- A valid signature names the platform, not the customer driving it.
What are Browserbase and Anchor Browser?
Browserbase and Anchor Browser are companies that run web browsers in the cloud for other people's software. A developer building an AI agent rents a browser session, and the agent uses it to open pages, click, fill in forms and read the results, the way a person would.
Browserbase describes itself as "the complete platform to build and deploy agents that browse and interact with the web like humans." Its docs list headless browsers, web search, page fetching and an identity product among its services.
Anchor Browser's docs describe it as "cloud browser infrastructure for AI agents and automation." They list browser sessions that developers control, natural-language web tasks, managed sign-in to third-party web apps, and network options.
Why do cloud browsers matter to a store owner?
A visit from a cloud browser is usually an AI agent working for someone else. When you see Browserbase or Anchor Browser traffic, the company that runs the browser is rarely the one deciding what to look at. One of its customers is.
Cloudflare made the same point when it named both companies, with ChatGPT agent and Goose from Block, as the first cohort of "signed agents" in August 2025. It said they fit because "their remote browsers are used by their end customers, not necessarily the companies themselves."
The companies say this themselves. In the same post, Browserbase's CEO said: "At Browserbase, we provide web browsing capabilities for some of the largest AI applications." Anchor Browser's CEO said the company "has partnered with Cloudflare to let developers ship verified browser agents."
That matters for two reasons. The visit can be useful: an agent comparing products or completing a purchase for a real person. And a single platform carries many unrelated customers, so a rule against the platform hits all of them at once.
Cloudflare now describes this kind of service with an "Intermediary" label. Its verified bots docs define an intermediary as an agentic service that a wide range of end users can operate, and note that you may trust the operator "but not necessarily every end user driving it."
Can you tell Browserbase or Anchor traffic apart from normal visitors?
Only when the session is signed. Both platforms run real browsers, and neither documents a fixed user agent or IP list for site owners to match. A session that is not signed can look like an ordinary visitor.
Both companies also offer tools to get past bot defences. Anchor's docs offer residential proxies, "extra stealth" and CAPTCHA solving, and sum up one page as "Get past IP blocks, bot detection, and CAPTCHAs on automated browser sessions." Browserbase offers proxies, CAPTCHA solving and Verified sessions, which use "a purpose-built Chromium browser with real browser fingerprints that Browserbase's bot protection partners recognize." That recognition happens at those partners, not in a check you can run yourself.
So the reliable signal is a cryptographic signature.
How do Browserbase and Anchor Browser sign requests?
Both support Web Bot Auth, the draft standard for signing HTTP requests. A signed request carries Signature-Agent, Signature-Input and Signature headers, and the verifier fetches the operator's public keys to check it. Our guide to Web Bot Auth explains the mechanics.
The difference from a crawler like GPTBot is that signing is optional and set by the customer:
| Browserbase | Anchor Browser | |
|---|---|---|
| Web Bot Auth status | Beta, by request | Documented feature |
| How it is turned on | Browserbase enables it for the customer's account | web_bot_auth.active set to true per session (default false) |
| Fixed user agent documented | No | No |
| Published IP list for site owners | None documented | None documented |
Anchor says that with the option on, "All HTTP requests are automatically signed as Anchor Browser." Browserbase's identity docs say Web Bot Auth "gives participating websites a cryptographic identity signal for your browser traffic."
Neither company's docs give the Signature-Agent value or a key directory address for site owners to check against. Anchor's docs say Cloudflare validates the signatures, and in practice most site owners rely on their CDN, such as Cloudflare, to do the check.
What does a valid signature tell you, and what doesn't it?
A valid signature tells you the request really came through that platform. It does not tell you who the platform's customer is, or that a real person approved what the agent is doing.
Browserbase's docs are clear on this. They say a valid signature "proves that a holder of the corresponding private key signed the covered components," and that "Web Bot Auth doesn't establish a human user's identity, grant permission to act on their behalf, or replace a website's login flow." They add that the website still decides whether to trust that identity and what it can do.
In other words, a signature moves a visit from "unknown browser" to "a Browserbase session" or "an Anchor Browser session." Your normal rules for rate limits, logins and checkout still apply.
What should a store owner do about cloud browser traffic?
Treat the platforms as you would any signed agent: verify, then judge by behaviour.
- Allow verified sessions where it suits you. If your site is on Cloudflare, our guide to allowing AI agents through Cloudflare covers the settings. Our explainer on Cloudflare verified bots and signed agents covers the July 2026 change to labels.
- Don't block by platform name alone. Many different customers share each platform, and some of them are shopping for real people.
- Keep rate limits and login protection on. A signature does not replace them, as Browserbase's own docs say.
- Expect unsigned sessions too. Signing is opt-in, so some cloud browser traffic will reach you without any label.
How Sill helps
Sill shows which AI agents and bots visit your site and the pages they read. On Cloudflare and WordPress installs it verifies Web Bot Auth signatures from agents that sign, so a signed cloud browser session is marked as verified rather than guessed from its user agent. When an agent places an order, your rules approve it, decline it or hold it for a person to review. A free readiness scan shows how your site looks to agents.
Questions people ask
What is Browserbase traffic?
It is a real Chromium browser running on Browserbase's infrastructure, controlled by one of Browserbase's customers, often an AI agent. Browserbase itself is the platform, not the party deciding what to visit.
Should I block Browserbase or Anchor Browser?
Blocking the platform blocks every customer on it, including agents shopping for real people. A fairer rule is to allow verified signed sessions and judge everything else by behaviour, such as request rates.
Do Browserbase and Anchor Browser have a user agent I can match?
Neither documents a fixed user agent for site owners. Browserbase says picking an operating system for a Verified session changes the browser's user agent to match that platform.
Is Anchor Browser the same as Cloudflare Browser Rendering?
No. They are separate products. Cloudflare's August 2025 post named Browser Rendering alongside similar products from Browserbase and Anchor Browser.
Sources
- Browserbase docs: What is Browserbase? · checked 17 Nov 2026
- Browserbase docs: Agent Identity overview · checked 17 Nov 2026
- Browserbase docs: Web Bot Auth · checked 17 Nov 2026
- Browserbase docs: Verified · checked 17 Nov 2026
- Anchor Browser docs: Cloudflare Web Bot Auth · checked 17 Nov 2026
- Anchor Browser docs: Network and Stealth · checked 17 Nov 2026
- Cloudflare: The age of agents: cryptographically recognizing agent traffic · checked 17 Nov 2026
- Cloudflare docs: Verified bots · checked 17 Nov 2026