No public API catalogue observed
This check looks for an API catalogue reference at /.well-known/api-catalog when the website shows API or developer-documentation signals. An absent public catalogue does not establish whether the business has private integrations or needs to provide an API.
Why this matters
Documented APIs can support integrations that are deliberately configured to use them. Their absence does not prove that an AI assistant cannot read the public website or recommend the business. The integration requirements depend on the actual client and use case.
How to fix it
Start with an integration requirement. If authorised clients need an API, document the supported endpoints, authentication, permissions and limits, and test that specific integration. Keep private services protected. Do not publish an API simply to obtain a better website score.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit