Agent Ready
Live agent-readiness score for any public website

How AI-ready is any website?

Paste a domain. We probe six public, well-known signals — /llms.txt, /llms-full.txt, AI bot policies in robots.txt, /.well-known/ai-agent.json, /ai.txt, and /sitemap.xml — and return a score from 0 to 100. No mocks, no API keys, just live HTTP.

Index stats

Loading...

Leaderboard

# Domain Category Score Grade Last checked
Loading...

Last 7-day movers

Domains whose score changed since previous check

Gainers

  • Loading...

Losers

  • Loading...

How we score

Every signal is a single public HTTP GET against the candidate domain. No third-party API, no scraping, no mocks. Failed fetches contribute 0 to the score and the failure mode is recorded.

SignalMaxWhat we look for
/llms.txt25200 OK, text content, >100 bytes; +5 if it parses as Markdown with H1 + sections per the proposed spec.
/llms-full.txt10200 OK, text, >500 bytes.
AI bots in robots.txt253 points per distinct AI bot directive (GPTBot, ClaudeBot, anthropic-ai, OAI-SearchBot, Google-Extended, PerplexityBot, ByteSpider, CCBot, Applebot-Extended, Amazonbot, FacebookBot, cohere-ai, Diffbot, etc.). 5 if robots.txt exists but has no AI-bot directives.
/.well-known/ai-agent.json15200 OK, parses as JSON, has at least one of name, description, actions, endpoints, agents, tools, capabilities (Aiia spec).
/ai.txt10200 OK at /ai.txt or /.well-known/ai.txt.
Sitemap declared1515 if /sitemap.xml returns a valid <urlset> or <sitemapindex>; 9 if only declared via Sitemap: in robots.txt.

Refresh cadence: every 6 hours for tracked domains; live single-domain checks are rate-limited to 10/min and 60/hour per IP to keep costs sane and to be a polite citizen of the open web.