How teardrop.dev treats AI agents
teardrop.dev 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 teardrop.dev block AI bots?
No. teardrop.dev is open to AI agents.
Does teardrop.dev need JavaScript?
No. The page has real content without JavaScript.
Does teardrop.dev have an llms.txt?
Yes, at /llms.txt.
Does teardrop.dev use a bot wall?
No bot wall was seen.
How should an agent fetch teardrop.dev?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/teardrop.dev. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.