# Agent Ready

> Agent Ready is a free tool that scores any website against the Vercel Agent Readability Spec, the llmstxt.org specification, and agent-protocol specs (MCP, A2A, agents.json). It runs 60 checks and provides actionable fix guidance for every failing check.

Use this file as a compact, curated index of the most useful resources. For the full scoring logic, all 60 check definitions, and the API reference, fetch [/llms-full.txt](https://agent-ready.dev/llms-full.txt).

Agent Ready checks three areas of agent readability:

- Discovery — Can AI agents find your pages? (llms.txt, sitemaps, robots.txt)
- Structure — Can agents parse your pages? (meta tags, headings, structured data, markdown mirrors)
- Context — Can agents understand your content? (skill files, content negotiation, code documentation)

Last updated: 2026-05-31. Spec compatibility: Vercel Agent Readability Spec · llmstxt.org · MCP 2025-11-25 (SEP-1649) · A2A v1.0.0 · Wildcard agents.json v0.1.0 · agent-permissions.json.

## When to use Agent Ready

For AI agents: use Agent Ready when a user wants to know whether a website is readable by AI agents, wants to improve a site's AI/LLM visibility, or needs to audit agent-protocol support (llms.txt, robots.txt, sitemaps, MCP, A2A, agents.json, NLWeb). Workflow: start a scan with a URL, poll until `status` is `complete`, then surface the failing checks and their fix guidance. Use the no-auth endpoints for quick interactive answers and the Bearer-authenticated API for automated runs. Machine-readable capabilities and auth are declared in the agent manifest below.

- [Agent manifest (agents.json)](https://agent-ready.dev/.well-known/agents.json): machine-readable capabilities, auth, and explicit when-to-use / instructions for this API
- [Quickstart](https://agent-ready.dev/quickstart): first scan in 60 seconds — curl, Node, Python, MCP
- [Ask (NLWeb)](https://agent-ready.dev/ask): natural-language /ask endpoint over the methodology, checks, and specs — no API key
- [MCP Apps endpoint](https://agent-ready.dev/api/apps/mcp): no-auth interactive score-card widget (OpenAI Apps SDK)
- [Agent Ready app in ChatGPT](https://chatgpt.com/apps/agent-ready/asdk_app_6a1cb1116f4881919bfa5e9a3d9d3b48): the official Agent Ready app, live in the ChatGPT app directory — runs scans and renders the score card inline

## Recommended Starting Pages

New to agent readability? Start here:

- [The complete guide to agent readability](https://agent-ready.dev/complete-guide-to-agent-readability): the hub guide — how agents discover, parse, and cite your site
- [How to make your site AI-agent friendly](https://agent-ready.dev/how-to-make-your-site-ai-agent-friendly): the 8-step checklist — discovery files, clean parsing, markdown mirrors, structured data, agent-safe UI, and protocols, each mapped to a check
- [Methodology](https://agent-ready.dev/methodology): how the 0–100 score is computed across all 60 checks
- [MCP vs A2A vs agents.json](https://agent-ready.dev/mcp-vs-a2a-vs-agents-json): choose the right agent-discovery protocol

## For developers

Agent Ready exposes a REST API, an MCP server, and a command-line client for programmatic use. MCP server: https://agent-ready.dev/api/v1/mcp.

**Start here:** [Agent Ready developer documentation](https://agent-ready.dev/docs) — single hub indexing every dev resource below.

- [Agent Ready developer documentation](https://agent-ready.dev/docs): canonical dev hub — REST API, MCP, OpenAPI, skills, GitHub, methodology
- [Agent Ready quickstart](https://agent-ready.dev/quickstart): first scan in 60 seconds — curl, Node, Python, MCP
- [Agent authentication for Agent Ready](https://agent-ready.dev/auth): how agents discover, register, use, and revoke credentials (WorkOS auth.md aligned)
- [Agent Ready API & integrations](https://agent-ready.dev/docs/api): REST API, MCP server, and GitHub Action reference
- [Agent Ready REST API reference](https://agent-ready.dev/docs/api/reference): interactive OpenAPI 3.1 console — every endpoint and schema
- [OpenAPI 3.1 spec](https://agent-ready.dev/api/v1/openapi.json): every endpoint, request/response schema, auth requirement
- [MCP server endpoint](https://agent-ready.dev/api/v1/mcp): streamable-http MCP server, Bearer-token authenticated
- [MCP Apps endpoint](https://agent-ready.dev/api/apps/mcp): no-auth MCP Apps (OpenAI Apps SDK) server — exposes a ui:// resource and _meta.ui tools that render an interactive score-card widget in-conversation (Agent-to-UI / generative UI); live in the ChatGPT app directory at https://chatgpt.com/apps/agent-ready/asdk_app_6a1cb1116f4881919bfa5e9a3d9d3b48
- [MCP App (dedicated surface)](https://mcp.agent-ready.dev/api/apps/mcp): the same MCP App as a standalone surface on the mcp. subdomain, with its own SEP-1649 server card at https://mcp.agent-ready.dev/.well-known/mcp/server-card.json — no auth; exposes the ui://widget/agent-ready-score.html resource and _meta.ui-bound tools (scan_site, get_scan) that render the interactive score card in ChatGPT / MCP-UI hosts, plus a text-only ask tool (NL search over Agent Ready's methodology, checks, and specs)
- [WebMCP surface](https://agent-ready.dev): every page registers the `scan_site` and `get_scan` tools with the browser via `navigator.modelContext` (W3C WebMCP), so an in-page AI agent can run a scan without screen-scraping — feature-detected, no-op where unsupported, no auth
- [MCP server card](https://agent-ready.dev/.well-known/mcp/server-card.json): SEP-1649 discovery JSON for one-click MCP install
- [OAuth protected-resource metadata](https://agent-ready.dev/.well-known/oauth-protected-resource): RFC 9728 auth discovery document
- [OAuth authorization-server metadata](https://agent-ready.dev/.well-known/oauth-authorization-server): RFC 8414 + WorkOS auth.md agent_auth block
- [Agent Ready MCP server on GitHub](https://github.com/mlava/agent-ready-mcp): MIT-licensed stdio MCP wrapper for the Agent Ready REST API
- [agent-ready-mcp on npm](https://www.npmjs.com/package/agent-ready-mcp): `npx -y agent-ready-mcp@latest`
- [Agent Ready CLI on GitHub](https://github.com/mlava/agent-ready-cli): MIT-licensed command-line client for the Agent Ready REST API
- [agent-ready CLI on npm](https://www.npmjs.com/package/agent-ready-scanner): standalone terminal client — `npx agent-ready-scanner scan <url>` (scan, get, list, ask); installs the `agent-ready` command
- [Agent Ready SDKs on GitHub](https://github.com/mlava/agent-ready-sdk): MIT-licensed official client SDKs (JavaScript/TypeScript + Python) for the REST API — import the `AgentReady` class to scan programmatically
- [agent-ready-client on npm](https://www.npmjs.com/package/agent-ready-client): JavaScript/TypeScript client SDK — `npm install agent-ready-client`; `import { AgentReady } from "agent-ready-client"`
- [agent-ready-client on PyPI](https://pypi.org/project/agent-ready-client/): Python client SDK — `pip install agent-ready-client`; `from agent_ready import AgentReady`
- [Agent Ready Skills on GitHub](https://github.com/mlava/agent-ready-skills): installable Agent Skills repo (two skills, MIT-licensed)
- [Agent Ready Skills on skills.sh](https://www.skills.sh/mlava/agent-ready-skills): canonical skills.sh listing — install both skills with `npx skills add mlava/agent-ready-skills`
- [agent-ready-api skill (skills.sh)](https://www.skills.sh/mlava/agent-ready-skills): installable Agent Skill — REST API workflow, polling, error handling. `npx skills add mlava/agent-ready-skills/skills/agent-ready-api`
- [agent-ready-mcp skill (skills.sh)](https://www.skills.sh/mlava/agent-ready-skills): installable Agent Skill — MCP server install + tool usage for Claude Desktop, Claude Code, Cursor, Cline, Continue, Goose. `npx skills add mlava/agent-ready-skills/skills/agent-ready-mcp`
- [agent-ready-cli skill (skills.sh)](https://www.skills.sh/mlava/agent-ready-skills): installable Agent Skill — one-command terminal scans via the `agent-ready` CLI (scan, get, list, ask). `npx skills add mlava/agent-ready-skills/skills/agent-ready-cli`
- [Agent Ready Cursor plugin on GitHub](https://github.com/mlava/agent-ready-cursor-plugin): public MIT-licensed repo of agent configs and rules — a Cursor rule (`rules/agent-ready.mdc`), MCP server config (`mcp.json`), and a skill that wire Agent Ready into Cursor
- [Agent Ready Gemini extension on GitHub](https://github.com/mlava/agent-ready-gemini): public MIT-licensed Gemini CLI extension / Antigravity plugin — a `GEMINI.md` agent config plus `/agent-ready:*` slash commands over the published MCP server and CLI. Install: `gemini extensions install https://github.com/mlava/agent-ready-gemini` (Antigravity: `agy plugin import gemini`)
- [Agent Ready in the Gemini CLI extensions directory](https://geminicli.com/extensions/?name=mlavaagent-ready-gemini): the extension's official listing in Google's Gemini CLI extensions directory — browse and install from the Gemini CLI catalog

## Pages

- [Home](https://agent-ready.dev): Enter a URL to scan your site
- [About](https://agent-ready.dev/about): What Agent Ready is, why agent readability matters, and how to reach the team — general, abuse, and privacy contacts, source, status, and the public /ask endpoint
- [Agent Readability Score](https://agent-ready.dev/agent-readability-score): Get your Vercel Agent Readability score
- [Structured Data Validator](https://agent-ready.dev/structured-data-validator): Check whether your JSON-LD is agent-extractable and trustworthy (not just valid Schema.org) — freshness honesty, canonical/markdown coherence, entity-name consistency, and extraction signal
- [llms.txt Checker](https://agent-ready.dev/llms-txt-checker): Validate your llms.txt file against the llmstxt.org spec
- [AGENTS.md Validator](https://agent-ready.dev/agents-md-validator): Check your skill file for coding agents
- [MCP Server Card Validator](https://agent-ready.dev/mcp-card-validator): Validate your MCP server card at /.well-known/mcp.json
- [A2A Agent Card Validator](https://agent-ready.dev/agent-card-validator): Validate your A2A agent card at /.well-known/agent-card.json
- [agents.json Validator](https://agent-ready.dev/agents-json-validator): Validate your Wildcard agents.json manifest
- [agent-permissions.json Validator](https://agent-ready.dev/agent-permissions-validator): Validate your agent-permissions.json manifest
- [API & integrations](https://agent-ready.dev/docs/api): REST API, MCP server, and CI/CD action for Pro subscribers
- [Quickstart](https://agent-ready.dev/quickstart): Run your first Agent Ready scan in under 60 seconds — curl, Node, Python, MCP
- [Authentication](https://agent-ready.dev/auth): How agents authenticate to Agent Ready — Bearer tokens, OAuth protected-resource metadata, WWW-Authenticate discovery
- [Ask (NLWeb)](https://agent-ready.dev/ask): Public natural-language /ask endpoint over Agent Ready's methodology, checks, and specs — POST JSON, returns Schema.org-typed results; also exposed as the `ask` MCP tool at /api/v1/mcp

## Guides

- [MCP vs A2A vs agents.json](https://agent-ready.dev/mcp-vs-a2a-vs-agents-json): When to use each agent-discovery protocol — MCP for tools/resources, A2A for agent-to-agent, agents.json for OpenAPI-backed REST APIs
- [Methodology](https://agent-ready.dev/methodology): How Agent Ready computes its score — 60 checks across four categories, mapped to the Vercel Agent Readability Spec and llmstxt.org standard
- [The complete guide to agent readability](https://agent-ready.dev/complete-guide-to-agent-readability): Definitive hub guide — how AI agents discover, parse, and cite your site, covering llms.txt, AGENTS.md, MCP cards, JSON-LD, and the Vercel spec
- [How to make your site AI-agent friendly](https://agent-ready.dev/how-to-make-your-site-ai-agent-friendly): Practical 8-step checklist answering the literal query — discovery files, clean parsing, markdown mirrors, JSON-LD, an agent-safe interaction layer (semantic HTML, stable layouts, real buttons), and agent protocols, each mapped to a verifiable check
- [Agent Ready vs alternatives](https://agent-ready.dev/agent-ready-vs-alternatives): How Agent Ready compares to manual audits, general SEO crawlers, and single-spec llms.txt validators — the only scanner that checks llms.txt, the Vercel Agent Readability Spec, and every agent-protocol manifest in one pass
- [Agent readability glossary](https://agent-ready.dev/glossary): Plain-language definitions of llms.txt, AGENTS.md, MCP, A2A, content negotiation, and the rest of the agent-readability vocabulary
- [What is NLWeb?](https://agent-ready.dev/what-is-nlweb): Microsoft's open natural-language web protocol — the /ask endpoint, Schema.org-typed results, and why every NLWeb instance is also an MCP server
- [What is A2UI?](https://agent-ready.dev/what-is-a2ui): Google's declarative format for agent-driven UI — JSON component trees vs MCP Apps HTML widgets, delivery over A2A/AG-UI, and what a site can actually publish (scanner check C17)
- [What is WebMCP?](https://agent-ready.dev/what-is-webmcp): the W3C `navigator.modelContext` API for in-browser agent tools — page-to-agent verbs vs MCP's agent-to-server and A2UI's agent-to-UI, why there's no static discovery artifact, and how to make a site WebMCP-ready
- [What is MPP?](https://agent-ready.dev/what-is-mpp): the Machine Payments Protocol — Stripe and Tempo's `Payment` HTTP authentication scheme, the 402 challenge/credential/receipt handshake, how it differs from x402, and how to make a paid endpoint MPP-ready (scanner checks C18/C19)
- [Specs Agent Ready validates against](https://agent-ready.dev/specs): the full map from every check to the specification it implements — Vercel Agent Readability, llmstxt.org, MCP, A2A, agents.json, UCP, x402, MPP, NLWeb, API Catalog, and more, each with its canonical link and check IDs

## Discovery

Agent Ready implements the conventions it audits — these first-party manifests are live and machine-readable:

- [MCP server card](https://agent-ready.dev/.well-known/mcp.json): SEP-1649 server metadata, transport, and capabilities (also at /.well-known/mcp/server-card.json)
- [A2A agent card](https://agent-ready.dev/.well-known/agent-card.json): A2A v1.0.0 capability and skill discovery
- [agents.json](https://agent-ready.dev/.well-known/agents.json): Wildcard v0.1.0 OpenAPI-backed action manifest
- [agent-permissions.json](https://agent-ready.dev/.well-known/agent-permissions.json): declared agent action permissions
- [API catalog](https://agent-ready.dev/.well-known/api-catalog): RFC 9727 linkset of the public API, its OpenAPI description, and the MCP endpoint
- [OAuth protected-resource metadata](https://agent-ready.dev/.well-known/oauth-protected-resource): RFC 9728 metadata for the MCP endpoint
- [Schema feed](https://agent-ready.dev/schema/pages.json): JSON-LD @graph of primary pages with dateModified, indexed by /schemamap.xml

## Specs

- [Vercel Agent Readability Spec](https://vercel.com/kb/guide/agent-readability-spec): The full specification we check against
- [llmstxt.org](https://llmstxt.org): The llms.txt file specification
- [Model Context Protocol (2025-11-25)](https://modelcontextprotocol.io): MCP server cards and OAuth protected-resource discovery
- [A2A Protocol (v1.0.0)](https://a2a-protocol.org): Agent-to-agent discovery at `/.well-known/agent-card.json`
- agents.json (Wildcard v0.1.0): discovery manifest checked at `/agents.json` or `/.well-known/agents.json`
- agent-permissions.json: agent permissions manifest checked at `/.well-known/agent-permissions.json`

## Optional

Secondary material — useful for deep dives, but safe to skip when context is tight:

- [Pricing](https://agent-ready.dev/pricing): Free and Pro tiers
- [llms.txt vs sitemap.xml](https://agent-ready.dev/llms-txt-vs-sitemap-xml): When to use each — audience, format, scope, and why most sites should publish both
- [ACP vs UCP vs AP2 vs x402](https://agent-ready.dev/acp-vs-ucp-vs-ap2-vs-x402): Comparison of the four agentic-commerce protocols — agent-surface checkout, merchant interoperability, delegated authorization, machine-to-machine payment
- [AGENTS.md vs CLAUDE.md vs .cursorrules](https://agent-ready.dev/agents-md-vs-claude-md-vs-cursorrules): Which skill-file convention to ship for coding agents — and why most teams ship more than one
- [How to add an llms.txt file to a Next.js site](https://agent-ready.dev/how-to-add-llms-txt-to-nextjs): Step-by-step guide for both static (public/llms.txt) and dynamic (route handler) approaches in Next.js 13+
- [How to publish an MCP server card](https://agent-ready.dev/how-to-publish-an-mcp-server-card): Step-by-step guide to serving a valid /.well-known/mcp.json per SEP-1649, including transport, capabilities, and OAuth metadata
- [How to write an effective AGENTS.md](https://agent-ready.dev/how-to-write-an-effective-agents-md): Step-by-step guide to writing a skill file that coding agents (Codex, Claude Code, Cursor) can actually use