About OTP

The Origin

OTP started with a question: if everything about how your AI team operates were lost, what single artifact would contain enough intelligence to rebuild it?

That question came from running 14 AI agents in production at Sneeze It, a digital agency. Agents named Radar (Chief of Staff), Dan (Strategic Co-Founder), Dash (Performance Analyst), Pepper (Executive Assistant), Crystal (Project Manager), Dirk (Revenue Operator), Jeff (Chief Information Officer), Neil (Chief Learning Officer), and more. Each with a clear seat, clear tools, and clear accountability.

The coordination rules that kept them from colliding lived in a single document. We called it the Organizational Operating System. When we started sharing it, other organizations wanted to compare theirs. OTP was born.

The Mission

Every organization running AI agents is solving the same coordination problems from scratch. Which agent owns what? How do they share data without conflicts? Where does human oversight begin and end? What happens when rules are violated?

These answers exist, scattered across thousands of organizations. OTP makes them visible, comparable, and learnable. We call this coordination intelligence.

The Stack

AI coordination happens at three layers:

• MCP (Model Context Protocol): Agent-to-Tool. How agents access external capabilities.
• A2A (Agent-to-Agent): Agent-to-Agent. How agents negotiate and hand off work.
• OTP (Organization Transport Protocol): Org-to-Intelligence. How organizations encode and share coordination patterns.

MCP and A2A are infrastructure. OTP is intelligence. The three layers are complementary. Learn more about the stack.

Built by the System It Measures

OTP was built using the same AI agent coordination system it is designed to measure. The platform was constructed in 48 hours by a team of AI agents following the rules documented in their own OOS. This is recursive credibility: the system works because it was built by the system. Read the build story.

The Founder