Every great communication revolution started with a protocol nobody owned. The AI revolution is no different — and the window to lead is closing.
In 1983, ARPANET switched from NCP to TCP/IP. It was a technical migration that most people didn't notice.
It created a $15 trillion economy.
Not because TCP/IP was the best protocol. Not because it was the most feature-rich. Not because it had the biggest corporate sponsor.
TCP/IP won because of three properties:
- Nobody owned it. No patents, no licensing, no vendor advantage.
- It was simple enough to implement. Any engineer could build a TCP/IP stack in weeks.
- It solved the right problem. Not "how do we build the best network?" but "how do we connect all networks?"
Every major communication standard in history shares these three properties. SMTP for email. HTTP for the web. USB-C for devices. All open. All simple. All focused on connection rather than perfection.
The AI industry is now facing its TCP/IP moment. And the decisions made in the next 24 months will determine the architecture of AI communication for the next 30 years.
The Standardization Train Has Left the Station
This is no longer a hypothetical discussion. The institutional machinery of standardization is already in motion:
February 2026: NIST launches the "AI Agent Standards Initiative" — explicitly targeting interoperability standards for autonomous AI systems.
W3C: The AI Agent Protocol Community Group is actively developing specifications for agent communication.
IETF: Drafting frameworks for autonomous AI communication protocols.
Linux Foundation: The Agentic AI Foundation — founded by Anthropic, OpenAI, and Block — is coordinating open infrastructure standards for AI agents.
ISO/IEC: Working on AI agent interoperability standards under JTC 1/SC 42.
When NIST, W3C, IETF, the Linux Foundation, and ISO are all working on the same problem simultaneously, the question is no longer "will there be a standard?" The question is "which standard?"
The Three Possible Futures
Future 1: One Vendor Wins (Unlikely)
Google's A2A becomes the universal standard. Or Anthropic's MCP. Or IBM's ACP. One company's protocol becomes the TCP/IP of AI.
Why this won't happen: Game theory. No company will voluntarily adopt a competitor's standard. Microsoft won't strengthen Google by adopting A2A. Google won't strengthen Anthropic by adopting MCP. The prisoner's dilemma prevents any single-vendor solution from reaching critical mass.
Every proprietary protocol from the 1970s-80s faced the same dynamic. IBM's SNA. DEC's DECnet. Xerox's XNS. All technically excellent. All dead. Replaced by TCP/IP — the protocol nobody owned.
Future 2: Fragmentation Persists (Costly)
Multiple incompatible standards coexist indefinitely. Enterprises maintain adapters between A2A, MCP, ACP, and whatever comes next.
Cost: $870 million per enterprise for point-to-point integrations. Multiplied by thousands of enterprises. A multi-trillion-dollar tax on the global AI economy.
This is technically possible but economically unsustainable. The integration costs will eventually force consolidation — the only question is how much money is wasted before it happens.
Future 3: An Open Standard Emerges (Historical Pattern)
A neutral, open-source protocol — owned by no one, usable by everyone — becomes the common layer that all vendors can adopt without "losing."
Historical probability: 100%. This has happened with every communication technology in history. The only variable is time.
What the TCP/IP of AI Looks Like
Based on every successful protocol standardization in history, the TCP/IP of AI will have these properties:
- Open Source (Apache 2.0 or Equivalent)
No patents. No licensing fees. No vendor advantage. Any company can implement it without enriching a competitor. Any startup can build on it without asking permission.
Apache 2.0 is the gold standard because it explicitly grants patent rights and allows commercial use without restrictions. Companies can adopt it without a 6-month legal review.
- Semantically Clear
Not just message formats — shared meaning. A vocabulary of precisely defined concepts that eliminates ambiguity.
HTTP succeeded because GET and POST have exact, universally agreed meanings. The AI protocol needs the same clarity: ACT.QUERY.DATA must mean exactly one thing, everywhere, always.
- Politically Neutral
Not owned by any competitor. Not governed by any single company's interests. Community-driven development where every contributor has equal voice.
The moment a protocol becomes identified with one company — even if it's technically open source — adoption resistance appears. TCP/IP worked because it came from academia (DARPA/universities), not from IBM or DEC.
- Simple Enough to Implement
If it takes a team of 20 engineers six months to implement, it's too complex. The protocol needs to be implementable by a single developer in days.
TCP/IP's simplicity was considered a weakness by its critics. It turned out to be its greatest strength. Simple protocols get implemented. Complex protocols get debated.
- Backward Compatible and Extensible
The core protocol must be stable. Extensions must be possible without breaking existing implementations. Version 2 must talk to version 1.
HTTP has maintained backward compatibility for 30 years. That stability is why it's still the foundation of the web. The AI protocol needs the same commitment to stability.
The FOMO Calculation
For every CTO reading this, here's the decision framework:
If you adopt an open semantic standard now:
- Integration costs drop by 90%
- New AI systems plug in immediately
- You can switch vendors without rebuilding integrations
- You're ready when the network effect arrives
- Your competitors are scrambling to catch up
If you wait:
- You pay the integration tax ($2M per connection) for years
- Every vendor change is a multi-million dollar project
- When the standard becomes inevitable, you migrate under pressure
- Your competitors who adopted early have years of expertise
- You're the company that migrated from DECnet to TCP/IP in 1995
If you build proprietary:
- You create yet another incompatible standard
- Your agents can only talk to your other agents
- Partners and customers can't integrate without custom work
- You've recreated the problem you were trying to solve
The math is clear. The history is clear. The institutional momentum is clear.
Who Moves First
The standardization window is open now but won't stay open forever. Once a standard reaches critical mass — typically 5-10% of the target market — the network effect makes it self-reinforcing.
In the TCP/IP adoption: Universities and research labs moved first (1983-1990). Then government agencies (1990-1993). Then enterprises (1993-2000). The early movers shaped the Internet. The late movers adapted to it.
In AI agent standardization: The early movers will be:
- Startups that can adopt without committee approval
- Research organizations that value interoperability over lock-in
- Forward-thinking enterprises that see the integration cost trajectory
- Open source communities that build the ecosystem
The late movers will be:
- Large enterprises waiting for "the committee to decide"
- Organizations locked into single-vendor ecosystems
- Companies that confused "we use AI" with "we're ready for the AI economy"
The Window
NIST, W3C, IETF, and the Linux Foundation are all converging on AI agent interoperability. Standards committees move slowly — typically 3-5 years from initiation to ratification.
That means the next 24 months are the window where early implementors shape the standard. After that, the standard shapes them.
The PULSE Protocol exists today. 1,000 semantic concepts. 10 categories. Apache 2.0. Production-tested with 256 passing tests, TLS transport security, binary encoding (10x compression), and cryptographic message signing.
It may become the standard. It may influence the standard. It may be one input among many.
But the question it answers — "how do AI agents share meaning?" — will be answered. By someone, somehow, in the next few years.
The only question is whether you'll be building the answer or buying it.
Sergej Klein is the creator of PULSE Protocol (Protocol for Universal Language-based System Exchange) — an open-source semantic communication standard for AI systems. 1,000 concepts. Apache 2.0. Free forever.
GitHub: github.com/pulseprotocolorg-cyber/pulse-python
PULSE Protocol is open source (Apache 2.0). Free forever.
Try it:
pip install pulse-protocol
Top comments (0)