Skip to content

A file for agents is published and cannot be read

agent-manifest-invalidminor
On this page

Why it matters

  • These are files a site publishes at fixed addresses (/.well-known/…) for agents and programs to read: OAuth metadata, MCP server and A2A agent cards, the skills index, the Web Bot Auth key directory, the agent catalog, and the UCP and ACP commerce files.
  • A broken file is worse than none: an agent finds it, believes the site offers the service, then fails to use it.
  • Not publishing them is no problem: each has its own rule or tool line that says so as information.

How to fix

Fix the file as its specification says, and send it as application/json. Protected resource metadata, for example:

json
{
  "resource": "https://api.example.com",
  "authorization_servers": ["https://auth.example.com"],
  "scopes_supported": ["orders:read"]
}

How we detect

In the agent-readiness tool alone: we ask for each address as ArablyzerBot with Accept: application/json, where robots.txt allows, read a 2xx as JSON, and ask for the fields its specification requires. A 4xx, or an HTML page in its place, means the site does not publish the file. We also ask for an address no site has: if the site answers it with 2xx, it answers every address, and a file that fails the test does not count as published.