Discovery · DNS
Google Proposes a Verification Layer for the Open Agentic Web
Google has published the Agentic Resource Discovery (ARD) specification, an attempt to standardize how AI agents find and verify tools, skills, and other agents across the web rather than inside a single vendor's walled garden. The pitch is explicit: existing registries are useful but siloed, each locked to a specific framework or provider.
The spec frames registries as search engines for the agentic web — they crawl published catalogs, index contents, and return matching capabilities to an agent's discovery request, along with the metadata an agent needs to verify the publisher before connecting. That verification step is the part worth noting. A plain capability listing tells an agent that something exists; it says nothing about whether the thing is what it claims to be. ARD tries to attach cryptographic verification to the discovery step itself, so trust gets established before a connection is made rather than inferred afterward.
Google is backing this with product, not just a document. Agent Registry inside its Gemini Enterprise Agent Platform is the hosted implementation, described as part of a global federated network built on the ARD spec. That's the more interesting claim: a federated model where any compliant registry can crawl and index any other publisher's catalog, instead of every platform building its own closed directory.
This matters for the discovery layer specifically because the agentic web's current failure mode isn't a lack of registries — AWS, Google, and others have all shipped their own in the past few months — it's that none of them talk to each other. An agent built on one stack can't discover, let alone verify, a tool published to a competitor's catalog. ARD is a bet that publishing a shared verification and crawling protocol matters more than any single company's registry product. Whether other platforms adopt the spec rather than treating it as Google's version of the same siloing problem is the open question; the announcement names partners but doesn't yet show a second major registry operator committing to interoperate on ARD's terms.
The spec is new enough that its real test — whether a tool published through one ARD-compliant catalog actually gets discovered and trusted by an agent running on a different vendor's stack — hasn't happened publicly yet. For now it's a standard on paper plus one company's production implementation of it.