As AI agents multiply, two questions keep coming up: how does one agent find another that can do a job, and how does a company keep track of every agent it runs? Registries and directories answer both. Public registries let agents and developers discover agents across the internet, using standards such as A2A agent cards and on-chain identities. Enterprise registries give IT and security teams an inventory of every agent, what it can reach and who owns it.
This list ranks ten AI agent registries and directories worth knowing in 2027, covering both the public agentic web and enterprise agent catalogs. Details come from vendor announcements, documentation and published research through early November 2026. For registries of tools rather than agents, see our list of MCP directories and registries.
| Registry | Type | Best For | Known For |
| Google Agent Registry | Enterprise, cloud | Google Cloud agent programs | A2A cards, MCP servers and Agent Gateway policy |
| Microsoft Agent 365 | Enterprise, cloud | Microsoft 365 organizations | Agent inventory tied to Microsoft identity and governance |
| AWS Agent Registry | Enterprise, cloud | Agents built on AWS | An organization catalog inside Amazon Bedrock AgentCore |
| ServiceNow AI Control Tower | Enterprise governance | Cross-platform AI inventories | Agents, models and MCP servers from many clouds |
| Microsoft Entra Agent ID | Identity directory | Identity-first agent governance | Agents treated as directory identities |
| A2A Registry | Public, open source | Finding live A2A agents | Registration from a published agent card |
| AGNTCY Agent Directory Service | Open infrastructure | Decentralized discovery | Content-addressed records with integrity checks |
| NANDA Index | Research and open standard | Verifiable agent metadata | AgentFacts with credentialed claims |
| Agent Arena | On-chain registry | ERC-8004 agents | Search across 22,000 plus on-chain agents |
| Coinbase Agent.market | Agent marketplace | Paid agent services | Services agents can buy with x402 |
Google’s Agent Registry, part of the Gemini Enterprise Agent Platform, became generally available in June 2026. It catalogs agents using A2A agent cards alongside MCP servers, tools, endpoints and skills, auto-registers supported workloads in a project and lets teams add external endpoints by hand.
Policy is enforced through Agent Gateway, so the registry is not just a list but a control point for which agents and tools can talk to each other. It is the natural choice for organizations building agents on Google Cloud, especially those adopting A2A.
Microsoft’s Agent 365 registry became generally available on May 1, 2026, giving Microsoft 365 organizations one place to see agents built in Copilot Studio, Azure AI Foundry and partner platforms. Entries connect to Microsoft’s identity, security and compliance tools, so agents can be governed with the same controls as users and apps.
Other platforms can publish into it, including ServiceNow’s AI Control Tower, which helps it act as a central inventory beyond Microsoft’s own tools.
AWS added an Agent Registry to Amazon Bedrock AgentCore at the end of August 2026. It is an organization-internal catalog where teams register agents, describe their capabilities and control who can discover and use them.
It fits companies running agents on AgentCore and other AWS services that want discovery and reuse inside the organization rather than a public listing.
ServiceNow’s AI Control Tower inventories AI assets on and off the ServiceNow platform: models, agents, prompts, datasets and, since June 2026, MCP servers. Connectors cover AWS, Google Cloud, Azure, SAP, Oracle and Workday, with risk classification at intake and lifecycle management through to offboarding.
It suits large enterprises that run agents on several platforms and want one governed register that risk and compliance teams already know how to use.
Microsoft Entra Agent ID approaches the registry problem from identity. Each agent gets an identity in Entra, so it can be discovered, governed with Conditional Access and lifecycle policies, and audited like a user or app.
Researchers comparing registry designs list it as the leading example of an enterprise directory with policy and zero-trust integration. It pairs naturally with Agent 365 for Microsoft-centric organizations; our list of AI agent identity and access management platforms covers alternatives.
The A2A Registry is a community-driven, open-source directory of live, hosted agents that implement the Agent2Agent protocol. If an agent publishes a valid agent card at its well-known address, it can be registered with a single API call, and the registry offers a web interface, a search API and filters by skill.
It is the simplest way to make a public A2A agent discoverable by other agents and developers. Because it trusts what agent cards declare, verify important agents directly before relying on them.
The AGNTCY project’s Agent Directory Service takes a decentralized approach. Agent records are content-addressed and stored as OCI artifacts, routed through a distributed hash table and signed with Sigstore so recipients can verify they have not been altered. It adds a taxonomy for discovering agents by skill.
It suits organizations that want discovery across company boundaries without depending on one central operator.
The NANDA Index, from MIT’s Project NANDA, is a research-led architecture for agent discovery built around AgentFacts, a metadata format with cryptographically verifiable, credentialed claims about what an agent can do. It is designed for privacy-preserving discovery and routing across domains.
It is more of an emerging standard than a busy marketplace today, but it shapes how verifiable agent identity is likely to work, and it is worth following for teams planning cross-organization agent networks.
Agent Arena is an on-chain registry that indexes more than 22,000 agents registered under ERC-8004, the Ethereum standard for agent identity, across 17 blockchains including Solana. It supports A2A, MCP and x402, exposes its own agent card and lets agents register by paying a small fee in USDC over x402.
It is the most practical way to explore the Web3 side of the agent economy, where identity, reputation and payment all live on-chain.
Coinbase launched Agent.market in April 2026 as a directory of x402-enabled services: APIs, data and tools that agents can find and pay for in stablecoins without accounts or contracts. At launch Coinbase reported tens of thousands of active agents using x402.
It is less a registry of agents than a storefront for them, but for developers building agents that need to buy services on their own, it is a key discovery point. Our guide on what x402 is explains the payment side.
Enterprise registries such as Google, Microsoft, AWS and ServiceNow answer the question of which agents you run and who owns them. Public registries such as the A2A Registry, AGNTCY and Agent Arena answer which agents exist that you could use. Most companies need the first before the second.
A2A agent cards are becoming the common description format for agents, MCP for tools and ERC-8004 for on-chain identity. Choose registries that understand the protocols your agents use; our comparison of A2A vs MCP explains the difference.
A listing is only as trustworthy as its verification. Look for signed agent cards, domain or DNS verification, credentialed claims or on-chain identity, and treat unverified entries with caution.
A registry that connects to a gateway or identity system can stop unapproved agents from being used, not just list them. That matters as soon as agents start calling other agents on their own.
Google Agent Registry and Microsoft Agent 365 lead this list because they turn agent inventories into enforceable policy for the clouds most enterprises already use, with AWS and ServiceNow close behind for AWS-centric and multi-cloud estates. Entra Agent ID brings identity to the problem, while the A2A Registry, AGNTCY, NANDA, Agent Arena and Coinbase’s Agent.market map the open agentic web, from community directories to on-chain identity and paid services. Start by registering every agent you run, then decide which public networks you want your agents to discover and join.