curl -s https://www.pathwren.workers.dev/crawler/exasearchbot.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

ExaSearchBot

Exa · AI search crawlers · json

User-agent: ExaSearchBot
Disallow: /


robots.txt token	`ExaSearchBot`
User-agent contains	`ExaSearchBot`
Operator	Exa
Category	AI search crawlers
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Exa's crawler. It discovers and indexes public pages so they can be retrieved and cited through Exa's search API, which is one of the common retrieval backends behind agent frameworks.

What blocking it costs you

Agents built on Exa's API stop finding you. Exa publishes no statement about robots.txt compliance, so treat the rule as a request.

Full user-agent string

ExaSearchBot

Allow it instead

User-agent: ExaSearchBot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=exasearchbot&s=client-dossiers'

/tools/verification-methods?crawler=exasearchbot
How do I prove a request really is ExaSearchBot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://exa.ai
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility