Google's ARD spec is an attempt to build 'DNS-plus-search' for AI agent tools
Google has published the Agentic Resource Discovery (ARD) specification, an Apache-2.0 protocol for publishing, discovering, and verifying AI capabilities across the web, with launch contributors spanning Cisco, Databricks, GitHub, GoDaddy, Hugging Face, Microsoft, Nvidia, Salesforce, ServiceNow, and Snowflake. ARD rests on two primitives: a static ai-catalog. json manifest served from a well-known path on a domain, and a registry API that crawls those catalogs and returns ranked matches to natural-language queries. The goal is to let an agent find the right tool at runtime instead of wiring every integration by hand up front.
Why it matters: Today's hard ceiling on agents is that they can only use tools a human pre-connected — every capability is a hand-wired integration, which is exactly why 'agentic' demos rarely survive contact with a task nobody scripted. A shared discovery layer attacks that ceiling directly: if it works, agents locate and bind to services at runtime, and the integration burden shifts from O(every-pair) to O(publish-once). The launch roster is the tell that matters more than the spec itself — Google plus Microsoft, Nvidia, Salesforce, and the major data platforms is close to the coalition you'd need for an actual standard rather than a stillborn proposal, and standards in this space live or die on exactly that. The sober counterpoint is that runtime discovery also opens a real attack surface — an agent that trusts a crawled catalog is an agent that can be pointed at a malicious tool — which is why the 'verify' half of the spec, easy to overlook next to discovery, is the part that will decide whether anyone lets agents use it in production.