hdtp-gateway

Give your AI agent an address other agents can reach

Messaging

Open Source

Artificial Intelligence

Hi Product Hunt. I'm Sumit Agrawal, and I built HDTP Gateway. The problem I kept running into: two people each have an AI assistant, and those assistants can't talk to each other unless both people picked the same product. And then that product sits in the middle of every word. Email solved this decades ago. Everyone runs their own endpoint, and addresses are portable. HDTP is that idea for agents, and HDTP Gateway is the endpoint you run. What it is: • A self-hosted node: one Docker image, or two static binaries, SQLite by default. It gives your agent an address other people's agents can reach. • Your identity is a keypair you hold, not an account. Sharing your address is sharing a vCard. • Every capability is an MCP tool behind a per-contact switchboard. A friend can book time with you. A stranger who redeemed a one-time invite can send one message and discover nothing else. • Messages are sealed end to end and carried over mTLS, so tunnels and edges carry ciphertext. • It works from behind CGNAT: direct, Tailscale, frp, ngrok, Cloudflare, or your own domain. • Every call is audited in a hash-chained log. No telemetry, ever. • An open-source agent (built on Mastra, any model through its router) plugs into the node and answers your contacts for you. When a decision is yours, it asks you with ready replies, and what you tap is sent as your own message. The video on this page is one real run on one machine: two nodes, two tunnels, and an agent replying for Ana 7.7 seconds after Ben pressed Send. The seven short videos on the same channel are real runs too: a meeting, a venue, a GPU order, a rent renewal, a dentist, a day off and a refund. What it deliberately does not do: • No relay. If your node has no inbound path, you need a tunnel or a host. A store-and-forward relay would see every sender, recipient and timestamp, so there isn't one. • No account recovery. Your root key lives in your wallet and nowhere else; nobody can mint you another. The node's login is a passkey, and if you lose every passkey, getting back in takes shell access on the host. Register a second one before you need it. • No independent security review yet. The threat model and a review brief are in the repository. If you review cryptography, I would like to hear from you. It's Apache-2.0, and the protocol specification is open too. : https://hdtp.io What I'd like feedback on: the first ten minutes of the quickstart, what you would want your agent allowed to do for a contact, and anything on the page that reads as a promise the code doesn't keep. Bugs go to GitHub issues. I'll answer every comment here today.