ExaUser

Exa uses ExaUser to fetch a page live when a user, or an application built on the Exa API, asks for its current content. ExaUser is not used for crawling the web in an automatic fashion; that is ExaSearchBot.

ExaUser is not used to determine whether content may appear in Exa search. Use ExaSearchBot in robots.txt to manage search opt-outs and automatic crawling.

User-agent

Mozilla/5.0 (compatible; ExaUser/1.0; +https://crawler.exa.ai/exauser)

Verification

Every request is signed with Web Bot Auth (RFC 9421) and is verified automatically on Cloudflare, Akamai, and other providers that support it. Keys are published at https://crawler.exa.ai/.well-known/http-message-signatures-directory.

How ExaUser behaves

robots.txt policy

Because fetches are initiated by a user, robots.txt rules may not apply.

Signs requests

So you can confirm a request is genuinely us.

Fetches on demand

Only when a user asks for a page; no scheduled or background crawling.

Public content only

It does not attempt to bypass logins, paywalls, or CAPTCHAs, and submits no forms.

Contact

Questions: support@exa.ai, ideally from an address at the domain you are asking about.