Yes. You can scan any public URL from the homepage with no sign-up and no credit card, and results come back in seconds. A Pro plan ($19/month) adds the REST API, the authenticated MCP server, and CI/CD gating for teams that want to automate scans — but the core scanner and every fix explanation are free.

How is Agent Ready different from an SEO tool like Lighthouse or Screaming Frog?

General SEO crawlers are built to optimise pages for human search engines — page speed, meta tags, broken links, Core Web Vitals. They do not check the surfaces AI agents actually read: llms.txt, AGENTS.md, markdown mirrors, content negotiation, MCP server cards, A2A agent cards, agents.json, or agent-permissions.json. Agent Ready was built specifically for AI-agent readability and checks all of those in one pass.

Can't I just check these files manually?

You can, and the specs are public — but a manual audit means reading the Vercel Agent Readability Spec, the llmstxt.org standard, SEP-1649, the A2A spec, and the agents.json spec, then hand-verifying ~60 conditions across every page and well-known path, and re-doing it on every deploy. Agent Ready runs all 60 checks in seconds and hands back a plain-English fix for each failure, so the audit becomes a remediation list instead of a research project.

Does Agent Ready only check llms.txt?

No. A single-spec llms.txt validator checks one file against the llmstxt.org format. Agent Ready includes those 10 llms.txt checks, but adds 38 checks against the Vercel Agent Readability Spec (site-wide and per-page) and 12 checks against agent-protocol manifests — MCP, A2A, agents.json, agent-permissions.json, UCP, x402, and NLWeb — for 60 checks total.

What does Agent Ready check that other tools don't?

The agent-protocol layer. Agent Ready is the only readiness scanner that validates MCP server cards (SEP-1649), A2A agent cards, Wildcard agents.json, agent-permissions.json, UCP, x402, and NLWeb /ask endpoints — alongside llms.txt and the full Vercel Agent Readability Spec — and explains how to fix each failing check.

Agent Ready vs alternatives: agent-readiness tools compared

At a glance

Criterion	Agent Ready	Manual audit	SEO crawlers	llms.txt validators
Built for	AI-agent readability	Whatever rubric you bring	Human search-engine SEO	llms.txt format only
llms.txt / llms-full.txt	✓ 10 checks vs llmstxt.org	By hand	✗ Usually ignored	✓ Its only job
Vercel Agent Readability Spec	✓ 38 site + per-page checks	By hand	✗	✗
MCP / A2A / agents.json manifests	✓ All validated in one pass	Possible, slow & error-prone	✗ Not checked	✗ Not checked
Markdown mirrors & content negotiation	✓ Checked per page	By hand	✗	✗
Total checks	60	—	SEO-focused set	~6–10 (one file)
Fix guidance	✓ Plain-English fix per check	You write it	Generic SEO tips	Format errors only
Output surfaces	Web, JSON API, Markdown, MCP, CLI, extension	—	Web / CSV	Web
Time to result	Seconds	Hours per site	Minutes	Seconds (one file)
Price	Free, no sign-up	Your time	Freemium → paid	Free

What are the alternatives to Agent Ready?

There’s no other tool with the same scope, but three approaches cover parts of what Agent Ready does:

Manual / DIY audits. Read the Vercel Agent Readability Spec, the llmstxt.org standard, and the MCP/A2A/agents.json specs, then hand-check every condition. Total control, but it doesn’t scale and goes stale the moment you ship.
General SEO crawlers. Lighthouse, Screaming Frog, and similar audit pages for human search engines — meta tags, performance, links. They never look at llms.txt, markdown mirrors, or agent-protocol manifests.
Single-spec llms.txt validators. Lint one file against the llmstxt.org format. Handy, but blind to the other ~50 conditions that decide whether an agent can discover, parse, and act on your site.

Why choose Agent Ready?

Built specifically for AI-agent readability. Not an SEO tool with an “AI” tab bolted on — every check maps to how agents discover, parse, and cite your site.
The only scanner that validates every agent-protocol manifest in one pass. MCP server cards, A2A agent cards, agents.json, agent-permissions.json, UCP, x402, and NLWeb — checked together with llms.txt and the Vercel spec.
A remediation plan, not just a score. Every one of the 60 checks ships a clear, actionable fix when it fails.
Free, instant, and everywhere your workflow is. Scan with no sign-up in seconds, and consume results via the web UI, JSON API, Markdown mirrors, an MCP server, a CLI, and a browser extension.
Spec-aligned and evidence-based. Mapped to the Vercel Agent Readability Spec and the llmstxt.org standard, and informed by published research like Princeton’s GEO study on what gets cited in AI answers.

How is Agent Ready different from an SEO scanner?

An SEO scanner optimises for the human-search funnel: rank on a results page, win the click. Agent Ready optimises for the agent funnel: get discovered, parsed, and cited by ChatGPT, Claude, Perplexity, Gemini, and coding assistants — where, per a July 2025 Pew Research study, users click a source link only about 8% of the time. The signals that win there — llms.txt, AGENTS.md, JSON-LD, markdown mirrors, content negotiation, and protocol manifests — are exactly the ones a traditional SEO crawler doesn’t measure.

When is a manual audit or single-spec validator enough?

If you only publish an llms.txt file and want to confirm it parses, a free llms.txt linter does the job. If you’re a spec author who enjoys reading RFCs and you ship rarely, a manual audit is fine. For everyone else — anyone shipping regularly, running more than one page, or exposing MCP/A2A/agents.json — a single scan that covers all 60 conditions and tells you exactly what to fix saves hours and catches the protocol gaps the narrow tools miss.

Frequently asked questions

Is Agent Ready free?: Yes. You can scan any public URL from the homepage with no sign-up and no credit card, and results come back in seconds. A Pro plan ($19/month) adds the REST API, the authenticated MCP server, and CI/CD gating for teams that want to automate scans — but the core scanner and every fix explanation are free.
How is Agent Ready different from an SEO tool like Lighthouse or Screaming Frog?: General SEO crawlers are built to optimise pages for human search engines — page speed, meta tags, broken links, Core Web Vitals. They do not check the surfaces AI agents actually read: llms.txt, AGENTS.md, markdown mirrors, content negotiation, MCP server cards, A2A agent cards, agents.json, or agent-permissions.json. Agent Ready was built specifically for AI-agent readability and checks all of those in one pass.
Can't I just check these files manually?: You can, and the specs are public — but a manual audit means reading the Vercel Agent Readability Spec, the llmstxt.org standard, SEP-1649, the A2A spec, and the agents.json spec, then hand-verifying ~60 conditions across every page and well-known path, and re-doing it on every deploy. Agent Ready runs all 60 checks in seconds and hands back a plain-English fix for each failure, so the audit becomes a remediation list instead of a research project.
Does Agent Ready only check llms.txt?: No. A single-spec llms.txt validator checks one file against the llmstxt.org format. Agent Ready includes those 10 llms.txt checks, but adds 38 checks against the Vercel Agent Readability Spec (site-wide and per-page) and 12 checks against agent-protocol manifests — MCP, A2A, agents.json, agent-permissions.json, UCP, x402, and NLWeb — for 60 checks total.
What does Agent Ready check that other tools don't?: The agent-protocol layer. Agent Ready is the only readiness scanner that validates MCP server cards (SEP-1649), A2A agent cards, Wildcard agents.json, agent-permissions.json, UCP, x402, and NLWeb /ask endpoints — alongside llms.txt and the full Vercel Agent Readability Spec — and explains how to fix each failing check.