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