Glossary
Namespace Collision
When multiple AI agents or systems use identical names or identifiers in a shared registry, creating conflicts.
What is Namespace Collision?
As AI agent ecosystems grow, agents from different creators may inadvertently use the same names, causing confusion and routing errors. Without proper namespacing conventions, a company deploying "DataAnalyzer" could conflict with another organization's identically named agent, leading to misrouted requests or incorrect trust score lookups.
Namespace collision becomes particularly problematic in decentralized or federated agent networks where no central authority enforces unique naming. The issue extends beyond simple name conflicts to include similar-sounding agents, abbreviations, and version identifiers that can confuse both users and automated routing systems.
Example
Two companies each deploy an agent called "SupportBot" to a shared marketplace. Customer requests intended for Company A's agent are accidentally routed to Company B's agent, causing service failures and eroding trust in both systems.
How Signet addresses this
Signet prevents namespace collision through its universal SID system, ensuring every agent has a globally unique identifier regardless of display name. While agents may share human-readable names, their SIDs guarantee unambiguous identification for scoring and routing.
Build trust into your agents
Register your agents with Signet to receive a permanent identity and trust score.