agentready-rho.vercel.app

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ✓Sitemap present & freshrequired4/4

  Sitemap at https://agentready-rho.vercel.app/sitemap.xml: 46 entries, freshest <lastmod> 2026-08-18 (0 days ago)

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✗Brand search discoverabilityrequired0/4

  Neither search ("AgentReady", "AgentReady developer tools") cited agentready-rho.vercel.app. Cited instead: https://www.agentready.website/, https://agent-ready.dev/docs, https://github.com/sundios/AgentReady, https://www.agentready.it.com/, https://agent-ready.dev

  fix → Your domain doesn't surface when agents search "AgentReady". Strengthen brand pages, structured data, and third-party citations (docs portals, GitHub, directories).

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• ✓MCP registry listingsrecommended4/4

  /.well-known/mcp/server-card.json serves JSON; searched "agentready-rho.vercel.app" and "AgentReady": listed in official MCP registry (1 of 3 reachable registries)

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✓robots.txt present & parseablerequired2/2

  /robots.txt parses: 11 User-agent group(s), 1 Sitemap line(s)

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✓AI crawler policyrequired5/5

  All 12 AI crawler user-agents (GPTBot, ClaudeBot, PerplexityBot, …) are allowed at / by robots.txt

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✓Content Signals directivesemerging2/2

  1 valid Content-Signal line(s) in robots.txt (e.g. `Content-Signal: search=yes, ai-input=yes, ai-train=no`)

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✓Agent user-agent paritybetarequired4/4

  All three UAs get HTTP 200; bot bodies are ClaudeBot 100%, GPTBot 100% of the browser response (26072 bytes)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✓agents.mdrecommended3/3

  Found https://agentready-rho.vercel.app/agents.md: 1533 chars of markdown with 4 heading(s)

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "AgentReady scans websites to assess their readiness for AI agents, providing detailed reports and actionable fixes to improve agent discoverability, access, usability, and payment capabilities.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ✓OpenGraph / social metadatarecommended2/2

  Homepage has og:title, og:description, and og:image (twitter:card="summary_large_image" present)

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✓llms.txtrecommended4/4

  /llms.txt is valid llmstxt.org shape: H1 "AgentReady", 8 markdown link(s)

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✓llms-full.txtbonusrecommended2/2

  /llms-full.txt serves 25174 chars of markdown

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✓JSON-LD structured datarequired4/4

  5 JSON-LD block(s) on homepage and pricing page (types: Organization, WebSite, Product); Organization block is well-formed

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✓Markdown content negotiationrecommended3/3

  https://agentready-rho.vercel.app/ returns markdown for `Accept: text/markdown` (content-type text/markdown)

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• ◐Developer resource discoverabilityrecommended1/3

  Search "AgentReady API documentation" cited no agentready-rho.vercel.app URL — only third-party content describes your API: https://agentready.cloud/docs/quickstart, https://agentready.cloud/, https://pypi.org/project/agentready-sdk/

  fix → Create a crawlable /docs or developers.agentready-rho.vercel.app hub and link it from your homepage footer so search-grounded agents find your official API docs.

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• ✓OpenAPI spec discoverablerequired5/5

  OpenAPI spec found at https://agentready-rho.vercel.app/api/openapi.json (version 3.1.0)

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✓Docs discoverablerequired4/4

  Docs found at https://agentready-rho.vercel.app/docs (via homepage link, 9610 chars of readable text)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ✓MCP server discoveryrequired5/5

  Valid MCP server card at https://agentready-rho.vercel.app/.well-known/mcp/server-card.json: name "AgentReady", endpoint https://agentready-rho.vercel.app/api/mcp

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• ✓npm SDKrecommended2/2

  Official npm package "@reloadapp/agentready-cli" (verified via linked from the site's own docs): latest 0.1.0 published 2026-08-18

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• ✗PyPI SDKrecommended0/2

  No official PyPI SDK found: probed 4 candidate(s) (agentready, agentready-sdk, agentreadyapi, agentready-python) — found but not domain-verified: agentready, agentready-sdk

  fix → Publish an official Python SDK (suggest "agentready") with your domain in the project URLs so agents can verify it's official.

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• ✓OpenAPI validity & qualityrecommended3/3

  Spec at https://agentready-rho.vercel.app/api/openapi.json: 7/7 quality criteria passed (7 paths, 7 operations)

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ✓Docs qualityrecommended2.9/3

  Docs at https://agentready-rho.vercel.app/docs scored clarity 5/5, completeness 4/5, runnable examples 5/5, agent-friendliness 5/5 (mean 4.8/5)

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• ✓Quickstart / getting startedrecommended2/2

  Quickstart found: https://agentready-rho.vercel.app/docs#quickstart (linked from https://agentready-rho.vercel.app/docs) returns 200 with a code block

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• ✓MCP tool qualityrecommended3/3

  11 tools listed at https://agentready-rho.vercel.app/api/mcp; all pass description, schema, and naming lint

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://agentready-rho.vercel.app/ upgrades to https in 1 hop(s), 1 redirect(s) total, final HTTP 200; HSTS present

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ✓Response speed & weightrequired1/1

  Homepage TTFB 294ms, payload 25KB, Content-Encoding: br

  Measured homepage TTFB, payload size, and compression

  report issue
• ✓security.txtrecommended1/1

  Valid security.txt at https://agentready-rho.vercel.app/.well-known/security.txt: Contact mailto:security@reload.app, Expires 2027-08-18

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• ✗OAuth authorization server metadatarecommended0/3

  Neither /.well-known/oauth-authorization-server nor /.well-known/openid-configuration resolved (HTTP 404 / HTTP 404)

  fix → Serve RFC 8414 metadata at /.well-known/oauth-authorization-server with PKCE (S256) and a registration_endpoint so agents can self-onboard.

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• ✗OAuth protected resource metadatarecommended0/2

  No RFC 9728 metadata: https://agentready-rho.vercel.app/.well-known/oauth-protected-resource → HTTP 404

  fix → Serve RFC 9728 metadata at /.well-known/oauth-protected-resource naming your authorization servers so agents can discover how to authenticate.

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• ✓Auth documentationrecommended2/2

  Auth documentation found at https://agentready-rho.vercel.app/auth.md (2014 chars, with code examples)

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ✓Pricing discoverablerequired5/5

  Pricing page found at https://agentready-rho.vercel.app/pricing (via homepage link) with legible price signals ("$0free plan, no card requiredS").

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• ✓Machine-readable pricingrecommended5/5

  Offer JSON-LD found on pricing page — machine-readable without inference (1 Product block(s) with an offers property at https://agentready-rho.vercel.app/pricing).

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✗x402 payment supportbonusrecommended0/2

  /.well-known/x402 returned HTTP 404. API probe GET https://agentready-rho.vercel.app/api/checks returned HTTP 200 without x402 payment requirements. No x402 support detected (bonus check — absence costs nothing).

  fix → Support x402: serve payment requirements at /.well-known/x402, or answer unauthenticated API calls with HTTP 402 plus an x402 payment-requirements payload (x402Version, accepts[]).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned llms.txt, agents.md, docs page (https://agentready-rho.vercel.app/docs), OpenAPI spec (https://agentready-rho.vercel.app/api/openapi.json); /.well-known/ap2 returned HTTP 404.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned llms.txt, agents.md, docs page (https://agentready-rho.vercel.app/docs), OpenAPI spec (https://agentready-rho.vercel.app/api/openapi.json); /.well-known/acp returned HTTP 404.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned llms.txt, agents.md, docs page (https://agentready-rho.vercel.app/docs), OpenAPI spec (https://agentready-rho.vercel.app/api/openapi.json).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• ✓MCP handshake & tools listrequired4/4

  MCP handshake OK at https://agentready-rho.vercel.app/api/mcp: server "agentready" (protocol 2025-06-18), 11 tool(s) listed

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✗NLWeb endpointemerging0/1

  No NLWeb endpoint detected: /.well-known/nlweb.json returned HTTP 404 (text/html); GET /ask?query=hello returned HTTP 404 (text/html)

  fix → Consider exposing an NLWeb /ask endpoint (and /.well-known/nlweb.json) for conversational access to your content.

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ✓Semantic HTML structurerequired3/3

  5/6 semantic signals present on the homepage (missing: text-to-markup ratio ≥ 0.10)

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 1611 chars of visible text without JavaScript

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✓Accessibility basicsrequired2/2

  Homepage accessibility: 5/5 checks passed

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue