Scan at scaleSites publishing agent-ready signals
Sites publishing agent-ready signals
A site-wide report: one row per host, over the access rows the crawl emitted.
What this report returns
Adoption overview: one row per agent-ready site-wide signal detected on the crawled site (access policies, sitemaps, the llms.txt index, Markdown negotiation, the API catalog, MCP server card, MCP authorization, OpenAPI, NLWeb, UCP, Web Bot Auth, A2A agent card). Signal Valid false means the signal is published but misconfigured; Signal Defects names each failed check — open that signal's own report to filter by defect.
Signal Assessment says whether the verdict covers the whole signal: "partial" means a per-host budget or read cap stopped us short, so Valid there means "no defect in what was read". Signals a site never adopted don't appear (absence is not a failure).
The columns it shows
Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.
- Host
host - Signal
signal - Signal Valid
signalValid - Signal Assessment
signalAssessment - Signal Defects
signalDefects - Signal Findings
signalFindings
Running it
This report comes with Agentic Readiness in Lumar and appears on every crawl of any project that has it turned on. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.