AWS: Agents shouldn’t be secret, so we built a registry • The Register

AI brokers shouldn’t be secret brokers, at the least in company environments. However when firms deploy software program automations, they do not all the time have visibility into what their roboscripts are literally doing.

Amazon Internet Providers goals to light up the enterprise agent ecosystem with its Agent Registry, which the infrastructure biz describes as “a single place to find, share, and reuse AI brokers, instruments, and agent expertise throughout your enterprise.”

AWS’ Agent Registry shouldn’t be the one agent registry. Microsoft has its Entra Agent Registry and an Azure Agent Registry. Google Cloud has its Agent Registry. There’s an Agent Client Protocol (ACP) Registry. And there are a lot of extra third-party registries. The Register notices such issues.

AWS intends its registry to assist make brokers extra seen inside organizations, to supply some measure of management over agent publication and discovery, and to make sure ample distribution in order that disparate groups aren’t reinventing the wheel with redundant brokers.

Agent Registry is constructed to work with Bedrock AgentCore, AWS’s platform for constructing, deploying, and managing agent software program. It supplies a central repository for storing metadata describing brokers, instruments, MCP servers, agent expertise, and related sources, linked to authorship information, protocol particulars, providers uncovered, and invocation directions. It helps requirements like MCP and A2A, along with customized schemas, and it is designed to work wherever brokers are hosted, whether or not that is Agent Core, different cloud providers, or on-premises.

Including information to the registry will be carried out by way of guide metadata submission through the AWS console, AWS SDK, or API. The registry may also fetch information mechanically after being linked to a correctly configured MCP or A2A endpoint. 

Querying the registry will be carried out through AgentCore Console, APIs, or any MCP-compatible shopper like Kiro or Claude Code.

In Amazon-packaged remarks, Pete Hirsch, chief product and know-how officer at Zuora, a income administration biz, talked up the benefits of having a supply of reality for brokers.

“This centralized strategy allows groups to search out and reuse present property moderately than rebuilding from scratch,” Hirsch stated through AWS comms. “Standardized metadata ensures every agent and power contains constant particulars on possession and capabilities, giving groups end-to-end visibility and accountability throughout all the agent ecosystem.”

AWS expects that brokers constructed utilizing AgentCore, Amazon Fast Suite, and Kiro will probably be mechanically listed within the registry and that metadata from the operation of these brokers will probably be surfaced to point out what exists and the way effectively they operate. Organizations can look ahead to viewing information about their brokers within the AWS Useful resource Entry Supervisor. 

The AWS Agent Registry is being supplied in preview through AgentCore in 5 areas: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Eire). ®