# ExaSearchBot

> 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.

| field | value |
|---|---|
| operator | Exa |
| category | AI search crawlers |
| robots.txt token | `ExaSearchBot` |
| user-agent contains | `ExaSearchBot` |
| robots.txt | operator publishes no robots.txt statement |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://exa.ai |
| last reviewed | 2026-09-14 |

## 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
```

## Block it

```
User-agent: ExaSearchBot
Disallow: /
```

## Allow it

```
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.

- **How do I prove a request really is ExaSearchBot?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=exasearchbot&s=client-dossiers'`  
  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.

JSON: https://www.pathwren.workers.dev/crawler/exasearchbot.json · index: https://www.pathwren.workers.dev/llms.txt