# Lumar Agentic Readiness Scanner

Check which agent-facing technologies a website publishes, and whether each one is implemented correctly.

## What it checks

Site-wide: robots.txt, AI-bot rules, Content Signals, ai.txt, TDMRep, XML sitemap, MCP server card, MCP
authorization, OpenAPI description, NLWeb endpoint, UCP profile, Web Bot Auth directory, A2A agent card.

Per URL, when you give it one: canonical, editorial metadata, JSON-LD, language and encoding, HTTP Link
headers, markdown twin, Product schema, schema:Action, server-side rendering, WebMCP.

## How to use it

- Web: https://agentic-readiness.lumar.io/
- Share a report: https://agentic-readiness.lumar.io/r/example.com
- API: https://agentic-readiness.lumar.io/api/scan?domain=example.com (server-sent events)
- MCP: https://agentic-readiness.lumar.io/mcp (Streamable HTTP; tools: scan_site, search_docs, build_agent_file, fit_for_sector)
- OpenAPI: https://agentic-readiness.lumar.io/openapi.json

## Use all of this from your own agent

Everything on this site is available to an agent, not just to a person. That is the same standard we hold other sites to, so it would be a poor look to publish a scanner that only a human can drive. Connect it to your AI client and it can scan a site, read the reference, build the file and hand you the publishing steps without anyone opening this page.

The steps, the tool names and every address are on their own page: https://agentic-readiness.lumar.io/agents (https://agentic-readiness.lumar.io/agents.md).

## In your pipeline

The host-level checks also run as a command: https://agentic-readiness.lumar.io/cli (https://agentic-readiness.lumar.io/cli.md). One npx line,
JSON out, and a build that fails on a broken implementation but never on a technology you have not adopted.

## Notes

Absence is never scored. Most sites publish few of these technologies, and that is not a fault; the scan
surfaces the ones that are published and implemented incorrectly.