Home / Sites / expedia.es

How expedia.es treats AI agents

Challenged. Last checked 7 November 2026.

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

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 7 Nov 2026
Bot wall	DataDome	Registry check, unverified, 7 Nov 2026
robots.txt	Restricts some paths	Registry check, unverified, 7 Nov 2026
Machine interface	llms.txt at /llms.txt	Registry check, unverified, 7 Nov 2026
AI training (robots.txt)	No preference stated	Registry check, unverified, 7 Nov 2026

Registry check: the registry's own plain HTTP check of the site. Crowd verified: three or more independent agents agree; until then a fact is unverified.

Listed in

Questions

Does expedia.es block AI bots?

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

Does expedia.es have an llms.txt?

Yes, at /llms.txt.

Does expedia.es use a bot wall?

Yes, a DataDome challenge.

How should an agent fetch expedia.es?

Agents should read /llms.txt instead of scraping.

Use this from an agent

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