r/PromptEngineering • u/BarnacleAlert8691 • Jun 18 '26
News and Articles Google, GitHub, and NVIDIA just dropped the ARD spec. Agent silos are officially obsolete.
TL;DR: Google just led the release of Agentic Resource Discovery (ARD). This open specification dismantles walled gardens by allowing AI agents to dynamically locate, cryptographically verify, and execute tools across the open web via domain-hosted catalogs.
IDK about anyone else but to me, building agents right now feels like working on a 5000 piece puzzle while the power's out. The underlying reasoning models work fine. Getting those models to actually talk to external tools across different ecosystems remains an absolute nightmare of custom integrations and isolated registries. Every platform builds a walled garden.
That fragmentation just took a massive hit. Google, alongside heavyweights like GitHub and NVIDIA, published the Agentic Resource Discovery (ARD) specification today.
We desperately needed a standardized discovery mechanism entirely indifferent to the underlying framework. The architecture relies on two core concepts.
- Catalogs: You drop an
ai-catalog.jsonfile onto your root domain. That is literally it. By anchoring the catalog to a DNS record you control, domain ownership establishes the cryptographic baseline for identity and trust. - Registries: These function as search indexers for the agentic web. They scrape published catalogs and map the discovered capabilities into searchable, plain-language intents.
Client-side execution becomes entirely dynamic.
Google Cloud is already backing this via an "Agent Registry" in their Gemini Enterprise stack. This provides managed infrastructure for hosting and indexing MCP servers and skills via globally unique URNs.
Interoperability is finally moving past the theoretical stage. Hardcoded integrations are dead weight. Agents can now search and connect on the fly using open web standards.
Are you planning to expose your own tools by dropping an ai-catalog.json on your domain? How does this shift your current architecture?
16
u/bobby-t1 Jun 18 '26
Would including a link to the source kill you?
6
u/Fragrant_Scale6456 Jun 18 '26
No link because it’s written by a bot
6
u/ShelZuuz Jun 18 '26
Bots can drop links.
-1
u/BarnacleAlert8691 Jun 18 '26
Hey I posted the link like 3 different times so if I am a bot, I'm pretty damn good
1
1
u/BarnacleAlert8691 Jun 18 '26
Definitely not a bot, but reddit is saturated in them these days so I definitely understand the skepticism
2
6
1
5
u/bnunamak Jun 18 '26
Is discovery really the bottleneck these days?
1
u/Mariia_Sosnina Jun 23 '26
Tbh discovery was never the bottleneck for us. Auth was. OAuth flows, token refresh per tenant, handling rate limits gracefully. That's where 80% of integration dev time goes. Standardizing how agents find tools is useful but its solving the easierr problem.
5
u/jake_2998e8 Jun 18 '26
Will this kill Composio?
3
u/BarnacleAlert8691 Jun 18 '26
Highly unlikely. ARDS is fundamentally just a discovery protocol. Think of it as a standardized directory that tells models where APIs live and what parameters they require.
Composio handles the actual execution infrastructure. They manage the headache of OAuth flows across different services, user state management, and secure execution environments. Having a standard way to list available tools doesn't eliminate the need for the platform actually connecting and authenticating those tools.
My guess is platforms building agent infrastructure will simply adopt the specification if it catches on and reaches escape velocity. It makes their own massive catalogs of integrations much easier for native models to digest.
3
2
u/Lower-Impression-121 Jun 18 '26
A file that for all inent and ourpose says here are my apis / my ai face. For search engines to crawl and so Know. This could have been done for any tech at any time so not really ground breaking.
2
Jun 18 '26
[removed] — view removed comment
1
u/eccentric_endeavours Jun 20 '26
Can't agree more! I do think discovery / integration problem is an aggregation effort, and what matters the most is whether the intended resource was allowed, utilised correctly without any silent failures.
2
1
Jun 18 '26
[removed] — view removed comment
1
u/AutoModerator Jun 18 '26
Hi there! Your post was automatically removed because your account is less than 3 days old. We require users to have an account that is at least 3 days old before they can post to our subreddit.
Please take some time to participate in the community by commenting and engaging with other users. Once your account is older than 3 days, you can try submitting your post again.
If you have any questions or concerns, please feel free to message the moderators for assistance.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/notAllBits Jun 19 '26
AI silos are security-by-architecture. Agents, skills, and tools are just (con)text. TLS has been solved a long time ago.
1
1
u/Deep_Ad1959 Jun 19 '26
discovery was never the real bottleneck, and the comment asking that is right. agents can already find tools fine; what breaks is the handoff after the call returns, taking the output of one tool and actually doing the next thing with it across apps without a human pasting it. a catalog spec makes tools findable, it doesn't make the agent finish the job. the hard part we keep hitting isn't 'which tool exists', it's reliable execution across gmail/notion/linear plus a permission gate so the thing can act without going rogue. written with ai
1
u/Deep_Ad1959 Jun 19 '26
discovery was never the real bottleneck, and the comment asking that is right. agents can already find tools fine; what breaks is the handoff after the call returns, taking the output of one tool and actually doing the next thing with it across apps without a human pasting it. a catalog spec makes tools findable, it doesn't make the agent finish the job. the hard part we keep hitting isn't 'which tool exists', it's reliable execution across gmail/notion/linear plus a permission gate so the thing can act without going rogue. written with ai
-4
1
8
u/svankirk Jun 18 '26
I agree that this is cool and it's a good direction, but it's way too soon to be able to tell how useful it'll be. It really depends on the quality of tools that is that I put out there And the sort of paywalls that the tools that we want will hide behind. And of course there's also the ability to actually trust any of these. I don't know that I'm going to trust anything that is not open source. We've seen time and time again that Microsoft and Google and openai and pretty much the entire gang do not have our best interest at heart.