openai.com
This site is essentially invisible to AI agents.
Partial results
Our scanner was blocked by this site's bot protection. Results are partial and the real score may be higher.
Note: real AI agents likely get blocked too.
Needs work (8)
GET /agents.md returned 403
agents.md is the primary self-description file AI agents look for when deciding how to interact with a site.
GET /llms.txt returned 403
llms.txt is the emerging convention for pointing LLMs at the most relevant content on a site.
GET /llms-full.txt returned 403
llms-full.txt provides an extended, unabridged version of llms.txt for agents that can handle more context.
GET /.well-known/mcp.json returned 404
An MCP server card at a well-known location lets agents discover tool/action interfaces automatically.
GET /.well-known/verified.md returned 404
Publishing /.well-known/verified.md is the strongest first-party signal that a site actively participates in agent-readiness self-attestation.
no x402 signals detected (probed /api paths, headers, agents.md)
x402 is an emerging standard for agent-native micropayments over HTTP 402. Early support signals forward-looking infrastructure.
HTTPS unreachable: 403
Agents should reach the site over HTTPS, and plain HTTP should redirect there so credentials and payloads are never sent in the clear.
homepage returned 403 to scanner user agent
If the homepage returns a 403 or a challenge page to a scanner-style user agent, real agents likely get blocked too.
Passed (2)
robots.txt does not block crawlers; no explicit AI-crawler directives found
robots.txt controls whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) can access your site at all.
/sitemap.xml is reachable and looks like a sitemap
A sitemap helps agents discover the full set of pages worth crawling or indexing.
Could not evaluate (4)
Could not evaluate: the homepage was blocked by bot protection
Could not evaluate: the homepage was blocked by bot protection
Could not evaluate: the homepage was blocked by bot protection
Could not evaluate: the homepage was blocked by bot protection
What this means for openai.com
- Your bot protection is turning AI agents away at the door. Nothing else on this list matters until they can get in.
- AI assistants answering questions in your category cannot read how openai.com wants to be used, so they cite competitors who declare themselves.
- Assistants that look for a plain-language summary of openai.com find nothing, so what they say about you is guesswork assembled from third-party pages.
- Agents that want your full content in one clean file have to crawl page by page instead, and most give up early.
- Agents can read openai.com but cannot interact with it. To them you are a brochure, not a service.
- Nothing proves openai.com is who it says it is, so an agent has no way to tell you apart from an impersonator.
- Agents that can pay for content and services have no way to pay you.
- Without clean TLS, most agents will refuse the connection outright.
Make openai.com agent ready
Displace implements every failing check above and re-verifies monthly. Beta rate EUR 990 flat (list EUR 1,900), first 10 sites only, includes the first 3 months of certification.
Or email hello@verified.md.