Agent Ready Crawlers

The field guide to every AI crawler and agent at the door, and the vendors who decide who gets in.

Browsing agent from Browser Use

Browser Use (library and cloud)

In short

Browser Use (library and cloud) is Browser Use's browsing agent. Browser Use has no robots.txt token, so robots.txt cannot address it and the crawl cannot measure a block rate. The operator publishes nothing a site can check. Browser Use says its cloud created 3.7M sessions in the seven days to 2026-10-14 (vendor figure via Verisoul).

Operator
Browser Use Vendor profile: Browser Use
Purpose
Task agent All task agent rows. A browsing agent that clicks, fills forms and finishes a job for a person.
User-agent string
No exact string is published. What the operator or a third party says: Chromium driven over the DevTools Protocol; Verisoul reports it names itself only in some setups
robots.txt token
None. No robots.txt line can address this agent.
Respects robots.txt

No documentation

operator publishes no bot documentation (checked 2026-11-04) for site owners; the library itself does not apply robots.txt. Source, read 2026-11-04.

Operator publishes no bot documentation (checked 2026-11-04).

Verification

Nothing published

The operator publishes no list, reverse DNS pattern or key directory a site owner can check. Documentation, read 2026-11-04.

IP ranges
Not published.
Rate behaviour
Set by the developer.
Block rate

None: the agent has no token, so a robots.txt block rate does not exist.

Documentation
Operator publishes no bot documentation (checked 2026-11-04). Closest page read.

Note. MIT-licensed. Browser Use says its cloud created 3.7M sessions in the seven days to 2026-10-14 (vendor figure via Verisoul). No key directory at browser-use.com (404, 2026-11-04).

Allow and refuse lines

This agent has no robots.txt token, so there are no lines to copy. Without a token, a published list or a signature, a site owner cannot tell it from an ordinary visitor by request alone.

Refusing or allowing in robots.txt states a preference. For this row the operator or its documentation says robots.txt may not govern the fetch, so enforcement belongs in your WAF.

Browser Use in the Verification Ledger

Publishes nothing for site owners (no key directory at browser-use.com, 404, 2026-11-04). All operators.

IP lists
publishes nothing
Reverse DNS
publishes nothing
Key directory
publishes nothing
Cloudflare
not checked
Visa TAP registry
no public operator-level registration found (checked 2026-11-04)
Mastercard Agent Pay
no public operator-level registration found (checked 2026-11-04)

Sources

Last reviewed 2026-11-04