Index / ARD adoption

Who publishes an ARD manifest

Agentic Resource Discovery works when publishers describe what they offer at a well-known location on their own domain. This tracks whether that is happening, on a named watchlist and across every host our crawler has seen.

OrganisationManifestHTTP
github.compublishes200
huggingface.copublishes200
vercel.compublishes200
zapier.compublishes200
anthropic.comno manifest404
atlassian.comno manifest404
aws.amazon.comno manifest404
cisco.comno manifest404
cloudflare.comno manifest404
google.comno manifest404
microsoft.comno manifest404
netlify.comno manifest404
notion.sono manifest404
nvidia.comno manifest403
openai.comno manifest404
salesforce.comno manifest404
shopify.comno manifest404
slack.comno manifest404
snowflake.comno manifest404
stripe.comno manifest404
one GET of each known manifest path per host, /.well-known/ard.json then /.well-known/ai-catalog.json; a 200 that does not parse as an ARD manifest object is recorded as absent. Both paths are checked because v0.91 renamed the file to ard.json and the ecosystem still serves the older ai-catalog.json. Two organisations on this list operate ARD registries of their own. Publishing a manifest is a few lines of JSON: see how to publish.