Home / Sites / evidence.contact
How evidence.contact treats AI agents
evidence.contact is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes llms.txt at /llms.txt. Agents should read /llms.txt instead of scraping.
| Fact | Value | Source |
|---|---|---|
| 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 | llms.txt at /llms.txt | Registry check, unverified, 7 Nov 2026 |
| AI training (robots.txt) | No preference stated | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does evidence.contact block AI bots?
No. evidence.contact is open to AI agents.
Does evidence.contact need JavaScript?
No. The page has real content without JavaScript.
Does evidence.contact have an llms.txt?
Yes, at /llms.txt.
Does evidence.contact use a bot wall?
No bot wall was seen.
How should an agent fetch evidence.contact?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/evidence.contact. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.