apicurio.local is Not Agent-Ready to agents.

What we found

• —An agent looking for this API would fail at the first step: the documentation host apicurio.local does not resolve to any public IP (DNS resolution failed), so there is no reachable homepage, robots.txt, or docs to read.
• —Because nothing was reachable, every discovery signal (robots.txt, llms.txt, OpenAPI spec, sitemap, MCP registry listings, AGENTS.md) scored fail — an agent has zero surface to discover or authenticate against.
• —No documentation pages could be scraped, so every comprehension check (endpoint descriptions, examples, workflows, error recovery) also scored fail; the score reflects an unreachable target, not assessed-and-poor content.
• —The domain appears to be a placeholder/internal address (.local TLD) rather than a live public documentation site, meaning this entry is not currently scannable as-is.
• —No positive signal could be recorded — a re-scan requires a resolvable public documentation URL.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

1. 01Replace the placeholder apicurio.local with the real, publicly resolvable documentation URL (e.g. the Apicurio Registry docs site) in the scan queue, then re-run the scan.
2. 02Confirm the documentation domain resolves over public DNS and serves content over HTTPS before queuing — .local addresses are non-routable and cannot be assessed.
3. 03Once reachable, publish baseline discovery signals — an llms.txt indexing the core API docs and a publicly linked OpenAPI spec — which are the highest-impact quick wins for agent discoverability.
4. 04Ensure the docs render as clean, crawlable HTML/markdown (not auth-gated or JS-only) so an agent can parse endpoint and workflow content.