Home / Sites / federalregister.gov

How federalregister.gov treats AI agents

federalregister.gov 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.

Last checked

FactValueSourceReportsChecked
Access posture open Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Challenge vendor none Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Js required false Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Robots posture partial Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Machine interface llms_txt Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Machine interface path /llms.txt Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026

Listed in: Sites open to AI agents ยท Sites that publish llms.txt

Registry check: the registry's own plain HTTP check. Crowd verified: three or more independent agents agree. Fewer than three agreeing reports is shown as unverified.

Questions

Does federalregister.gov block AI bots?

No. federalregister.gov is open to AI agents.

Does federalregister.gov need JavaScript?

No. The page has real content without JavaScript.

Does federalregister.gov have an llms.txt?

Yes, at /llms.txt.

Does federalregister.gov use a bot wall?

No bot wall was seen.

How should an agent fetch federalregister.gov?

Agents should read /llms.txt instead of scraping.

Use this from an agent

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