AWS released Agent Registry through Amazon Bedrock AgentCore on April 13, 2026, now available in preview across five regions. The registry provides enterprises with a private, governed catalog for discovering and managing AI agents, tools, skills, MCP servers, and custom resources across their organizations.
What Agent Registry Does
The registry stores structured metadata for every agent, tool, MCP server, and skill in an organization’s inventory. Each record captures who published it, what protocols it implements, what capabilities it exposes, and how to invoke it. Records can be added manually through the AgentCore console, AWS CLI, or SDK, or automatically by pointing to a live MCP or A2A endpoint that the registry will index.
Discovery works through hybrid search combining keyword and semantic matching. A search for “payment processing” surfaces tools tagged as “billing” or “invoicing,” according to AWS’s Machine Learning blog. The registry is also accessible as an MCP server, meaning MCP-compatible clients like Kiro and Claude Code can query it directly from IDEs.
Governance and Approval Workflows
Every record follows a lifecycle: draft, pending approval, discoverable. Administrators use IAM policies to control who can register and who can consume. Records are versioned, can be deprecated, and carry custom metadata fields for team ownership, compliance status, or cost center, per the AWS What’s New announcement. AWS CloudTrail provides audit trails for all registry access and administrative actions. For organizations with custom identity providers, OAuth-based access allows teams to build their own discovery interfaces without requiring IAM credentials.
Early Adopters
Southwest Airlines is using Agent Registry for enterprise-wide agent cataloging and governance. “AWS Agent Registry in AgentCore solves the critical discoverability challenge, enabling teams to find and reuse existing agents instead of rebuilding capabilities from scratch,” said Justin Bundick, VP of AI and Intelligent Platforms at Southwest Airlines, in a statement to AWS.
Zuora, which deploys 50 agents across Sales, Finance, Product, and Developer teams, is using the registry for centralized visibility. Pete Hirsch, Zuora’s Chief Product and Technology Officer, said the registry “gives Principal Architects a unified view to discover, manage, and catalog every agent, tool, and skill in use,” according to the same AWS blog post.
The Agent Sprawl Problem
The timing is deliberate. OutSystems found that 94% of enterprises cite agent sprawl as a concern in its State of AI Development 2026 report. As organizations scale from pilot projects to hundreds of agents built across different teams, cloud platforms, and on-premises environments, keeping track of what exists becomes its own operational challenge. Duplicate work multiplies. Governance gaps widen.
AWS is positioning the registry as framework-agnostic and cloud-agnostic. It indexes agents regardless of where they’re built or hosted, supporting MCP and A2A protocols natively. That’s a clear bet that enterprise agent landscapes will be heterogeneous, not locked into a single provider.
Availability and Roadmap
Agent Registry is available in preview in US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Ireland). AWS says it plans to expand the registry across every AWS service where agents are built, including Amazon Quick and Kiro, with automatic indexing at deployment time. Cross-registry federation, allowing organizations to connect multiple registries and search across them as one, is on the roadmap.