Back to Devoured - June 22, 2026
DEVOURED
Solving an ARD problem in AI: Agentic Resource Discovery

Solving an ARD problem in AI: Agentic Resource Discovery

AI InfoWorld
Major tech players are proposing a new standard, Agentic Resource Discovery (ARD), to standardize how AI agents find and interact with corporate tools.
What: Google, Microsoft, Cisco, Nvidia, and Salesforce have proposed the ARD protocol to allow agents to automatically crawl catalogs and registries to discover authorized internal tools and services.
Why it matters: This signals that the industry is shifting from 'agents finding web search results' to 'agents acting as enterprise operators,' requiring a unified discovery layer for internal systems.
Takeaway: If your team manages internal tool registries, investigate the ARD specification to prepare your services for automated discovery by enterprise AI agents.
Deep dive
  • ARD operates on a two-level architecture: Catalogs (defined capabilities) and Registries (searchable indices).
  • The protocol aims to break down information silos by allowing agents to discover documentation, ticket history, and observability systems autonomously.
  • It addresses governance concerns regarding which tools an agent is authorized to use within a corporate environment.
  • It creates a standardized interface for agents to query disparate data sources across an organization.
Decoder
  • Agentic Resource Discovery (ARD): A proposed protocol to create a standardized, searchable directory of internal APIs, documentation, and tools for AI agents to interact with in an enterprise.
Original article

Microsoft, Google, Cisco and others propose a new way to help AI agents discover the tools they need to perform the tasks they are assigned.

Enterprises implementing agentic AI face a challenge: Which tools should they allow their agents to use, where can they be found, and how can they be used safely? A new protocol, Agentic Resource Discovery, or ARD, aims to let agents answer those questions for themselves. Behind it are Google, Microsoft, Cisco, Nvidia, Salesforce and others.

ARD aims to standardize the way that tools and services are shared across systems within a corporate domain. For example, when investigating a production problem, an agent may want to query engineering documentation and open support tickets, deployment history and observability systems, all of which could be managed by different registries and across different silos. There is no common layer that pulls them together. ARD has been designed to be that layer.

It operates across two levels. Catalogs and Registries. In the first, an organization publishes a catalog setting out its available capabilities. The Registries layer act as a form of search engine, crawling those published catalogs.

The ARD specification is available now. Organizations are invited to publish their own catalogs using the quickstart guide. After this, they are able to join the community and participate in the evolution of ARD.

Explore all 69 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi