No agent interface discovery surface

What it detects

None of the common machine-interface descriptors (agents.txt, agents.json, an OpenAPI spec, SKILL.md, an A2A agent card) are published.

Why it matters

At least one machine-readable interface descriptor gives an agent a starting point for programmatic interaction beyond scraping the rendered page.

How to fix

- Check for any of: `agents.txt`, `agents.json`, `/.well-known/ai-plugin.json`, an OpenAPI spec (`/openapi.json`), `SKILL.md`, an A2A agent card, or OAuth discovery metadata. - Publish at least one machine-readable interface descriptor — an OpenAPI spec at `/openapi.json` is the most broadly understood starting point if the site already has a documented API; `agents.txt` is a lower-effort alternative if not. - Keep the descriptor accurate: list only endpoints that are actually available to external/agent callers, with real request/response schemas. - Verify: `curl` the chosen discovery path, confirm valid JSON/YAML (or well-formed Markdown for `agents.txt`/`SKILL.md`), and that it lists at least one real, callable capability.

References

• Model Context Protocol specification
• WAI-ARIA 1.2 (W3C)