Skip to content

No /.well-known/api-catalog for AI agent discovery

This check looks for a /.well-known/api-catalog file, a standard location where AI shopping and integration agents like Perplexity, Claude Computer Use, and ChatGPT Plugins look first for machine-callable APIs (application programming interfaces). This site advertises an API or developer docs, but no api-catalog reference was found. Cloudflare's Agent Readiness Score (April 2026) treats this as the primary signal for whether AI agents can discover your API at all. Without it, your API is effectively invisible to agents that check this well-known location by default before looking anywhere else, even if your documentation itself is excellent. Your developer should create /.well-known/api-catalog.json, following the IETF draft standard (draft-ietf-httpapi-api-catalog), listing each of your APIs with a link to its OpenAPI specification. This is roughly two hours of work for a developer already familiar with your API documentation, and a one-off task rather than something that needs ongoing maintenance.

Why this matters

Cloudflare's Agent Readiness Score (April 2026) treats this as the primary signal for whether AI agents can discover your API at all. Without it, your API is effectively invisible to agents that check this well-known location by default before looking anywhere else, even if your documentation itself is excellent.

How to fix it

Your developer should create /.well-known/api-catalog.json, following the IETF draft standard (draft-ietf-httpapi-api-catalog), listing each of your APIs with a link to its OpenAPI specification. This is roughly two hours of work for a developer already familiar with your API documentation, and a one-off task rather than something that needs ongoing maintenance.