A timely bet on the AI agent-tool protocol wave: genuinely useful to MCP server builders if the protocol endures, narrow if it fades.
developers and companies publishing Model Context Protocol servers and agent-tool integrations, plus AI infrastructure vendors wanting a protocol-native address for their connector products
One of 46 ICANN 2026-round applications Radix announced on its own applications page. Radix states it intends to build and operate each TLD it wins.
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet that a just-born category of software component needs its own address space, sold to the vendors and developers shipping those components rather than to any consumer audience, and it only works if the category outlives its hype window.
Same bet that a technical standard's acronym can become the namespace of the implementer community that lives around that standard, where the registrant base is vendors proving conformance rather than anyone with a brand to place.
Shares the shape of a named technology serving as the identity layer for the third parties who build on it, but the 2012 version was a mature corporate platform name rather than a two-year-old open protocol acronym, so the risk profile is inverted.
- Radix · first recordedRadix
“Radix has applied for these TLDs; we do not own or operate them today.”Radix