Skip to content
Start free trial

Free tool

AI agent readiness checker

See how well AI agents can find, read and use your site. We run 29 checks across discovery, markdown content, crawler rules, agent protocols, agent commerce and page signals, then give a score with a fix for each problem, quickest first.

A public address such as example.com or https://example.com/pricing/.

What kind of site is it?

Every check counts.

Customize checks29 of 29 checks
Discoverability
Content for agents
Bot access
Agent protocols
Agent commerce
Page signals

What this tool checks

  • Discoverability robots.txt (RFC 9309), the XML sitemap, Link response headers with registered relations (RFC 8288) and DNS records for agent discovery (DNS-AID, an early IETF draft).
  • Content for agents Markdown on request (Accept: text/markdown with Vary: Accept), a linked markdown alternate, /llms.txt in the llmstxt.org format with live links, and /llms-full.txt.
  • Bot access Which AI crawlers your robots.txt allows or blocks, Content-Signal or Content-Usage preferences, and a Web Bot Auth key directory if you run a bot.
  • Agent protocols API catalog (RFC 9727), OAuth and OpenID metadata (RFC 8414), protected resource metadata (RFC 9728), auth.md, MCP server cards, A2A agent cards, agent skills, ARD manifests, WebMCP forms and the Personal Agent Protocol.
  • Agent commerce x402 and MPP payment challenges on the URL you enter, and the UCP and ACP discovery files. They only count when we find them.
  • Page signals JSON-LD that parses, text in the raw HTML before any script runs, a canonical URL and the four required Open Graph tags.

How to fix common problems

Start with the quick fixes
robots.txt, llms.txt, Content-Signal, the API catalog, canonical and Open Graph are single files or tags. The result lists them first, each with an example you can copy.
No markdown version
Publish a markdown copy of each page (for example /page/index.md), link it with rel="alternate" type="text/markdown" and answer Accept: text/markdown with it plus Vary: Accept.
Little text without JavaScript
Agents often read the raw HTML. Render the main content on the server (SSR or static generation) instead of only in the browser.
Hand it to your coding agent
Copy all fix instructions puts every failing check, the reason and an example into one prompt for Claude Code, Cursor or Copilot. Review what it changes before you merge.

The standards behind each check

Agent readiness is a mix of long-standing web standards and new proposals that are still changing. Each check below links its specification and says how settled it is, so you can decide what is worth doing now.

Discoverability

How agents find what you publish: the robots.txt file every crawler reads first, the sitemap that lists your pages, Link headers that point at machine-readable resources, and an early proposal for discovering agents through DNS.

  • robots.txt

    Crawlers and agents read /robots.txt first to learn what they may fetch and where your sitemap is. A 5xx answer tells well-behaved crawlers to stay away from the whole site.

  • XML sitemap

    A sitemap lists every page you want found, so crawlers and agents do not have to discover them link by link.

  • Link response headers

    A Link header on the homepage points agents at machine-readable resources (API catalog, markdown version, llms.txt) without parsing any HTML.

  • DNS records for agent discovery

    DNS-AID proposes SVCB records under _agents.<your domain> so agents can find your agent endpoints before loading any page. It is an early individual IETF draft.

Content for agents

How agents read your pages. Markdown is smaller and cleaner than HTML, so agents ask for it when they can. llms.txt is a short markdown index of your site for language models.

  • Markdown on request (Accept: text/markdown)

    Agents that ask for text/markdown get clean text instead of HTML, which is smaller and easier to read correctly.

  • Markdown alternate link

    A <link rel="alternate" type="text/markdown"> tells agents where the markdown version of this page lives.

  • /llms.txt

    llms.txt is a short markdown index of your site written for language models: what the site is and which pages matter.

  • /llms-full.txt

    Some tools read llms-full.txt, your docs in one markdown file. It is a community convention, not part of the llms.txt proposal.

Bot access

Which AI crawlers may read your site and for what. robots.txt groups decide access per crawler; Content Signals and the IETF AI preferences drafts state how content may be used. Web Bot Auth lets bots prove who they are.

  • AI crawler rules

    Naming AI crawlers in robots.txt makes your choice explicit per company and purpose (training, search, user requests). Allowing or blocking is your decision; we only report it.

  • AI usage preferences

    Content-Signal lines (a Cloudflare policy) or Content-Usage (an IETF draft) state whether content may be used for search, AI answers or AI training. Neither is enforced; they record your terms.

  • Web Bot Auth key directory

    Sites that run their own bots or agents publish signing keys so other sites can verify those requests. Only relevant if you operate a bot.

Agent protocols

How agents find your APIs, sign users in and talk to your own agents or MCP servers. The OAuth documents and the API catalog are RFCs; the agent-specific formats are recent proposals.

  • API catalog

    RFC 9727 gives every site one well-known address that lists its public APIs and their OpenAPI descriptions, so agents can find them without guessing.

  • OAuth / OpenID discovery

    Agents that sign in on behalf of a user read your authorization server metadata to find the login and token endpoints.

  • OAuth protected resource metadata

    RFC 9728 tells an agent which authorization server protects your API. MCP servers are required to publish it.

  • auth.md for agents

    auth.md (a WorkOS proposal) is a markdown guide that tells agents how to authenticate, linked from your OAuth metadata.

  • MCP server card

    A server card describes your MCP server (name, version, endpoints) so clients can connect without trial and error.

  • A2A agent card

    Agents that talk to other agents over the A2A protocol fetch /.well-known/agent-card.json to learn what your agent can do.

  • Agent skills index

    A skills index lists SKILL.md files agents can download to learn how to use your product.

  • Agent resource catalog (ARD)

    An ARD manifest lists the agent-facing resources of a domain (MCP servers, agents, APIs) in one file.

  • WebMCP tools in the page

    WebMCP lets a page offer actions to browser agents. We can only see the declarative form attributes in the HTML; tools registered from JavaScript are invisible to this check.

  • Personal Agent Protocol

    A draft protocol that lets personal agents discover how to sign in and act on your site for a user.

Agent commerce

How agents pay or check out. These protocols are new and mostly vendor-led; we only count them when your site publishes them.

  • x402 payments

    x402 lets an agent pay for a resource over HTTP: the server answers 402 with what it accepts. There is no site-wide discovery file, so check the URL of a paid resource.

  • Machine payments (MPP)

    MPP is a draft HTTP authentication scheme for payments: a 402 with WWW-Authenticate: Payment, and an OpenAPI file that marks paid operations.

  • Universal Commerce Protocol

    A UCP profile tells shopping agents which commerce services and payment handlers your store supports.

  • Agentic Commerce Protocol

    ACP defines a checkout API for agents. Its discovery file is still a proposal, so few stores publish it yet.

Page signals

Signals inside the HTML that agents and search engines already rely on: structured data, text that does not need JavaScript, the canonical URL and Open Graph tags.

  • Structured data (JSON-LD)

    JSON-LD states facts about the page (who runs it, what is sold, prices) in a form agents and search engines read without guessing.

  • Text without JavaScript

    Many agents read the raw HTML and never run scripts. A page that renders its text only in the browser looks empty to them.

  • Canonical URL

    The canonical tells agents and search engines which URL is the real one, so they do not cite a copy with tracking parameters.

  • Open Graph tags

    og:title, og:type, og:image and og:url give link previews and many agents a clean title, image and URL for the page.

FAQ

Questions

Something missing here? Send us a message

How is the score calculated?

Each check has a weight that depends on the site type you pick. A pass earns the full weight, a warning half and a fail nothing. Checks marked not applicable are left out, so a blog is not marked down for having no payment API. The level reads 85 and up as Agent-ready, 60 as Agent-friendly, 35 as Partly ready.

Which site type should I pick?

Content site for blogs, docs, shops and marketing sites: reading and discovery weigh most, and API or agent protocols only count when you publish them. API or app for products with an API, sign-in or an MCP server: the API catalog, OAuth metadata and MCP card count even when missing. All checks counts everything.

Are all of these official standards?

No. robots.txt, Link headers, the API catalog and the OAuth documents are IETF RFCs. DNS-AID, Web Bot Auth, AI usage preferences and MPP are IETF drafts, WebMCP is a W3C community draft, and llms.txt, Content Signals, MCP server cards, A2A, agent skills, ARD, x402, UCP and ACP are vendor or community proposals. Each check in the result names its status and links the specification. Drafts change, so we only count most of them when you publish them.

Why is x402 not applicable on my homepage?

x402 has no site-wide discovery file. A paid resource answers 402 with its payment requirements, so enter the URL of a paid endpoint to test it.

Does a high score mean AI can train on my content?

No. The score is about agents finding and reading your pages. We report which AI crawlers your robots.txt allows or blocks without judging the choice, and training is a separate preference (Content-Signal: ai-train=no).

How do you look up DNS records?

Through a public DNS-over-HTTPS resolver, which only answers public names. We query _agents and _index._agents under your domain and nothing else.

Can I share a result?

Yes. After a check the page address includes your URL and options. Anyone who opens it runs the same check again; within 10 minutes they get the saved result. We keep no history.

Is this tool free?

Yes. You do not need an account. Each IP address can run 10 checks a minute and 100 a day, and a website can be checked 10 times in 10 minutes across all visitors so the tool is never used to flood a site.

Do you store the URL or the results?

The result is kept for 10 minutes so a repeated check is instant, then it is deleted. We do not log the URLs you check or the content of the page.

More free tools

Start monitoring your website

Add your address, pick the pages and approve the first scan as your baseline.

Start monitoring Talk to us

Plans start at €19 per month. Prices are provisional.