Context
The ARD v0.91 proposal, dated August 26, 2026, defines JSON-LD descriptions for discoverable agentic resources and specifies a federated discovery model with publisher-hosted manifests and searchable registries.
What changed
Version 0.91 expresses resource entries with JSON-LD namespaces and requires conformant consumers resolving a domain to fetch /.well-known/ard.json and honor rel=ard. The earlier ai-catalog.json path and rel=ai-catalog are optional compatibility lookups.
Why it matters
Publishers relying solely on the earlier manifest path risk being invisible to conforming ARD consumers; the proposal also separates semantic relevance ranking from identity and trust verification.
Visibility OS interpretation
Visibility OS classifies this as a standards-proposal evolution in agentic capability discoverability. It does not imply deployment across all AI agents, nor improved citations or search ranking for normal web content.
What remains uncertain
Will registries implement v0.91 consistently? Which agents consume ard.json in production? Will the proposal be ratified or the manifest path change again?
Evidence claims
The ARD v0.91 proposal dated August 26, 2026 specifies JSON-LD agentic resource entries and requires conformant domain resolvers to fetch /.well-known/ard.json, while the earlier ai-catalog.json lookup is optional.
Related historical records
Google announces Agentic Resource Discovery for federated agent-capability discovery
This record expands the linked event.