Agentic Resource Discovery (ARD) is a new open standard, announced in July 2026 and backed by Google, Microsoft, Salesforce, Snowflake, and ServiceNow, that lets AI agents automatically find the tools and data they need across enterprise software. It adds a discovery layer above existing agent protocols, and it signals where the real competition in enterprise AI is moving next.
For the last two years, the story of enterprise AI agents has been about connection: how to plug an agent into a database, a CRM, or an internal API. ARD is about a harder, quieter problem that comes right after connection, which is discovery. Before an agent can use a tool, it has to know the tool exists. As of mid-2026, a coalition of the largest software vendors has decided that this should work the same way everywhere.
What Is Agentic Resource Discovery?
The direct answer: ARD is a specification for publishing, searching, and discovering agent resources across a federated network of catalogs. According to the official announcement from Google's developer team, a provider publishes a machine-readable catalog on its own domain that describes the resources it makes available. An AI client can then describe a task in natural language and receive matching resources, ranked by relevance, along with details on what each one does and how to reach it.
The specification itself is deliberately narrow. As documented in the ARD project repository, ARD is described as "a federated, domain-anchored standard for cataloging, searching, and discovering agentic resources," including Model Context Protocol servers, agent-to-agent cards, skills, and APIs. It is licensed under Apache 2.0 and hosted in open repositories, and the discovery network is federated, which means no single vendor owns the registry. Each organization maintains its own catalog while participating in a shared way of describing and finding resources.
The backing coalition is what makes this notable rather than academic. Beyond the headline vendors, participants reported in July 2026 include GitHub, Hugging Face, NVIDIA, Cisco, Databricks, and GoDaddy, as covered by developer-focused press and confirmed in vendor posts such as Snowflake's. When companies that compete directly on AI platforms agree on a shared standard, it usually means they have all hit the same wall.
Why Did Rival Vendors Back the Same Standard?
The wall is fragmentation. Enterprises adopting agents in 2026 are accumulating MCP servers, custom skills, internal APIs, and specialized agents at speed. Each one has to be wired into each workflow by hand. That works for a pilot with three tools. It collapses when an organization has hundreds of internal capabilities and an agent needs to figure out, at runtime, which one fits the task in front of it.
MCP solved the connection problem. If you have followed our explainer on what the Model Context Protocol is, you know it standardized how an agent talks to a tool once the agent knows the tool exists. ARD targets the step before that. It answers the question "what is available for this task?" so that agents are not limited to a hardcoded list of integrations that a developer stitched together in advance. In practice, ARD catalogs MCP servers and agent cards rather than competing with them, which is why it can sit on top of the protocols already in production.
Some coverage framed the ARD coalition as a move to counter Anthropic and OpenAI. That framing is worth examining, because it is only half right. Our take: the standards competition in enterprise AI has moved up the stack. The protocol layer, how agents connect and talk, is largely settled around MCP and agent-to-agent standards, both now governed as open projects. The unsettled question is who defines the discovery and registry layer, the map that tells agents where everything lives. Whoever shapes that layer influences how enterprise AI capability gets found, ranked, and surfaced. That is the territory ARD stakes out, and it is why so many rivals showed up at once.
How ARD Works in Practice
The mechanism is simpler than the strategic stakes suggest.
Providers publish a catalog. An organization or software vendor describes its available agent resources in a machine-readable catalog file hosted at a known location on its own domain. This keeps each provider in control of what it exposes and to whom.
Agents query in natural language. Rather than being handed a fixed list of integrations, an agent can describe what it is trying to accomplish and let the discovery service return matching resources, ranked by how well they fit.
Discovery is federated. Catalogs across many domains form a network. There is no central gatekeeper that every request must pass through, which lowers the political and technical risk of any one vendor controlling the index.
This design matters for anyone building real systems. The value of an agent that can automate a multi-step business process depends on how reliably it can locate the right internal tool at the right moment. That reliability is the practical benefit of connecting AI agents to the systems that run daily operations through a consistent discovery layer instead of brittle, hand-maintained integration lists. When discovery is standardized, the wiring stops being a permanent maintenance tax.
What ARD Means for Your Business
Most businesses will not implement ARD this quarter, and they should not feel behind for that. The specification is early, listed as a draft, and the immediate audience is platform vendors and toolmakers, not every company running a few agents. But the direction it confirms should shape how you build now.
First, it validates a bet on open protocols. If your agent strategy is built on MCP and open agent standards, ARD extends that foundation rather than threatening it. If your strategy depends on a single vendor's proprietary connectors, the arrival of a cross-vendor discovery standard is a signal to reduce that lock-in. This is the same discipline we described in building AI into existing infrastructure: favor interfaces that survive vendor turnover.
Second, it raises the value of clean internal documentation. ARD works by describing capabilities in a structured, machine-readable way. Organizations whose internal tools, data sources, and services are already well documented and cleanly interfaced will be able to publish catalogs with little effort. Those whose systems are undocumented tribal knowledge will face that debt again, this time in front of their own agents.
Third, it reframes agent architecture. As we covered in multi-agent systems explained, coordinating many agents is already the hard part of production AI. Discovery standards are what make large fleets of agents manageable, because an agent that can find its own tools does not need a human to pre-wire every path. The businesses thinking about that coordination layer now will adopt standards like ARD smoothly when they mature, instead of retrofitting them under pressure.
How to Prepare Without Overreacting
Practical steps beat speculation here.
- Audit your integration approach. Identify where your agents connect to tools through open protocols versus proprietary connectors. The former positions you for discovery standards; the latter is where future friction lives.
- Document your internal capabilities. Treat a clean, structured inventory of your tools, APIs, and data sources as a near-term deliverable. It pays off for security and governance regardless of ARD, and it is the raw material a capability catalog needs.
- Keep watching the governance, not the hype. Standards succeed or fail on adoption and neutral stewardship, not launch announcements. Track whether ARD moves from draft to broad implementation and whether the federated model holds.
- Do not rip and replace. ARD complements MCP and agent-to-agent protocols. Nothing about it obsoletes a well-built agent system today. Let it mature before committing engineering time to implementation.
Common Mistakes to Avoid
The first mistake is treating every new standard announcement as an emergency. ARD is a draft backed by big names, which is meaningful but not a mandate to rebuild. The second mistake is the opposite: dismissing it entirely because it does not affect this month's roadmap. Standards set the terrain your future systems run on, and the companies that ignored MCP early spent 2025 catching up. The third mistake is confusing discovery with connection. ARD does not replace how your agents talk to tools; it changes how they find them. Teams that conflate the two layers will make architecture decisions on a misunderstanding.
Key Takeaways
- Agentic Resource Discovery (ARD) is a new open standard, announced in July 2026, for how AI agents find the tools and data they need across enterprise software.
- It is backed by a rare coalition of rivals, including Google, Microsoft, Salesforce, Snowflake, ServiceNow, GitHub, Hugging Face, and NVIDIA, and is Apache 2.0 licensed with a federated, no-single-owner design.
- ARD adds a discovery layer above protocols like MCP and agent-to-agent standards; it catalogs them rather than replacing them.
- The strategic signal is that competition in enterprise AI is shifting from how agents connect to how their capabilities get discovered and ranked.
- Most businesses should prepare by favoring open protocols and documenting internal capabilities cleanly, not by rushing to implement a draft specification.
The businesses that move early on agent discovery standards will have a meaningful advantage over those that wait until fragmentation forces the issue. If you want to be one of them, let's start with a conversation.