PAIX

PAIX

A Simple but Powerful Protocol for the Agentic Internet

12 followers

Visit website
PAIX is an open protocol that upgrades email into a shared interface for you and your AI to interact with services. Works as normal email on day 0, with gradual upgrade paths for identity, login, and API-like actions.
PAIX gallery image
PAIX gallery image
PAIX gallery image
PAIX gallery image
Free
Launch tags:Open Source•Developer Tools•Artificial Intelligence
Launch Team / Built With
AssemblyAI
AssemblyAI
Build voice AI apps with a single API
Promoted

What do you think? …

Valto Loikkanen
DealIndex
Maker
📌
Hi everyone! I'm Valto, one of the creators of PAIX. We’ve been working on this because the internet today isn’t designed for AI acting on your behalf. Services still expect humans to click through browsers or apps, while AIs “watch over the shoulder.” That doesn’t scale. PAIX (Private AI eXchange) is a simple but powerful open protocol that turns email into a universal interface shared by you and your AI. Every service already supports email, every individual already has it — PAIX makes it structured, secure, and future-ready. Why now? Because your AI will need its own email anyway. With PAIX, one address can act as your ID, verified email, login, comms, API key, and AI interface. It works as normal email on day zero, but can scale up gradually to more advanced interactions. We’ve published the first spec + examples on GitHub (MIT-licensed). Would love your feedback, critiques, and collaboration as we shape this together: 👉 https://github.com/privateaiexch... Excited to hear what you think, – Valto
Vatsal M

It is innovative and also commendable to build for the AI future. But, we already have another established protocol now MCP that is also build to solve very similar problem imo. How is it different from it and what is your plan for making this wider adoption in the dev community?

Valto Loikkanen
DealIndex
Maker

@vatsmi Thank you very much for your comment. MCP has in deed been a big inspiration for this and MCP is amazing. But unfortunately it also requires a communication channel, where as today that is very much the traditional API that is required with that. PAIX makes email into more intelligent communication channel on top of existing infra. In a way making email into universal API that everyone already has. Also PAIX dont take any stand into what is the communication inside this channel, only how to get more use out of it. As such its complementary to MCP (ie MCP protocol can be one format to communicate inside PAIX email).

Mike Prince

@vatsmi  @valto 

Email also requires communication channels (ever since the old days of multi channel MTAs sometimes using dialup!)

An issue with email is that's it's one way: fire off an email and hope it's received and processed correctly, and then the recipients might decide to fire a one-way message back.

Two way pipes (mostly built on TCP/IP) are the way most of the Internet works these days and for good reason :)

MCP (like was mentioned above) and A2A are leading protocols for working with agents and can provide secure, trusted, and real-time two way communications. A2A even has a facility for delayed responses where the recipient can take time to think, or even loop in the human, before responding to a request.

Lots of great work is being done in the protocol space!