Checklist · scored by the free checker

Agent-ready website checklist: llms.txt, robots.txt, OpenAPI, MCP and x402.

An agent-ready site lets an AI agent find out what you offer, read it as text, call your API and, if you sell, pay. In practice that means files at known paths: llms.txt, robots.txt with a sitemap, structured data, an OpenAPI description, an MCP endpoint and, for sellers, an x402 or MPP payment offer. This is the list the free agent readiness checker scores, item by item, with the weight and the fix for each.

40 of 100 points

Readable: the content checks

Scroll the table horizontally to see all fields.

Readable checks
ItemWhere the checker looksWeightFix if it fails
llms.txt/llms.txt12Publish /llms.txt: a Markdown file that starts with one H1 naming the site and links to the pages an agent should read.
robots.txt/robots.txt8Publish /robots.txt, even if it only allows everything, and list your sitemap in it.
Rules for AI crawlersThe rules in /robots.txt6Review the robots.txt rules for AI crawlers and for agents acting for a person.
SitemapThe sitemap named in /robots.txt, or /sitemap.xml6Publish a sitemap on this site and name it in robots.txt.
Structured dataJSON-LD on the home page8Add JSON-LD structured data to the home page.

These decide whether an agent can find and read your pages at all. A site that cannot be read will not be called or paid. Keep llms.txt short and written for an agent with a task: what you do, where to start and what it costs.

40 of 100 points

Callable: the API checks

Scroll the table horizontally to see all fields.

Callable checks
ItemWhere the checker looksWeightFix if it fails
OpenAPI description/openapi.json, then /openapi.yaml14Publish an OpenAPI description at /openapi.json.
MCP endpointAn endpoint declared in /.well-known/ai-catalog.json or /.well-known/mcp/server-card.json, otherwise /mcp14Expose an MCP endpoint over Streamable HTTP and declare it in a discovery file.
API catalog/.well-known/api-catalog6Publish an API catalog at /.well-known/api-catalog.
A2A agent card/.well-known/agent-card.json6Publish an agent card at /.well-known/agent-card.json.
OAuth metadata/.well-known/oauth-protected-resource and /.well-known/oauth-authorization-serverReported, not scoredReported for information.

These decide whether an agent can call you. Publish one OpenAPI description at a stable URL and declare its authentication, so a client knows which credential to send. An MCP endpoint can let agent clients list your tools before they hold a key.

20 of 100 points

Payable: the commerce checks

Scroll the table horizontally to see all fields.

Payable checks
ItemWhere the checker looksWeightFix if it fails
Payment offersPaid operations in the OpenAPI description, or a 402 from the home page10If the site sells to agents, declare its payment offers (x402 or MPP).
UCP profile/.well-known/ucp5If the site sells to agents, publish a UCP profile at /.well-known/ucp.
ACP manifest/.well-known/acp.json5If the site sells to agents, publish an ACP manifest at /.well-known/acp.json.

These only matter if you sell to agents. A paid endpoint should answer an unpaid request with a real 402 offer, and the operations that cost money should be marked in your OpenAPI description.

How the score works

  • 12 items carry weight, 100 points in all. OAuth metadata is reported but scores nothing.
  • A pass earns the full weight, a warning half and a failure none.
  • An item the checker could not read, because it timed out or was refused, is left out of the score instead of counted as missing.
  • If under half of the weight could be read, there is no score: it would mean nothing.
  • The free check marks a site as passing at 50 or more out of 100. You can show the result as a badge.

A high score does not show that a site's API works, that its offers are honest or that it is safe to pay. A low score does not make it a bad site.

Free, no key

Run the checklist on your site

Enter your domain on the agent readiness checker. It reads the files above in one sweep, from outside, with no cookies. The same result is JSON:

curl -s "https://pageverified.com/api/v1/check/agent-readiness?domain=example.com"

The free result gives the status of each item and the fix. agent_readiness (3 credits) returns the full report for an agent: the detail behind each status, the standard each item comes from and how settled that standard is.

Where each item comes from

The blog post Making a website readable and payable by agents walks through the same ground in prose, with a link to the standard or proposal behind each item and notes on what to serve. This page is the scored version of that list: what the checker reads, what it weighs and what it tells you to fix.

Common questions

Do I need every item?

No. The payable items only matter if you sell to agents, and a site that does not offer an API has no reason to publish an OpenAPI description. Do the readable items first.

Is llms.txt a standard?

It is a proposal, not a ratified standard. It is cheap to publish and some agent tools look for it, which is why the checker gives it weight.

Does robots.txt stop agents?

No. It states your preferences, and well-behaved crawlers follow them. It is not access control. Protect private pages with real authentication.

Does the checker obey robots.txt?

Yes. Every file is requested through PageVerified's fetcher, which obeys robots.txt. If the site refuses PageVerifiedBot on its home page, the check stops and says so.

Next steps

  • Free checks: test an MCP server, read an x402 payment offer or score a domain's agent readiness. No key needed.
  • Evidence Capture: capture one public page as a screenshot and its HTML, with the SHA-256 of each file and a signed record, for US$9 once by card. No account and no API key.
  • Pricing: credit packs and what every tool costs.
  • Documentation: quickstart, MCP setup and every tool's reference page.
  • Agent readiness checker: the scored check of this list.

Related answers: How to test an MCP server · Is this x402 API legit? · Find MCP servers by tested capability.