AWS Backs Open Agentic Resource Discovery Specification for Agent Registry Federation

Amazon Web Services announced support for the Agentic Resource Discovery (ARD) open specification, detailing how the federation standard will integrate with AWS Agent Registry, its managed catalog for AI agents, tools, and skills currently in preview within Amazon Bedrock AgentCore. The alignment targets cross-platform discovery across heterogeneous enterprise stacks. While AWS Agent Registry provides centralized indexing and access controls within an AWS environment, real-world deployments fre

2 min
AWS Backs Open Agentic Resource Discovery Specification for Agent Registry Federation

Amazon Web Services announced support for the Agentic Resource Discovery (ARD) open specification, detailing how the federation standard will integrate with AWS Agent Registry, its managed catalog for AI agents, tools, and skills currently in preview within Amazon Bedrock AgentCore.

The alignment targets cross-platform discovery across heterogeneous enterprise stacks. While AWS Agent Registry provides centralized indexing and access controls within an AWS environment, real-world deployments frequently span multi-cloud architectures, on-premises infrastructure, and third-party SaaS platforms. ARD establishes a standard metadata format and discovery protocol, enabling organizations to publish resources once and make them discoverable across disparate runtime environments without custom point-to-point connectors.

Agentic Resource Discovery Architecture

Architecture of the ARD Standard

The ARD specification is an Apache 2.0-licensed open standard created by an industry working group that includes Google, Microsoft, Hugging Face, GoDaddy, Cisco, Databricks, GitHub, NVIDIA, Salesforce, ServiceNow, and Snowflake.

The architecture is structured around two primary primitives:

  1. Catalogs: Machine-readable JSON files (ai-catalog.json) hosted at well-known domain paths. These files declare available agents, Model Context Protocol (MCP) servers, Agent-to-Agent (A2A) endpoints, and OpenAPI tool definitions. Domain ownership establishes the cryptographic root of trust for publisher identity.
  2. Registries: Search and indexing engines that crawl distributed catalogs to resolve plain-language discovery queries, returning matching endpoints alongside verifiable trust and identity metadata.

ARD standardizes discovery rather than execution. Once an agent or tool is discovered, client runtimes interact with it using native communication layers such as MCP or standard REST APIs.

Integration with AWS Agent Registry

Within AWS Bedrock AgentCore, Agent Registry operates as a managed catalog with built-in governance workflows. The lifecycle routes through administrators, publishers, and curators, enforcing approval gates before assets become discoverable. Authorization is managed via AWS Identity and Access Management (IAM) policies or JSON Web Tokens (JWT) from enterprise identity providers, with the registry exposed as a remote MCP endpoint.

Under the planned federation model, ARD acts as an external interoperability layer. Organizations can expose local catalog metadata in the ARD format for federated cross-cloud discovery while retaining internal IAM policies, approval pipelines, and access revocation controls at the registry boundary.

Google has similarly outlined native ARD support for its Gemini Enterprise Agent Platform, establishing an emerging consensus among major cloud providers around open discovery standards paired with managed, governed internal registries.

Sources

Written by

More to read

  • The Score Function Estimator: Mathematical Foundations of REINFORCE, Log-Derivative Tricks, and Baseline Variance Reduction

    In modern artificial intelligence, standard backpropagation relies on continuous differentiability: every operation between model parameters and the final loss must provide well-behaved analytical Jacobian matrices. However, many of the most critical optimization challenges in machine learning break this continuity. Autoregressive token generation in large language models, discrete tool invocation, programmatic compiler execution, and black-box reward environments are fundamentally non-different

    1 min
  • Lancium and NVIDIA Partner on Gigawatt-Scale AI Factories Across 15GW Pipeline

    Texas energy infrastructure provider Lancium has entered a strategic partnership with NVIDIA to deploy NVIDIA's full AI factory technology stack across Lancium's multi-gigawatt clean energy data center portfolio. As part of the transaction, NVIDIA has taken a direct equity stake in Lancium, which is backed by funds managed by Blackstone Energy Transition Partners and Blackstone Multi-Asset Investing. The partnership combines Lancium's 4 gigawatts of operational and leased capacity and a pipelin

    1 min
  • NVIDIA Groq 3 LPX Enters Full Production Delivering 3,400 Tokens per Second for Agentic Inference

    At Hot Chips 2026, NVIDIA announced that the Groq 3 LPX dedicated inference accelerator has entered full commercial production. Built as a workload-optimized extension to the Vera Rubin data center architecture, the accelerator addresses the decode bottlenecks inherent in multi-step agentic AI workloads by offloading token generation from primary GPU clusters onto specialized Language Processing Units (LPUs). In independent benchmarking conducted by Artificial Analysis, the Groq 3 LPX delivered

    1 min