Now accessible via Amazon Bedrock AgentCore, use AWS Agent Registry to find, share, and reuse brokers, instruments, and agent abilities throughout your group.
As enterprises scale to a whole lot or 1000’s of brokers, platform groups face three important challenges: visibility (realizing what brokers exist throughout the group), management (governing who can publish and what turns into discoverable organization-wide), and reuse (stopping groups from rebuilding capabilities that exist already). With out a centralized system, agent sprawl accelerates, compliance dangers develop, and growth effort is wasted on duplicate work. These challenges are compounded by actuality: no group’s agent panorama lives solely inside one supplier. Brokers are constructed throughout AWS companies, different cloud platforms, and on-premises environments. A registry that solely covers a part of the stack leaves the remaining invisible, and invisible brokers can’t be found, ruled, or reused. Fixing this requires greater than a spot to record what exists. Platform groups must construct brokers, publish them with approval workflows, assist groups to find and reuse what exists, govern who can publish and devour, monitor what’s operating in manufacturing, and retire what’s now not wanted. At present, we’re asserting AWS Agent Registry (preview) in AgentCore, a single place to find, share, and reuse AI brokers, instruments, and agent abilities throughout your enterprise.
AgentCore is the platform to construct, join, and optimize brokers at scale, designed from the bottom up for brokers: open to any mannequin, any framework, any enterprise structure. Whether or not you’re transport your first agent or your thousandth, you could have one platform that scales with you. The registry extends that very same flexibility to the way you manage and govern what you’ve constructed. It indexes brokers no matter the place they’re constructed or hosted – on AWS, different cloud suppliers, or on premises.
What’s accessible in preview right this moment
The registry shops metadata for each agent, instrument, MCP server, agent ability, and customized assets as a structured file. It captures who printed every file, what protocols it implements, what it exposes, and how you can invoke it. The registry helps established requirements like MCP and A2A natively, with the flexibleness to outline customized schemas on your group. There are two methods to register a file. You possibly can present metadata manually via the console, AWS SDK, or API, specifying functionality descriptions, possession, compliance standing, and utilization documentation. Or you possibly can level to an MCP or A2A endpoint, and the registry will routinely pull within the particulars. Your registry can mirror your full agent panorama from day one, not solely the items that occur to run on AWS.
The registry is accessible via the AgentCore Console, APIs, and as an MCP server. Any MCP-compatible consumer can question it straight, together with Kiro and Claude Code. For organizations with customized identification suppliers, OAuth-based entry signifies that groups can construct their very own discovery UIs with out requiring IAM credentials.
Discovering what already exists
With out a central registry, builders search externally for third-party instruments or duplicate work {that a} neighboring staff already shipped. You lose visibility into what’s been constructed, who owns it, and whether or not it’s accredited to be used. The registry solves this with hybrid search that mixes key phrase and semantic matching: all queries use key phrase matching, however longer, pure language queries additionally use semantic understanding to floor conceptually associated outcomes. This implies a seek for “cost processing” surfaces instruments tagged as “billing” or “invoicing,” even when they’re named otherwise. Discovery turns into the trail of least resistance. Groups can search by title, descriptions, and useful resource sort to search out what already exists earlier than constructing one thing new. Builders search the registry first. If a vetted functionality exists, they use it. If it doesn’t, they construct it, register it, and make it accessible to everybody else. You possibly can see what exists throughout your group.
For Zuora, an AI-first monetization and income administration platform deploying 50 brokers throughout Gross sales, Finance, Product, and Developer groups, the AWS Agent Registry in AgentCore provides Principal Architects a unified view to find, handle, and catalog each agent, instrument, and ability in use. This centralized strategy permits groups to search out and reuse present belongings reasonably than rebuilding from scratch. Standardized metadata ensures every agent and gear consists of constant particulars on possession and capabilities, giving groups end-to-end visibility and accountability throughout all the agent ecosystem.
– Pete Hirsch, Chief Product and Know-how Officer, Zuora
Governing what will get printed
With out governance, anybody can register something. You lose management over what turns into discoverable, can’t implement requirements, can’t observe possession, and may’t handle brokers from growth to retirement. When you could have a couple of brokers, you possibly can handle them in a spreadsheet. When you could have a whole lot or 1000’s, you want a system that enforces requirements routinely.
The registry provides you management over what will get printed and who can entry it. Admins use IAM insurance policies to outline who can register brokers, instruments, and agent abilities and who can uncover them. Each file follows an approval workflow: they begin as drafts, transfer to pending approval, and turn into discoverable to the broader group as soon as accredited. The registry tracks brokers throughout their whole lifecycle, from preliminary growth via deployment to eventual retirement. Data are versioned to trace adjustments over time, and organizations can deprecate data which might be now not in use. The registry offers hooks to combine your present approval workflows. You possibly can add customized metadata to every entry via a file, capturing data like staff possession, compliance standing, or deployment surroundings.
Southwest Airways is enabling an enterprise-wide agent catalog and governance throughout the enterprise. AWS Agent Registry in AgentCore solves the important discoverability problem— enabling groups to search out and reuse present brokers as a substitute of rebuilding capabilities from scratch. With managed governance throughout a number of platforms, each agent carries standardized possession metadata and coverage enforcement. This may forestall agent sprawl throughout the group whereas establishing the muse for scaling 1000’s of brokers with enterprise-grade governance from day one.
– Justin Bundick, VP AI and Clever Platforms, Southwest Airways
The place we’re headed
We’re constructing towards a future the place the registry spans each AWS service the place brokers are constructed, together with Amazon Fast, and Kiro. Brokers will likely be routinely listed the second that they’re deployed. Builders will search from the IDE, enterprise customers will uncover brokers of their workspace, and admins will govern from the console, all backed by the identical supply of reality. Cross-registry federation will allow you to join a number of registries and search throughout them as one. It is possible for you to to outline classes and taxonomies that match how your group thinks about brokers, backed by structured metadata schemas capturing possession, compliance standing, price middle, and no matter else your governance mannequin requires. Over time, operational intelligence from AgentCore Observability will floor alongside registry data: invocation counts, latency, uptime, and utilization patterns, serving to you to know not solely what exists, however what’s actively working in manufacturing.
Past AWS Agent Registry, we’re constructing towards connecting with exterior associate catalogs. We’re enthusiastic about early associate curiosity in centralized discovery and governance throughout your know-how panorama.
Get began
At present’s preview is the beginning line. No extra rebuilding what already exists. No extra brokers deployed with out visibility. The AWS Agent Registry provides you one place to find, govern, and reuse each agent throughout your enterprise.
AWS Agent Registry is out there in preview right this moment via AgentCore in 5 AWS Areas: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Eire).
Get began with AWS Agent Registry via the AgentCore Console. Be taught extra by studying the documentation.
In regards to the authors
