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