AI news ·
AWS Agent Registry adds verified domain naming and public discovery for agents
AWS Agent Registry now supports verified domain names for agents, removing the manual networking work that previously complicated multi-agent setups. The capability is available now across all AWS Regions at no additional charge.

AWS Agent Registry now lets developers register verified public domain names for their agents and publish them for discovery by any AWS-authenticated user. The move cuts out the manual networking work that previously made multi-agent systems harder to build, while giving teams a way to confirm an agent's origin before connecting to it.
Domain verification sits at the center of the update. Developers or network admins complete a verification check to prove they own a domain, then associate that domain with their agents. Once published, the agent records become searchable through both semantic and lexical search - meaning other AWS users can find them by meaning or by exact keyword match.
How public naming changes agent discovery
Before this launch, developers had to manually configure how agents discovered and connected to one another. That added friction to any project involving multiple agents. Now the public records are anchored to a verified domain identity, so the source of an agent is traceable. A team evaluating an agent from outside their organization can check the domain before integrating it into their workflow.
The search capability works across AWS accounts. Any AWS-authenticated user can search for published agents, not just those within the same registry or account boundary. This opens the door to broader agent ecosystems without requiring custom discovery infrastructure.
What this means for product and operations teams
For product development groups building agent-based features, domain-verified naming removes a step from the integration checklist. Instead of building bespoke trust mechanisms, they can rely on the domain verification AWS performs. Operations and IT teams get a clear audit trail - agent records tied to verified domains are easier to track and govern than anonymous or self-asserted identifiers.
Customer support workflows that use multiple agents across accounts also stand to benefit. Searchable, publicly named agents reduce the coordination overhead when support systems need to route tasks to specialized agents maintained by different teams or partners.
Availability and cost
The naming and public discovery capability is available now in all AWS Regions where AWS Agent Registry operates. There is no additional charge at this time. AWS has published documentation covering the domain verification process and how to publish agents for public visibility.
Why this matters for customer support, IT, development, and operations teams
For customer support leaders, verified agent names mean less guesswork when connecting a support bot to a billing agent or a returns-processing agent maintained by another team. IT and development groups can publish agents once and let others discover them, rather than maintaining separate connection configurations for each consumer. Operations teams gain a lightweight governance mechanism - domain verification creates accountability without adding a heavy identity layer. The capability removes manual wiring from multi-agent setups, which directly reduces the time spent on integration and troubleshooting across agent networks. For professionals exploring how agent-based automation fits into broader workflows, resources like AI Agent Courses can help map these patterns to real-world use cases.