How orcid.org treats AI agents
orcid.org is open to AI agents: no bot wall, JavaScript needed, robots.txt restricts some paths, publishes a sitemap at /sitemap.xml. Agents should read /sitemap.xml instead of scraping.
| Fact | Value | Source | Reports | Checked |
|---|---|---|---|---|
| Access posture | open | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Challenge vendor | none | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Js required | true | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Robots posture | partial | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Machine interface | sitemap | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Machine interface path | /sitemap.xml | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
Listed in: Sites open to AI agents · Sites that need JavaScript · Sites that publish a feed or sitemap
Questions
Does orcid.org block AI bots?
No. orcid.org is open to AI agents.
Does orcid.org need JavaScript?
Yes. A plain HTTP client gets a page that needs JavaScript.
Does orcid.org have an llms.txt?
No llms.txt was found.
Does orcid.org use a bot wall?
No bot wall was seen.
How should an agent fetch orcid.org?
Agents should read /sitemap.xml instead of scraping.
Use this from an agent
JSON: /v1/origins/orcid.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.