https://agent-ready.dev/

{
  "url": "https://agent-ready.dev/",
  "timestamp": 1779974609091,
  "fetch": {
    "mode": "simple",
    "timeMs": 834,
    "htmlSizeBytes": 225128,
    "supportsMarkdown": true,
    "markdownAgents": {
      "contentNegotiation": true,
      "mdUrl": {
        "found": false,
        "url": null
      },
      "linkTag": {
        "found": true,
        "url": "https://agent-ready.dev/index.html.md"
      },
      "linkHeader": {
        "found": false,
        "url": null
      },
      "responseHeaders": {
        "contentSignal": null,
        "xMarkdownTokens": null,
        "vary": null
      },
      "frontmatter": {
        "present": true,
        "fields": [
          "title",
          "description",
          "last_updated",
          "canonical_url"
        ],
        "level": "enriched"
      },
      "level": "application"
    },
    "statusCode": 200
  },
  "extraction": {
    "title": "Agent Ready — AI Agent Readability Checker",
    "excerpt": "Score any website against the Vercel Agent Readability Spec and llmstxt.org standard.",
    "byline": null,
    "siteName": "Agent Ready",
    "lang": "en",
    "contentLength": 2337,
    "metadata": {
      "description": "Score any website against the Vercel Agent Readability Spec and llmstxt.org standard. Get actionable fixes to make your site AI-agent friendly.",
      "ogTitle": "Agent Ready — AI Agent Readability Checker",
      "ogDescription": "Score any website against the Vercel Agent Readability Spec and llmstxt.org standard.",
      "ogImage": "https://agent-ready.dev/opengraph-image?a06723ce554d69c8",
      "ogType": "website",
      "canonical": "https://agent-ready.dev",
      "lang": "en",
      "schemas": [
        {
          "@type": "Organization",
          "@id": "https://agent-ready.dev/#organization",
          "name": "Agent Ready",
          "url": "https://agent-ready.dev",
          "logo": "https://agent-ready.dev/opengraph-image"
        },
        {
          "@type": "WebSite",
          "@id": "https://agent-ready.dev/#website",
          "url": "https://agent-ready.dev",
          "name": "Agent Ready",
          "description": "Score any website against the Vercel Agent Readability Spec and llmstxt.org standard.",
          "publisher": {
            "@id": "https://agent-ready.dev/#organization"
          },
          "inLanguage": "en-GB",
          "dateModified": "2026-05-12"
        },
        {
          "@type": "Service",
          "@id": "https://agent-ready.dev/#service",
          "name": "Agent Ready",
          "url": "https://agent-ready.dev",
          "description": "AI agent readability scanner. Runs 60 checks against the Vercel Agent Readability Spec, llmstxt.org, and agent-protocol specs (MCP, A2A, agents.json, agent-permissions.json), returning a 0–100 score and per-check fix guidance.",
          "serviceType": "Agent readability scanner",
          "provider": {
            "@id": "https://agent-ready.dev/#organization"
          },
          "areaServed": "Worldwide",
          "audience": {
            "@type": "Audience",
            "audienceType": "Developers"
          },
          "offers": [
            {
              "@type": "Offer",
              "name": "Free",
              "price": "0",
              "priceCurrency": "USD",
              "url": "https://agent-ready.dev/pricing"
            },
            {
              "@type": "Offer",
              "name": "Pro",
              "priceCurrency": "USD",
              "priceSpecification": {
                "@type": "UnitPriceSpecification",
                "price": "19",
                "priceCurrency": "USD",
                "unitText": "MONTH"
              },
              "url": "https://agent-ready.dev/pricing"
            },
            {
              "@type": "Offer",
              "name": "Team",
              "priceCurrency": "USD",
              "priceSpecification": {
                "@type": "UnitPriceSpecification",
                "price": "49",
                "priceCurrency": "USD",
                "unitText": "MONTH"
              },
              "url": "https://agent-ready.dev/pricing"
            }
          ]
        },
        {
          "@context": "https://schema.org",
          "@type": "SoftwareApplication",
          "name": "Agent Ready",
          "url": "https://agent-ready.dev",
          "description": "Score any website against the Vercel Agent Readability Spec and llmstxt.org standard. Get actionable fixes to make your site AI-agent friendly.",
          "applicationCategory": "DeveloperApplication",
          "operatingSystem": "Web",
          "publisher": {
            "@id": "https://agent-ready.dev/#organization"
          },
          "dateModified": "2026-05-11",
          "offers": {
            "@type": "AggregateOffer",
            "priceCurrency": "USD",
            "lowPrice": "0",
            "highPrice": "19",
            "offerCount": "2"
          },
          "breadcrumb": {
            "@type": "BreadcrumbList",
            "itemListElement": [
              {
                "@type": "ListItem",
                "position": 1,
                "name": "Home",
                "item": "https://agent-ready.dev"
              }
            ]
          }
        },
        {
          "@context": "https://schema.org",
          "@type": "BreadcrumbList",
          "itemListElement": [
            {
              "@type": "ListItem",
              "position": 1,
              "name": "Home",
              "item": "https://agent-ready.dev"
            }
          ]
        },
        {
          "@context": "https://schema.org",
          "@type": "FAQPage",
          "mainEntity": [
            {
              "@type": "Question",
              "name": "What is agent readability?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "Agent readability is how easily AI agents — ChatGPT, Claude, Perplexity, Google Gemini, coding assistants, MCP clients — can discover, parse, and act on a website. It spans three surfaces: discovery files (llms.txt, robots.txt, sitemaps), structural signals (semantic headings, canonical links, structured data, markdown mirrors), and protocol manifests (MCP Server Cards, A2A Agent Cards, agents.json, agent-permissions.json)."
              }
            },
            {
              "@type": "Question",
              "name": "Why does AI agent readability matter for SEO?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "AI agents crawl what loads cleanly and cite what parses correctly. Sites that score well get summarised accurately and referred qualified traffic; sites that score poorly get paraphrased badly or skipped entirely. Unlike traditional SEO, you do not need to rank on page 1 — structured, citable content gets pulled even when organic rank is low."
              }
            },
            {
              "@type": "Question",
              "name": "What does the agent readability scanner check?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "Agent Ready runs 60 checks across three spec families: 38 against the Vercel Agent Readability Spec (15 site-wide plus 23 per-page covering meta tags, JSON-LD, headings, markdown mirrors, content negotiation, code-block language tags, JS rendering), 10 against the llmstxt.org specification, and 12 against agent protocols (MCP Server Cards, A2A Agent Cards, Wildcard agents.json, agent-permissions.json, UCP, x402, and NLWeb)."
              }
            },
            {
              "@type": "Question",
              "name": "How is the agent readability score calculated?",
              "acceptedAnswer": {
                "@type": "Answer",
                "text": "Score = round((passed checks / total checks) × 100). The denominator compounds: 15 site-wide plus (23 per-page × number of pages scanned). A systemic issue like a missing canonical link on every page compounds significantly. Ratings: 90-100 Excellent, 70-89 Good, 50-69 Fair, 0-49 Needs Improvement."
              }
            }
          ]
        }
      ],
      "robotsMeta": null,
      "author": null,
      "generator": null,
      "markdownAlternateHref": "https://agent-ready.dev/index.html.md"
    }
  },
  "markdown": "## What is agent readability?\n\nAgent readability is how easily AI agents — ChatGPT, Claude, Perplexity, Google Gemini, coding assistants, MCP clients — can discover, parse, and act on a website. It spans three surfaces: discovery files (`llms.txt`, `robots.txt`, sitemaps), structural signals (semantic headings, canonical links, structured data, markdown mirrors), and protocol manifests (MCP Server Cards, A2A Agent Cards, agents.json, agent-permissions.json).\n\n## Why does AI agent readability matter for SEO?\n\nAI agents crawl what loads cleanly and cite what parses correctly. The incentives are sharp: a [July 2025 Pew Research study](https://www.pewresearch.org/short-reads/2025/07/22/google-users-are-less-likely-to-click-on-links-when-an-ai-summary-appears-in-the-results/) found users who encounter a Google AI Overview click on a source link only about 8% of the time — roughly half the rate of searches without an AI summary. Princeton’s [GEO study (KDD 2024)](https://arxiv.org/abs/2311.09735) measured that adding source citations to a page lifted its inclusion in AI answers by roughly 40%, with statistics and quotations close behind. Sites that score well get summarised accurately and referred qualified traffic; sites that score poorly get paraphrased (badly) or skipped entirely. Unlike traditional SEO, you don’t need to rank on page 1 — structured, citable content gets pulled even when organic rank is low.\n\n## What does the agent readability scanner check?\n\n-   **Vercel Agent Readability Spec** — 15 site-wide checks (llms.txt, robots.txt, sitemap.xml, sitemap.md, AGENTS.md, HTTPS, OpenAPI) plus 23 per-page checks (meta tags, JSON-LD, headings, markdown mirrors, content negotiation, code-block language tags, JS-rendering dependency).\n-   **llmstxt.org** — 10 checks against the llms.txt format (H1 present, blockquote summary, H2 sections, link format, content-type, llms-full.txt).\n-   **Agent protocols** — 12 checks covering MCP Server Cards (SEP-1649 / [RFC 9728](https://datatracker.ietf.org/doc/html/rfc9728) OAuth Protected Resource metadata), A2A Agent Cards (a2a.proto v1.0.0), Wildcard agents.json, agent-permissions.json, UCP (Universal Commerce Protocol), x402 (HTTP 402 Payment Required), and NLWeb (natural-language /ask endpoint).\n\n## How is the agent readability score calculated?\n\n`score = round((passed checks / total checks) × 100)`. The denominator compounds: 15 site-wide + (23 per-page × number of pages scanned). A systemic issue like a missing canonical link on every page compounds significantly. Ratings: 90-100 Excellent, 70-89 Good, 50-69 Fair, 0-49 Needs Improvement.\n",
  "fullPageMarkdown": "Agent Ready — AI Agent Readability Checker\n\n[Agent Readyagent.ready](https://agent-ready.dev/)[Sign in](https://agent-ready.dev/sign-in)\n\nNo sign-up required — scan instantly\n\n# Is your site ready for AI agents?\n\nScore any website against the Vercel Agent Readability Spec and llmstxt.org standard. Get actionable fixes in seconds.\n\nScan\n\nLast updated 2026-05-11\n\n[\n\n## Readability spec\n\n15 site-wide + 23 per-page checks from the Vercel Agent Readability Spec\n\n](https://agent-ready.dev/agent-readability-score)[\n\n## llms.txt\n\n10 checks against the llmstxt.org specification for LLM-friendly content\n\n](https://agent-ready.dev/llms-txt-checker)[\n\n## Agent protocols\n\n12 checks covering MCP, A2A, agents.json, UCP, x402, and NLWeb\n\n](https://agent-ready.dev/mcp-card-validator)\n\n## Fix guidance\n\nEvery failing check includes a clear, actionable how-to-fix explanation\n\n## What is agent readability?\n\nAgent readability is how easily AI agents — ChatGPT, Claude, Perplexity, Google Gemini, coding assistants, MCP clients — can discover, parse, and act on a website. It spans three surfaces: discovery files (`llms.txt`, `robots.txt`, sitemaps), structural signals (semantic headings, canonical links, structured data, markdown mirrors), and protocol manifests (MCP Server Cards, A2A Agent Cards, agents.json, agent-permissions.json).\n\n## Why does AI agent readability matter for SEO?\n\nAI agents crawl what loads cleanly and cite what parses correctly. The incentives are sharp: a [July 2025 Pew Research study](https://www.pewresearch.org/short-reads/2025/07/22/google-users-are-less-likely-to-click-on-links-when-an-ai-summary-appears-in-the-results/) found users who encounter a Google AI Overview click on a source link only about 8% of the time — roughly half the rate of searches without an AI summary. Princeton’s [GEO study (KDD 2024)](https://arxiv.org/abs/2311.09735) measured that adding source citations to a page lifted its inclusion in AI answers by roughly 40%, with statistics and quotations close behind. Sites that score well get summarised accurately and referred qualified traffic; sites that score poorly get paraphrased (badly) or skipped entirely. Unlike traditional SEO, you don’t need to rank on page 1 — structured, citable content gets pulled even when organic rank is low.\n\n## What does the agent readability scanner check?\n\n-   **Vercel Agent Readability Spec** — 15 site-wide checks (llms.txt, robots.txt, sitemap.xml, sitemap.md, AGENTS.md, HTTPS, OpenAPI) plus 23 per-page checks (meta tags, JSON-LD, headings, markdown mirrors, content negotiation, code-block language tags, JS-rendering dependency).\n-   **llmstxt.org** — 10 checks against the llms.txt format (H1 present, blockquote summary, H2 sections, link format, content-type, llms-full.txt).\n-   **Agent protocols** — 12 checks covering MCP Server Cards (SEP-1649 / [RFC 9728](https://datatracker.ietf.org/doc/html/rfc9728) OAuth Protected Resource metadata), A2A Agent Cards (a2a.proto v1.0.0), Wildcard agents.json, agent-permissions.json, UCP (Universal Commerce Protocol), x402 (HTTP 402 Payment Required), and NLWeb (natural-language /ask endpoint).\n\n## How is the agent readability score calculated?\n\n`score = round((passed checks / total checks) × 100)`. The denominator compounds: 15 site-wide + (23 per-page × number of pages scanned). A systemic issue like a missing canonical link on every page compounds significantly. Ratings: 90-100 Excellent, 70-89 Good, 50-69 Fair, 0-49 Needs Improvement.\n",
  "markdownStats": {
    "images": 0,
    "links": 3,
    "tables": 0,
    "codeBlocks": 0,
    "headings": 4
  },
  "tokens": {
    "htmlTokens": 71912,
    "markdownTokens": 635,
    "reduction": 71277,
    "reductionPercent": 99
  },
  "score": {
    "score": 83,
    "grade": "B",
    "dimensions": {
      "semanticHtml": {
        "score": 92,
        "weight": 20,
        "grade": "A",
        "checks": {
          "uses_article_or_main": {
            "score": 100,
            "weight": 20,
            "details": "Has <main>"
          },
          "proper_heading_hierarchy": {
            "score": 100,
            "weight": 25,
            "details": "Clean heading hierarchy"
          },
          "semantic_elements": {
            "score": 59,
            "weight": 20,
            "details": "6 semantic elements, 28 divs (ratio: 18%)"
          },
          "meaningful_alt_texts": {
            "score": 100,
            "weight": 15,
            "details": "No images found"
          },
          "low_div_nesting": {
            "score": 100,
            "weight": 20,
            "details": "Avg div depth: 1.6, max: 4"
          }
        }
      },
      "contentEfficiency": {
        "score": 63,
        "weight": 25,
        "grade": "C",
        "checks": {
          "token_reduction_ratio": {
            "score": 100,
            "weight": 40,
            "details": "99% token reduction (HTML→Markdown)"
          },
          "content_to_noise_ratio": {
            "score": 0,
            "weight": 30,
            "details": "Content ratio: 1.0% (2337 content chars / 225128 HTML bytes)"
          },
          "minimal_inline_styles": {
            "score": 100,
            "weight": 15,
            "details": "0/266 elements with inline styles (0.0%)"
          },
          "reasonable_page_weight": {
            "score": 50,
            "weight": 15,
            "details": "HTML size: 220KB"
          }
        }
      },
      "aiDiscoverability": {
        "score": 82,
        "weight": 25,
        "grade": "B",
        "checks": {
          "has_llms_txt": {
            "score": 100,
            "weight": 20,
            "details": "llms.txt exists and is valid"
          },
          "has_robots_txt": {
            "score": 100,
            "weight": 10,
            "details": "robots.txt exists"
          },
          "robots_allows_ai_bots": {
            "score": 100,
            "weight": 15,
            "details": "All major AI bots allowed"
          },
          "has_sitemap": {
            "score": 100,
            "weight": 10,
            "details": "Sitemap found"
          },
          "supports_markdown_negotiation": {
            "score": 60,
            "weight": 25,
            "details": "Application level — Content negotiation, <link> tag"
          },
          "has_content_signals": {
            "score": 60,
            "weight": 20,
            "details": "robots.txt: search=yes, ai-input=yes, ai-train=yes"
          }
        }
      },
      "structuredData": {
        "score": 100,
        "weight": 15,
        "grade": "A",
        "checks": {
          "has_schema_org": {
            "score": 100,
            "weight": 30,
            "details": "JSON-LD found: Organization, WebSite, Service, SoftwareApplication, BreadcrumbList, FAQPage"
          },
          "has_open_graph": {
            "score": 100,
            "weight": 25,
            "details": "All OG tags present"
          },
          "has_meta_description": {
            "score": 100,
            "weight": 20,
            "details": "Meta description: 143 chars"
          },
          "has_canonical_url": {
            "score": 100,
            "weight": 15,
            "details": "Canonical URL present"
          },
          "has_lang_attribute": {
            "score": 100,
            "weight": 10,
            "details": "lang=\"en\""
          }
        }
      },
      "accessibility": {
        "score": 87,
        "weight": 15,
        "grade": "B",
        "checks": {
          "content_without_js": {
            "score": 100,
            "weight": 40,
            "details": "Content available without JavaScript"
          },
          "reasonable_page_size": {
            "score": 80,
            "weight": 30,
            "details": "Page size: 220KB"
          },
          "fast_content_position": {
            "score": 75,
            "weight": 30,
            "details": "Main content starts at 26% of HTML"
          }
        }
      }
    }
  },
  "recommendations": [
    {
      "id": "improve_content_ratio",
      "priority": "critical",
      "category": "contentEfficiency",
      "titleKey": "rec.improve_content_ratio.title",
      "descriptionKey": "rec.improve_content_ratio.description",
      "howToKey": "rec.improve_content_ratio.howto",
      "effort": "moderate",
      "estimatedImpact": 6,
      "checkScore": 0,
      "checkDetails": "Content ratio: 1.0% (2337 content chars / 225128 HTML bytes)"
    }
  ],
  "llmsTxtPreview": "# Agent Ready\n\n> AI agent readability scanner. Runs 60 checks against the Vercel Agent Readability Spec, llmstxt.org, and agent-protocol specs (MCP, A2A, agents.json, agent-permissions.json), returning a 0–100 score and per-check fix guidance.\n\n## Documentation\n- [API & integrations](https://agent-ready.dev/docs/api)\n- [REST API reference](https://agent-ready.dev/docs/api/reference)\n\n## Main\n- [Agent Ready — AI Agent Readability Checker](https://agent-ready.dev/): Score any website against the Vercel Agent Readability Spec and llmstxt.org standard. Get actionable fixes to make your…\n- [Pricing](https://agent-ready.dev/pricing)\n- [Sign in](https://agent-ready.dev/sign-in)\n- [Agent Readability Score](https://agent-ready.dev/agent-readability-score)\n- [llms.txt Checker](https://agent-ready.dev/llms-txt-checker)\n- [AGENTS.md Validator](https://agent-ready.dev/agents-md-validator)\n- [MCP Card Validator](https://agent-ready.dev/mcp-card-validator)\n- [A2A Card Validator](https://agent-ready.dev/agent-card-validator)\n- [agents.json Validator](https://agent-ready.dev/agents-json-validator)\n- [Permissions Validator](https://agent-ready.dev/agent-permissions-validator)\n\n## Legal\n- [Privacy Policy](https://agent-ready.dev/privacy)\n- [Terms of Service](https://agent-ready.dev/terms)\n\n",
  "llmsTxtExisting": "# Agent Ready\n\n> 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.\n\nUse 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).\n\nAgent Ready checks three areas of agent readability:\n\n- Discovery — Can AI agents find your pages? (llms.txt, sitemaps, robots.txt)\n- Structure — Can agents parse your pages? (meta tags, headings, structured data, markdown mirrors)\n- Context — Can agents understand your content? (skill files, content negotiation, code documentation)\n\nLast updated: 2026-05-28. 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.\n\n## Recommended Starting Pages\n\nNew to agent readability? Start here:\n\n- [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\n- [Methodology](https://agent-ready.dev/methodology): how the 0–100 score is computed across all 60 checks\n- [MCP vs A2A vs agents.json](https://agent-ready.dev/mcp-vs-a2a-vs-agents-json): choose the right agent-discovery protocol\n\n## For developers\n\nAgent Ready exposes a REST API and an MCP server for programmatic use. MCP server: https://agent-ready.dev/api/v1/mcp.\n\n- [Agent Ready quickstart](https://agent-ready.dev/quickstart): first scan in 60 seconds — curl, Node, Python, MCP\n- [Agent authentication for Agent Ready](https://agent-ready.dev/auth): how agents discover, register, use, and revoke credentials (WorkOS auth.md aligned)\n- [OpenAPI 3.1 spec](https://agent-ready.dev/api/v1/openapi.json): every endpoint, request/response schema, auth requirement\n- [MCP server endpoint](https://agent-ready.dev/api/v1/mcp): streamable-http MCP server, Bearer-token authenticated\n- [MCP server card](https://agent-ready.dev/.well-known/mcp/server-card.json): SEP-1649 discovery JSON for one-click MCP install\n- [OAuth protected-resource metadata](https://agent-ready.dev/.well-known/oauth-protected-resource): RFC 9728 auth discovery document\n\n## Pages\n\n- [Home](https://agent-ready.dev): Enter a URL to scan your site\n- [Agent Readability Score](https://agent-ready.dev/agent-readability-score): Get your Vercel Agent Readability score\n- [llms.txt Checker](https://agent-ready.dev/llms-txt-checker): Validate your llms.txt file against the llmstxt.org spec\n- [AGENTS.md Validator](https://agent-ready.dev/agents-md-validator): Check your skill file for coding agents\n- [MCP Server Card Validator](https://agent-ready.dev/mcp-card-validator): Validate your MCP server card at /.well-known/mcp.json\n- [A2A Agent Card Validator](https://agent-ready.dev/agent-card-validator): Validate your A2A agent card at /.well-known/agent-card.json\n- [agents.json Validator](https://agent-ready.dev/agents-json-validator): Validate your Wildcard agents.json manifest\n- [agent-permissions.json Validator](https://agent-ready.dev/agent-permissions-validator): Validate your agent-permissions.json manifest\n- [API & integrations](https://agent-ready.dev/docs/api): REST API, MCP server, and CI/CD action for Pro subscribers\n- [Quickstart](https://agent-ready.dev/quickstart): Run your first Agent Ready scan in under 60 seconds — curl, Node, Python, MCP\n- [Authentication](https://agent-ready.dev/auth): How agents authenticate to Agent Ready — Bearer tokens, OAuth protected-resource metadata, WWW-Authenticate discovery\n- [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\n\n## Guides\n\n- [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\n- [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\n- [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\n- [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\n- [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\n\n## Discovery\n\nAgent Ready implements the conventions it audits — these first-party manifests are live and machine-readable:\n\n- [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)\n- [A2A agent card](https://agent-ready.dev/.well-known/agent-card.json): A2A v1.0.0 capability and skill discovery\n- [agents.json](https://agent-ready.dev/.well-known/agents.json): Wildcard v0.1.0 OpenAPI-backed action manifest\n- [agent-permissions.json](https://agent-ready.dev/.well-known/agent-permissions.json): declared agent action permissions\n- [API catalog](https://agent-ready.dev/.well-known/api-catalog): RFC 9727 linkset of the public API, its OpenAPI description, and the MCP endpoint\n- [OAuth protected-resource metadata](https://agent-ready.dev/.well-known/oauth-protected-resource): RFC 9728 metadata for the MCP endpoint\n- [Schema feed](https://agent-ready.dev/schema/pages.json): JSON-LD @graph of primary pages with dateModified, indexed by /schemamap.xml\n\n## Specs\n\n- [Vercel Agent Readability Spec](https://vercel.com/kb/guide/agent-readability-spec): The full specification we check against\n- [llmstxt.org](https://llmstxt.org): The llms.txt file specification\n- [Model Context Protocol (2025-11-25)](https://modelcontextprotocol.io): MCP server cards and OAuth protected-resource discovery\n- [A2A Protocol (v1.0.0)](https://a2a-protocol.org): Agent-to-agent discovery at `/.well-known/agent-card.json`\n- agents.json (Wildcard v0.1.0): discovery manifest checked at `/agents.json` or `/.well-known/agents.json`\n- agent-permissions.json: agent permissions manifest checked at `/.well-known/agent-permissions.json`\n\n## Optional\n\nSecondary material — useful for deep dives, but safe to skip when context is tight:\n\n- [Pricing](https://agent-ready.dev/pricing): Free and Pro tiers\n- [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\n- [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\n- [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\n- [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+\n- [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\n- [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",
  "emergingProtocols": {
    "oauthDiscovery": {
      "exists": false,
      "url": "https://agent-ready.dev/.well-known/oauth-authorization-server"
    },
    "mcpServerCard": {
      "exists": true,
      "url": "https://agent-ready.dev/.well-known/mcp.json",
      "name": "agent-ready",
      "version": "1.0.0",
      "description": "AI agent readability scanner. Scan any site and get scores + per-check remediation via MCP tools.",
      "transport": null,
      "tools": 3,
      "resources": null,
      "prompts": null
    },
    "a2aAgentCard": {
      "exists": false,
      "url": "https://agent-ready.dev/.well-known/agent.json"
    },
    "count": 1
  },
  "snippets": []
}

Utilisez notre API pour obtenir ceci de manière programmatique (bientôt disponible)