Diary / field note
ARD is the boring agent standard that matters
Agents do not just need better reasoning. They need a trusted way to find the right tools, skills and other agents at runtime.
Google has announced Agentic Resource Discovery, or ARD.
It is not a flashy model launch.
That is why it matters.
ARD is an open specification for publishing, discovering and verifying AI capabilities across the web.
In plain English: how does an agent find the right tool, skill, MCP server, API or other agent when it needs one?
Right now, most agent systems are wired by hand.
You connect the tools. You preload the context. You tell the agent what it can use. If the capability is not already inside the system, it may as well not exist.
That is fine for demos.
It does not work for the agentic web.
Google frames ARD around three questions:
- where does the right capability live
- which capability should the agent use
- how does the agent verify it is safe to connect
The partner list is the clue that this is more than a blog post. Microsoft says ARD is being developed with Cisco, Databricks, GitHub, GoDaddy, Google, Hugging Face, Nvidia, Salesforce, ServiceNow and Snowflake.
GitHub is also launching agent finder, built on ARD, so Copilot can discover and call MCP servers, skills, tools and agents at runtime instead of bloating the context window with everything up front.
That is the interesting shift.
The next generation of agents will not carry every tool in their backpack.
They will know how to find the right tool, verify it and connect when the job calls for it.
This is search again, but for capabilities instead of pages.
Search lit up the human web because it made unknown pages usable.
ARD is trying to light up the agent web by making unknown capabilities usable.
That is infrastructure, not hype.
And infrastructure is usually where the real shift starts.
Sources: Google Developers Blog, Microsoft Command Line