Exa AI

Operator

See operator's docs

Verification

ExaUser

robots.txt token

No

Honours robots.txt

What ExaUser is

Exa fetching a page live when a user or an Exa API application asks for it; not used for crawling.

Its robots.txt token is ExaUser , but it is not listed as honouring robots.txt. Operator documentation: Exa AI .

Verifying it yourself

WebDecoy has no published IP list or reverse DNS hostname on file for ExaUser. Check Exa AI's documentation for one, such as a list of addresses or signed requests. Until you can check the source address, the User-Agent is only a claim, and copying a User-Agent costs nothing.

Blocking it

You can ask in robots.txt, but it is not listed as honouring it:

User-agent: ExaUser
Disallow: /

robots.txt only works on a client willing to obey it, which rules out every request that was already lying about who it is. Stopping those takes enforcement at the network or application layer, keyed on something the client cannot simply retype. That is the problem WebDecoy exists to solve.

Frequently Asked Questions

What is ExaUser? +

ExaUser is an ai assistant operated by Exa AI. Exa fetching a page live when a user or an Exa API application asks for it; not used for crawling.

How do I verify ExaUser? +

WebDecoy has no published IP list or reverse DNS hostname on file for ExaUser. Check Exa AI's documentation for one; until you can check the source address, the User-Agent is only a claim.

How do I block ExaUser? +

It is not listed as honouring robots.txt, so a Disallow rule for ExaUser may be ignored. Block it at your firewall, CDN or application instead, after verifying which requests really come from Exa AI.

See which ExaUser requests are real

WebDecoy verifies declared crawlers against what their operators publish and identifies the ones that fail, as persistent actors rather than disposable IPs.

Start Free Trial