It appears .agent and .agi are about to be the hot new domains
What’s in a URL anymore, really. For the first time in years, the Internet Corporation for Assigned Names and Numbers - better known as ICANN - is accepting applications for new top-level domains.
Editorial analysis
The advancement in it appears .agent and .agi are about to be the hot new domains demonstrates the accelerating maturity of agent-tool integration protocols. What’s in a URL anymore, really. For the first time in years, the Internet Corporation for Assigned Names and Numbers - better known as ICANN - is accepting applications for new top-level domains. The Model Context Protocol (MCP) is emerging as the de facto standard for connecting language models to external tools and data sources, analogous to how LSP standardized editor-language server communication. For engineering teams, this means tool integrations can now be written once and reused across multiple agent frameworks and hosts. The security model—capability-based permissions with explicit user approval—addresses the primary enterprise concern around agent autonomy. Teams should evaluate their existing tool surfaces for MCP compatibility and plan migration from framework-specific tool registries. The ecosystem momentum suggests MCP will become a baseline requirement for enterprise AI deployments within the next twelve months.