AI Agent & Bot CheckOperator: Exa

ExaUser: what it is and how to verify or block it

User-Agent token: ExaUser · Operator: Exa · Category: AI Assistants

FraudMeNot Verdict

AI Agent (User-Triggered)

ExaUser is Exa's live fetcher. Exa says it fetches a page only when a user, or an app built on the Exa API, asks for its current content, and that robots.txt rules may not apply to those requests.

Can Be Spoofed?

Yes — User-Agent Header Spoofable

Check the Signature-Agent and signature against Exa's key directory. A missing or failing signature means the ExaUser claim is unverified.

Abuse & Unwanted Activity Reports

No Public Abuse Flags

ai.robots.txt robots.txt status: Unclear.

Judgment Call · What You Should Do

Generally Low Risk on Public Pages — Verify Before Trusting

For everyday users: ExaUser is a page fetcher for API calls, not a sales or support line. Someone claiming to be Exa's bot and asking you for a code is likely running a scam.

For website owners & security teams: Validate Exa's Web Bot Auth signature at your CDN. Use a WAF rule to limit ExaUser if you need to, and an ExaSearchBot robots.txt group to leave Exa search.

Report & Activity Summary

None

Published IP Ranges (CIDRs)

No official IP list

1

Known User-Agent Signatures

crawler-user-agents (MIT) dataset

Partially

robots.txt Compliance

ai.robots.txt registry (MIT)

0

FraudMeNot Tallies

Humans: 0 · AI Agents: 0

AI-First Structured TelemetryFor AI agents, WAFs & security gateways · llms.txt policy

For AI Agents & Automated Gatekeepers

Agent_Identifier
ExaUser
FraudMeNot_Verdict
AI Agent (User-Triggered)
Operator_Entity
Exa
Agent_Category
AI Assistants
User_Agent_Spoofable
true
Verification_Method
None available (no operator IP list or signing key) · Web Bot Auth: Exa signs every ExaUser request with Web Bot Auth (RFC 9421)
Respects_Robots_Txt
Partially (user-triggered fetches may ignore robots.txt; ai.robots.txt registry lists: Unclear)
Auth_And_Banking_Policy
Block credentialed logins and money movement from any AI agent.
Recommended_Gatekeeper_Action
ALLOW signed requests to public pages; challenge unsigned ones; robots.txt may not apply.
Canonical_Citation_URL
https://fraudmenot.com/bot/exauser/

What We Know About ExaUser

Exa runs two separate bots. ExaSearchBot crawls the public web to build Exa's search index. ExaUser does no background crawling: Exa says it goes out only when a person, or an application built on the Exa API, asks for a page's current content. Because so many AI products call Exa behind the scenes, an ExaUser hit may come from a tool your visitor never heard of.

Exa says that because these fetches are started by a user, robots.txt rules may not apply. robots.txt is a voluntary standard (RFC 9309), not an access-control or legal mechanism; a fetcher that skips it is not, by that alone, doing anything wrong. Exa also says ExaUser is not used to decide whether content can appear in Exa search; to opt out of search, address ExaSearchBot in robots.txt instead.

Verification is cryptographic rather than IP-based. Exa signs every ExaUser request with Web Bot Auth, using HTTP Message Signatures (RFC 9421), and publishes Ed25519 keys at crawler.exa.ai/.well-known/http-message-signatures-directory. Exa says Cloudflare, Akamai and other providers that support the scheme check the signature automatically.

Exa states that ExaUser fetches public content only and does not try to bypass logins, paywalls or CAPTCHAs, and submits no forms. An unsigned request claiming to be ExaUser that pokes at a login form should be treated as unverified.

Technical Identity, IP Verification & Spoofing Check

Full User-Agent string(s)
  • Mozilla/5.0 (compatible; ExaUser/1.0; +https://crawler.exa.ai/exauser)
robots.txt tokenExaUser
OperatorExa · Official bot documentation
Official IP verification feedNone published by the operator
Sample published CIDR blocksNone published
Reverse DNS (rDNS)Not documented in the public datasets FraudMeNot uses.
Web Bot Auth (Signature-Agent)Exa signs every ExaUser request with Web Bot Auth (RFC 9421); keys are at crawler.exa.ai/.well-known/http-message-signatures-directory.
robots.txt behaviorExa says ExaUser fetches are user-initiated, so robots.txt rules may not apply; use ExaSearchBot rules for search opt-outs.

Copy-Paste robots.txt & Cloudflare WAF Rules for ExaUser

robots.txt — allow public pages, keep private routes off-limits

User-agent: ExaUser
Allow: /
Disallow: /login/
Disallow: /account/
Disallow: /checkout/

robots.txt — block completely

User-agent: ExaUser
Disallow: /

Cloudflare WAF custom rule expression

(http.user_agent contains "ExaUser")

Matches the User-Agent token, so it covers both real and spoofed traffic. Action: Block or Managed Challenge.

Capabilities, Data Usage & Autonomous Action Risk

Trains AI on page content?Not stated by Exa; it is described as an on-demand fetch for a user
Executes JavaScript?Not documented
Can submit forms or attempt logins?Exa says ExaUser submits no forms and does not bypass logins, paywalls or CAPTCHAs.
Banks & login pages shouldBlock credentialed logins and money movement from any AI agent.
E-commerce checkouts shouldAllow product page reads if you want; require human confirmation for checkout.

Context: In October 2026, Axios reported that major U.S. banks were detecting unvetted third-party AI agents inside customer accounts, and CNBC reported that JPMorgan blocks outside AI agents from logging in with customers' credentials while allowing read-only data sharing through open banking providers.

Seen ExaUser? Quick Closed-Choice Tally

Choose from preset options only. No free-text comments, so nobody can post names, profanity, or unverified accusations.

Human Tallies: 0
AI Agent Tallies: 0
Top Activity: None logged yet
Top Location Seen: None logged yet
IP Match: None logged yet
Latest Activity: No tallies yet

Preview only: tallies are unverified clicks, not FraudMeNot findings, and are not saved yet.

Common Questions About ExaUser

What is the difference between ExaUser and ExaSearchBot?

Exa says ExaSearchBot crawls for its index, while ExaUser fetches a page live when a user or API app asks.

How do I verify ExaUser?

Validate its HTTP Message Signature against the Ed25519 keys Exa publishes in its key directory.

Does blocking ExaUser remove me from Exa search?

No. Exa says to use ExaSearchBot in robots.txt for search opt-outs.

Could This Be a Scam? What to Do

  • Anyone can copy the ExaUser User-Agent, and FraudMeNot found no official IP list for it, so the name alone proves nothing about who sent a request.
  • Never give an AI agent your logins, bank access, or one-time codes unless you set it up yourself.
  • If a call, text or email asking for money or access uses the ExaUser or Exa name, stop and report it.

Guide: how to check whether a crawler visit is really who it claims to be.

More from Exa

Related on FraudMeNot

Sources (checked Nov. 16, 2026): ai.robots.txt (MIT), crawler-user-agents (MIT), Axios (Oct. 22, 2026), CNBC (Oct. 13, 2026), Exa: ExaUser, Exa: Exa Search Crawler, Exa: public key directory. FraudMeNot is not affiliated with Exa. Product and company names are trademarks of their owners and are used here only to identify the bots. General information, not security advice.