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