GEO · AI-agent utilities · 10 credits
AI Agent Readiness Checker & llms.txt Validator
Check whether AI browsers and agents can read and use a site, with each page attribute, llms.txt line or discovery file to fix.
AI Agent Readiness Checker 1.0.0 · price g38-v1 · retrieved at run time · Run it from an AI agent
Loading tool
What the AI Agent Readiness Checker checks
Check whether AI agents and browsers can read and use a site: llms.txt syntax and links, Lighthouse’s Agentic Browsing checks, WebMCP form coverage, Markdown responses for Accept: text/markdown, and MCP or A2A agent cards. Paste an llms.txt draft to validate it before it ships.
- llms.txt syntax and whether its links load
- Lighthouse's Agentic Browsing checks
- WebMCP coverage of the site's forms
- Markdown responses for Accept: text/markdown
- MCP and A2A agent cards
What it does not do
- Layout shift (use the Core Web Vitals Snapshot)
- A full accessibility audit
- Testing JavaScript-registered tools end to end
Questions about the AI Agent Readiness Checker
- What is llms.txt?
- llms.txt is a proposed Markdown file at the root of a site that gives language models a short summary and links to the pages worth reading. It is optional. Paste a draft here to validate it, or draft one with the llms.txt Generator.
- Why serve Markdown to AI agents?
- Some agents request pages with an Accept: text/markdown header because Markdown is shorter and cleaner to read than HTML. The checker tests whether your site answers those requests with Markdown.
- What are agent cards?
- Discovery files that describe what an AI agent can do on a site, published for the Model Context Protocol (MCP) or the Agent2Agent (A2A) protocol. The checker looks for them and reports what it finds.
- How much does the AI Agent Readiness Checker cost?
- 10 credits per run, shown before the run starts. An AI agent can run the same tool over the REST API or MCP with a workspace API key.
