Discovery & Registry¶
Once an agent has a profile, the registry makes it findable by capability, semantic description, or metadata. Locally or across a distributed network.
Why This Is Powerful
Find by what agents do, not by name: capability-name lookup and semantic search find collaborators from a plain text description, no identifiers required.
Same API, two scales: CommunicationHub.register_agent() runs identically whether the registry is in-process or a remote HTTP server.
Identity-backed: every agent’s DID is verified before it becomes discoverable.
See Setting Up an Agent Network for how discovery fits multi-agent architectures.
I want to…¶
Register agents and search by name or natural language → Local Discovery
Deploy a shared registry for a distributed network → Remote Discovery
Connect my agent code to a remote registry → Remote Discovery
All pages¶
In-process AgentRegistry via CommunicationHub. Covers registration, exact and semantic capability search with filters, and vector store configuration.
HTTP registry server via agentconnect serve registry and RegistryAPIClient. Includes CLI, deployment, and production configuration.
How the pieces fit
Describe: define an agent’s profile, capabilities, and skills → Agent Profile & Capabilities
Discover: register agents and search by capability or semantics → this section
Talk: route signed messages via the hub → Communication
Note
On the horizon: the registry is evolving into the network’s trust authority with stricter DID ownership verification, routing metadata storage per agent, and a managed hosted option.