Why it matters
- The
Linkheader (RFC 8288) tells whoever reads the response where to find what belongs to the page. Some of its relations point agents to an API's description (service-desc), documentation (service-doc) and status (service-meta), a description of the resource (describedby), an API catalog (api-catalog) and an agent catalog (ard). - Other relations, such as
preconnectandpreload, are for the browser, not the agent. - This is information: a site with nothing to offer agents does not need them.
How to fix
Send links to what you offer agents with the home page:
http
Link: </.well-known/api-catalog>; rel="api-catalog", </openapi.json>; rel="service-desc", </docs/api>; rel="service-doc"How we detect
In the agent-readiness tool alone: we read the Link header of the page's response as it reached us, and look for one of the relations service-desc, service-doc, service-meta, describedby, api-catalog, ard and ai-catalog.