From 74baee8063b8d0082c51417d0af4e7891ba310f1 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 13 Jul 2026 11:27:46 +0000 Subject: [PATCH] fix(ard-registry-builder): align registry-api.md with OpenAPI spec - Remove incorrect 'max 100' for POST /search pageSize; the OpenAPI spec only defines maximum: 100 for GET /agents, not for POST /search. - Add application/ai-registry (short form) as a valid registry referral type alongside application/ai-registry+json, per the OpenAPI enum in spec/schemas/ard.openapi.yaml. Source: https://github.com/ards-project/ard-spec/blob/afd447d88ed165427687d8af37e8d42398552b56/spec/schemas/ard.openapi.yaml#L189-L194 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- skills/ard-registry-builder/references/registry-api.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/skills/ard-registry-builder/references/registry-api.md b/skills/ard-registry-builder/references/registry-api.md index a7a3922..3c935da 100644 --- a/skills/ard-registry-builder/references/registry-api.md +++ b/skills/ard-registry-builder/references/registry-api.md @@ -39,7 +39,7 @@ must exist regardless. ## POST /search (required) Request adds root-level `federation` (`auto` default / `referrals` / `none`), `pageSize` -(default 10, max 100), `pageToken`. +(default 10), `pageToken`. Response envelope: ```json @@ -121,6 +121,6 @@ as a cross-check. ## Discovering a registry's base URL Inside a static manifest, a dynamic registry advertises itself as an entry of type -`application/ai-registry+json` whose `url` is the API base. Clients read that `url` and then -call `POST {base}/search`. DNS `SRV` records under `_search._agents.` are an -alternative discovery path. +`application/ai-registry+json` (or the shorter `application/ai-registry`) whose `url` is the +API base. Clients read that `url` and then call `POST {base}/search`. DNS `SRV` records under +`_search._agents.` are an alternative discovery path.