agent-ready-ard

# Implement ARD (Agentic Resource Discovery) Publish a capability manifest so agents can discover your MCP servers, A2A agents, skills and API tools, per the [ARD spec](https://agenticresourcediscovery.org/) and the [ai-catalog](https://github.com/Agent-Card/ai-catalog) data model. The ARD spec is a v0.9 draft, so the scanner validates structure only and reports non-conformant identifiers and media types without failing the check. Note that `specVersion` refers to the ai-catalog data model, not the ARD spec version, which is why the example below reads `1.0`. The scanner only requires it to be a non-empty string. ## Requirements - Serve `/.well-known/ai-catalog.json` from the origin root with `Content-Type: application/json`, HTTP 200, and `Access-Control-Allow-Origin: *` - Include a `specVersion` string and a non-empty `entries` array - Add a `host` object with `displayName` and a stable `identifier` - Each entry needs an `identifier`, a `displayName`, and a `type` media type - Each entry needs **exactly one** of `url` or `data` — never both, never neither (spec §3.4) - Use `urn:air:<your-fqdn>:<namespace>:<name>` for entry identifiers - Add 2-5 `representativeQueries` per entry so registries can build semantic embeddings ## Example ```json { "specVersion": "1.0", "host": { "displayName": "Example Systems", "identifier": "did:web:example.com" }, "entries": [ { "identifier": "urn:air:example.com:server:weather", "displayName": "Wea...