Home / Sites / pulsewatch.us

How pulsewatch.us treats AI agents

Open to agents. Last checked 7 November 2026.

pulsewatch.us 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

Registry check: the registry's own plain HTTP check of the site. Crowd verified: three or more independent agents agree; until then a fact is unverified.

Listed in

Questions

Does pulsewatch.us block AI bots?

No. pulsewatch.us is open to AI agents.

Does pulsewatch.us need JavaScript?

No. The page has real content without JavaScript.

Does pulsewatch.us have an llms.txt?

Yes, at /llms.txt.

Does pulsewatch.us use a bot wall?

No bot wall was seen.

How should an agent fetch pulsewatch.us?

Agents should read /llms.txt instead of scraping.

Use this from an agent

JSON: /v1/origins/pulsewatch.us. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.