Back to Insights

17 Jun 2026 | Junjie Bu and Srinivas Krishnan (Google)

Google's Agentic Resource Discovery Specification: The Missing Layer for Agent-Native Commerce

Google has published an open specification — ARD — for how AI agents discover, verify and safely connect to tools across organisational boundaries. For hospitality, it is the standard that finally lets a booking agent find your property's live inventory without going through an OTA aggregator.

Google's Agentic Resource Discovery specification — the protocol layer that lets AI agents find, verify and connect to a hotel's own capabilities without going through an aggregator.

Why this matters for hotels

Every conversation about agent-native distribution eventually hits the same wall: how does the agent find the hotel's live capabilities in the first place, and how does it decide whether to trust them? Google's Agentic Resource Discovery (ARD) specification is a direct answer. If it lands as an industry standard, it becomes the layer that lets an AI travel agent discover a hotel's booking, availability and ancillary APIs directly — bypassing an aggregator-only discovery model.

The three questions ARD standardises

  1. Where does a capability live? — an agent needs to locate the right endpoint without hard-coded knowledge
  2. Which of several options should it use? — competing tools need a comparable discovery format
  3. Is it safe to connect? — cryptographic trust metadata lets the agent verify before it acts

Today there is no cross-organisation answer to any of these. ARD proposes one.

The architecture

Two components, both intentionally decentralised:

  • Catalogs — hosted on an organisation's own domain, functioning as the trust anchor for its capabilities
  • Registries — search-engine-like indexes over those catalogs, letting agents find capabilities across organisations

An agent can discover through a registry or fetch a catalog directly from a known domain. Verifiable trust metadata rides along so the agent can confirm authenticity before executing anything.

Enterprise and open

Google Cloud's Agent Registry provides a hosted ARD implementation inside Gemini Enterprise Agent Platform — governance, namespaced identifiers, HIPAA-class compliance. But the specification itself is Apache 2.0, developed with industry partners, with quickstarts and community pathways. That combination — open standard plus first-party managed implementation — is the same pattern that made Kubernetes and OpenTelemetry hard to route around.

What hoteliers should take from this

  • The "how does an agent find you" problem is being answered at the protocol layer
  • Hosting a catalog on your own domain becomes a real technical asset — brand-owned discovery
  • PMS, CRS and channel-manager vendors will be judged on whether they can publish ARD-compliant catalogs
  • The window to be discoverable by agents outside an OTA's index just opened

Read the announcement on the Google Developers Blog →

Stay Updated

Enjoyed this insight?

Get more AI hospitality research and trends.

For Contributors

Submit article for consideration

Share an article, perspective, or industry analysis for possible inclusion in the Alliance Insights section.