When an agent is not listed in its publisher's adagents. json (e. g. Entry is stale, mismatched path, or missing), the registry dashboard's "Publishers & properties" panel surfaces a raw client-side error instead of a clean authorization-failure message:Unexpected token '<', "<!DOCTYPE "... is not valid JSONThis reads like the fetch to adagents. json itself failed or returned HTML (e. g. A 404 page), which sent debugging down the wrong path — hostname resolution, wrong-domain fetching, etc. The actual root cause was unrelated: the publisher's adagents. json was valid and reachable, but the specific agent entry was stale (bare domain instead of the full agent URL with path), so the agent simply wasn't in the authorized_agents list.
Happy to go deeper on any of this if useful.
When an agent is not listed in its publisher's adagents. json (e. g. Entry is stale, mismatched path, or missing), the registry dashboard's "Publishers & properties" panel surfaces a raw client-side error instead of a clean authorization-failure message:Unexpected token '<', "<!DOCTYPE "... is not valid JSONThis reads like the fetch to adagents. json itself failed or returned HTML (e. g. A 404 page), which sent debugging down the wrong path — hostname resolution, wrong-domain fetching, etc. The actual root cause was unrelated: the publisher's adagents. json was valid and reachable, but the specific agent entry was stale (bare domain instead of the full agent URL with path), so the agent simply wasn't in the authorized_agents list.
Happy to go deeper on any of this if useful.