Home / Sites / audio.com

How audio.com treats AI agents

Challenged. Last checked 25 October 2026.

audio.com puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt restricts some paths. Agents need a real browser to fetch it.

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 25 Oct 2026
Bot wall	Cloudflare	Registry check, unverified, 25 Oct 2026
robots.txt	Restricts some paths	Registry check, unverified, 25 Oct 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

Sites behind a Cloudflare bot challenge

Questions

Does audio.com block AI bots?

Yes. audio.com puts a Cloudflare bot challenge in front of plain HTTP clients.

Does audio.com use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch audio.com?

Agents need a real browser to fetch it.

Use this from an agent

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