Now available through Amazon Bedrock AgentCore. You can use AWS Agent Registry to discover, share, and reuse agents, tools, and agent skills across your organization.
As companies scale up to hundreds or thousands of agents, platform teams face three key challenges. These are visibility (knowing which agents exist across your organization), control (managing who can publish and what is discoverable across your organization), and reuse (preventing teams from rebuilding existing functionality). Without a centralized system, agent sprawl accelerates, compliance risks increase, and development efforts are wasted on duplicative work. These challenges are further complicated by reality. An organization’s agent environment never resides entirely within a single provider. Agents are built across AWS services, other cloud platforms, and on-premises environments. A registry that covers only part of the stack leaves the rest hidden, and hidden agents cannot be discovered, managed, or reused. To solve this, you need more than just a place to list what exists. Platform teams must build agents, publish them with approval workflows, help teams discover and reuse what’s out there, manage who can publish and use it, monitor what’s running in production, and retire what’s no longer needed. Today, we are announcing AWS Agent Registry (preview) for AgentCore. It’s a single place to discover, share, and reuse AI agents, tools, and agent skills across your enterprise.
AgentCore is a platform for building, connecting, and optimizing agents at scale, designed from the ground up for agents and open to any model, any framework, and any enterprise architecture. Whether you’re shipping your first agent or your 1,000th agent, we have one platform that scales with you. Registries extend that same flexibility to how you organize and manage what you build. Index your agents wherever they are built or hosted: AWS, other cloud providers, or on-premises.
What is currently available in preview
The registry stores metadata for all agents, tools, MCP servers, agent skills, and custom resources as structured records. Capture each record’s publisher, the protocol it implements, what it exposes, and how it is invoked. The registry natively supports established standards such as MCP and A2A, and provides the flexibility to define custom schemas for your organization. There are two ways to register records. You can manually provide metadata through the console, AWS SDKs, or APIs to specify feature description, ownership, compliance status, and usage documentation. Alternatively, you can specify an MCP or A2A endpoint and the registry will automatically populate the details. The registry can reflect the state of your entire agent from day one, not just the parts that happen to run on AWS.
The registry can be accessed through the AgentCore console, API, and as an MCP server. Any MCP-compatible client, including Kiro and Claude Code, can run queries directly. For organizations using custom identity providers, OAuth-based access means teams can build their own discovery UIs without requiring IAM credentials.
find something that already exists
Without a central registry, developers are forced to search externally for third-party tools or for duplicate work that neighboring teams have already shipped. You won’t be able to see what’s being built, who owns it, and whether it’s approved for use. The registry solves this problem with a hybrid search that combines keywords and semantic matching. All queries use keyword matching, but longer natural language queries also use semantic understanding to uncover conceptually related results. This means that if you search for “payment processing,” you’ll see tools tagged with “billing” or “invoicing,” even if the name is different. Discovery becomes the path of least resistance. Teams can search by name, description, or resource type to find existing ones before building something new. Developers first search the registry. If a vetted feature exists, use it. If not, build it and register it to make it available to others. See what exists across your organization.
For Zuora, an AI-first monetization and revenue management platform with 50 agents across sales, finance, product, and developer teams, AgentCore’s AWS Agent Registry provides principal architects with a unified view to discover, manage, and catalog all agents, tools, and skills in use. This centralized approach allows teams to find and reuse existing assets rather than rebuilding from scratch. Standardized metadata ensures that each agent and tool includes consistent details about ownership and capabilities, giving teams end-to-end visibility and accountability across the agent ecosystem.
– Pete Hirsch, Chief Product and Technology Officer, Zuora
Control what is published
Without governance, anyone can register anything. You lose control over what becomes discoverable, you can’t enforce standards, you can’t track ownership, and you can’t manage agents from development to retirement. If you have several agents, you can manage them with a spreadsheet. If you have hundreds or thousands, you’ll need a system that automatically enforces standards.
The registry allows you to control what is published and who has access to it. Administrators use IAM policies to define who can register agents, tools, and agent skills, and who can discover them. All records follow an approval workflow. A record starts as a draft, moves to pending approval, and becomes discoverable to the broader organization once approved. The registry tracks agents throughout their lifecycle, from initial development to deployment and eventual retirement. Records are versioned to track changes over time, and organizations can deprecate records when they are no longer used. The registry provides hooks for integrating existing approval workflows. You can add custom metadata to each entry through records to capture information such as team ownership, compliance status, deployment environment, and more.
Southwest Airlines has an enterprise-wide agent catalog and enterprise-wide governance. AgentCore’s AWS Agent Registry solves important discoverability challenges and enables teams to discover and reuse existing agents instead of rebuilding functionality from scratch. Managed governance across multiple platforms ensures that all agents perform standardized ownership metadata and policy enforcement. This prevents agents from spreading across your organization and establishes the foundation for scaling to thousands of agents with enterprise-grade governance from day one.
– Justin Bundick, Vice President, AI and Intelligent Platforms, Southwest Airlines
where we are heading
We’re building for a future where the registry spans all AWS services that agents are built on, including Amazon Quick and Kiro. Agents are automatically indexed the moment they are deployed. Developers search from the IDE, business users discover agents in their workspaces, and administrators manage them from the console. They are all based on the same reliable source. Cross-registry federation allows you to connect multiple registries and search them as one. You’ll be able to define categories and taxonomies that match how your organization thinks about your agents, backed by a structured metadata schema that captures ownership, compliance status, cost centers, and everything else you need for your governance model. Over time, operational intelligence from AgentCore Observability emerges along with registry records such as call counts, latency, uptime, and usage patterns, helping you understand not just what exists, but what is actively working in your production environment.
We’re building beyond AWS Agent Registry to connect with external partner catalogs. We are excited about early partner interest in centralized discovery and governance across your technology environment.
Let’s get started
Today’s preview is the starting line. There’s no need to rebuild what already exists. No more deploying agents with no visibility. AWS Agent Registry lets you discover, manage, and reuse all your agents across your enterprise in one place.
AWS Agent Registry is currently available in preview through AgentCore in five AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Ireland).
Get started with AWS Agent Registry from the AgentCore console. See the documentation for more information.
About the author
