Per the Google Developers Blog, Google announced the open Agentic Resource Discovery specification, a web standard for publishing, discovering, and verifying AI tools, skills, and agents across disparate registries and platforms. Help Net Security and ITSecurityNews indexed coverage noting the specification addresses gaps where agents cannot easily find or connect to resources hosted by other teams or organizations. The spec is framed as an interoperable discovery and verification layer that lets tools and services advertise capabilities so agents can locate and validate them across the web. Google positions the specification as an open standard on the developer blog; the company blog post contains the primary announcement and technical framing.
What happened
On June 17, 2026, Google published the Agentic Resource Discovery (ARD) specification, an open protocol for publishing, discovering, and verifying AI capabilities across the web. Per the Google Developers Blog, the spec was developed with partners across the industry: launch contributors include Cisco, Databricks, GitHub, GoDaddy, Google, Hugging Face, Microsoft, Nvidia, Salesforce, ServiceNow, and Snowflake. The spec is licensed under Apache 2.0 and builds on the AI Catalog data model from the Linux Foundation's AI Catalog Working Group.
Technical details
ARD addresses three questions agents need answered at runtime: where does the right capability live, which one should I use, and how do I verify it is safe to connect to. The specification defines two primitives: a static ai-catalog.json manifest hosted at a well-known path on an organization's domain, and a registry API that crawls and indexes published catalogs and returns ranked matches to natural-language discovery queries. Per the Hugging Face blog, ARD sits entirely before invocation - it finds the right resource; the resource is then called through its own native protocol (MCP, A2A, OpenAPI, etc.). It is explicitly not a replacement for MCP, A2A, or Skills.
Reference implementations
Hugging Face launched a Discover Tool (huggingface-hf-discover.hf.space) that wraps the Hub's semantic search over Spaces, Skills, and MCP servers in the ARD envelope, making thousands of capabilities searchable via the specification. Google Cloud's Agent Registry in Gemini Enterprise Agent Platform also implements ARD with enterprise governance features including namespaced URNs, egress policies, and cryptographic trust manifests.
Context and significance
Standards for capability discovery sit at the intersection of agent orchestration, API metadata, and service governance. The ARD model is federated - organizations can run their own registries, and registries can cross-reference each other without a central catalog. The spec includes guides for connecting Claude, ChatGPT, GitHub Copilot, Microsoft Copilot, and Gemini as ARD clients.
What to watch
Look for adoption of the ai-catalog.json well-known URI by tool and service providers; watch how registry trust and attestation layers evolve; and monitor whether ARD federation becomes a de-facto standard across the MCP and A2A ecosystems given the breadth of contributors already signed on.
Scoring Rationale #
ARD is a multi-org open specification (11 major contributors including Google, Microsoft, Nvidia, Salesforce, and Snowflake) that addresses a real gap in agentic ecosystems: runtime capability discovery across organizational boundaries. With reference implementations already live from Hugging Face and Google Cloud, and connection guides for all major AI assistants, this is notable infrastructure for practitioners building multi-agent systems, placing it at the upper end of the Notable band.
Practice with real Ad Tech data
90 SQL & Python problems · 15 industry datasets
[Active Search Campaigns by BudgetEasy](/problems/sql/active-search-campaigns-by-budget)
[High CPC Clicks & Poor Landing PagesMedium](/problems/sql/high-cpc-clicks-poor-landing-page)
[Campaign ROAS by Attribution ModelHard](/problems/sql/campaign-roas-by-attribution-model)
250 free problems · No credit card