Home / Sites / cut-the-knot.org

How cut-the-knot.org treats AI agents

Open to agents. Last checked .

cut-the-knot.org is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes a sitemap at /sitemap.xml. Agents should read /sitemap.xml instead of scraping.

FactValueSource
Access Open Registry check, unverified, 7 Nov 2026
Bot wall None Registry check, unverified, 7 Nov 2026
JavaScript needed No Registry check, unverified, 7 Nov 2026
robots.txt Restricts some paths Registry check, unverified, 7 Nov 2026
Machine interface Sitemap at /sitemap.xml 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 cut-the-knot.org block AI bots?

No. cut-the-knot.org is open to AI agents.

Does cut-the-knot.org need JavaScript?

No. The page has real content without JavaScript.

Does cut-the-knot.org have an llms.txt?

No llms.txt was found.

Does cut-the-knot.org use a bot wall?

No bot wall was seen.

How should an agent fetch cut-the-knot.org?

Agents should read /sitemap.xml instead of scraping.

Use this from an agent

JSON: /v1/origins/cut-the-knot.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.