How to make your API agent-ready (a prioritized checklist)
The fixes that move your Discry Score the most, in order.
- Read
- 8 min
- Updated
- 2026-06-30
Start with discovery
Most APIs lose more points on Discovery than Comprehension — the signature finding across the Index. Ship an OpenAPI spec, a focused llms.txt, and an AGENTS.md first; add an MCP manifest at .well-known/mcp.json if you expose tools.
Then tighten comprehension
Rewrite endpoint descriptions to be task-oriented (“charge a customer,” not “POST /charges”), add realistic runnable examples, document multi-step workflows end to end, and write real error-recovery guidance.
Then keep it passing
Discoverability regresses silently on every deploy. Re-scan after any docs change so a refactor that drops your llms.txt doesn’t quietly cost you the agent channel. The free scan is unlimited; a Fix Kit includes one official confirmation re-run, and the Discry on your repo GitHub app (in development) will check each docs PR before it ships.
Want the prioritized list for your API specifically? Run a free scan.
See where your API stands.
Drop your docs URL. The scan probes the same signals this guide describes — in about a minute, free.