Add Desvela ARD Registry to reference implementations - #18
Open
mrenzo20 wants to merge 2 commits into
Open
Conversation
v0.91 moved the canonical path to /.well-known/ard.json, so the entry now names it. Desvela serves it and emits rel="ard". Also lists the two surfaces added on 19 Aug (agent-card.json, mcp.json), which the original text predated, and explains why both manifest paths are counted separately instead of one replacing the other. Re-verified against the v0.91 conformance suite: publisher desvela.dev PASS, publisher desvela.ai PASS, registry https://registry.desvela.dev PASS — 0 critical errors, 0 warnings on all three.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the Desvela ARD Registry to the reference implementations, alongside Hugging Face, GitHub, Cisco, Ora, and ANS.
Updated for v0.91: the entry now names
/.well-known/ard.json, and everything below was re-verified against the v0.91 conformance suite.What's distinct: it indexes the open web rather than a single platform's own resources. The crawl covers the Tranco top-100K for
ard.json, its predecessorai-catalog.json,llms.txt,agents.md,agent-card.json,mcp.json, and AI-botrobots.txtdirectives, refreshed weekly. Findings are published monthly at desvela.ai/census with the methodology in the open (canary requests against non-existent paths to exclude catch-all servers, apex-domain scope, subdomains out of scope).Implements the full protocol surface:
POST /search—query.text,filter.type,pageTokenPOST /explore(spec §7.3) — facet aggregationPOST /mcp(Streamable HTTP), with a freepreflight(domain)tool and awatch(domain, webhook_url)tool that delivers a signed webhook when a domain's agent-facing surfaces changeVerified against the spec's own conformance suite, all three PASS with 0 critical errors and 0 warnings:
One note that may be useful beyond this entry. When v0.91 moved the canonical path, the tempting change on our side was to swap the
ai-catalog.jsoncolumn for anard.jsonone. We kept both instead. The census is a month-over-month series and the count of ARD publishers in the top-100K is still single digits, so a swap would have rendered as a collapse in adoption that belonged to our crawler rather than to the web. Each surface now carries the date it entered the census, so a zero before that date reads as not measured rather than nobody published. Anyone else tracking adoption across this version boundary will hit the same thing.Disclosure: I run this registry.