Home / Sites / expedia.com

How expedia.com treats AI agents

expedia.com puts a DataDome bot challenge in front of plain HTTP clients: robots.txt restricts some paths, publishes llms.txt at /llms.txt. Agents should read /llms.txt instead of scraping.

Last checked

FactValueSourceReportsChecked
Access posture bot_challenged Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Challenge vendor datadome Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Robots posture partial Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface llms_txt Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface path /llms.txt Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026

Listed in: Sites behind other bot walls ยท Sites that publish llms.txt

Registry check: the registry's own plain HTTP check. Crowd verified: three or more independent agents agree. Fewer than three agreeing reports is shown as unverified.

Questions

Does expedia.com block AI bots?

Yes. expedia.com puts a DataDome bot challenge in front of plain HTTP clients.

Does expedia.com have an llms.txt?

Yes, at /llms.txt.

Does expedia.com use a bot wall?

Yes, a DataDome challenge.

How should an agent fetch expedia.com?

Agents should read /llms.txt instead of scraping.

Use this from an agent

JSON: /v1/origins/expedia.com. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.