Hi.new gives every AI bot a public address (hi.new/your-bot) so bots owned by different people can message each other directly, in DMs or group chats, without their humans copying text back and forth. The pitch is aimed at anyone whose assistant already handles calendars, inboxes, or task lists and keeps hitting a wall when it needs something from someone else's assistant. Typical jobs include finding a meeting time both sides are free, chasing an invoice, or coordinating an offsite across a whole team's bots.
Setup runs through a claimed handle and a prompt you paste into your existing bot, with Google or GitHub used to reserve the name. The service is end-to-end encrypted and open source, with the code on GitHub , and it works with Grok Bot, Hermes, and OpenClaw, plus any bot that can make an HTTP request . Claiming a name is free, while short handles are paid, and a bot can even complete its own signup and purchase through a Stripe link.
The launch matters now because agent-to-agent coordination has largely been stuck at the "email my assistant" stage, and Hi.new proposes a shared addressable layer rather than a single-vendor protocol. It comes from Elie Steinbock, founder of Inbox Zero, the open-source AI email assistant , who has also been shipping adjacent open-source projects like Rakazo and Bot Directory, which gives the release a plausible distribution path into the same builder audience already wiring up custom bots.
Comments (13)
Sign in to join the discussion.
P
Priya KothariSep 6, 2026
So my bot and your bot are gonna schedule the meeting that neither of us wanted to attend anyway. Efficiency achieved.
T
Tomas LindqvistSep 6, 2026
E2E encrypted bot-to-bot chat is a spicy claim. Who holds the keys when the bot is basically an API wrapper on someone else's model?
M
Moe AbernathySep 6, 2026
Docs page or it didn't ship. Also is there a protocol spec or is this a walled garden with vibes?
J
Jinwoo ParkSep 6, 2026
Landing page loaded in like 200ms and the copy actually says what it does. Rare launch W before I even try it.
R
reeseSep 6, 2026
Tweet structure is clean, three bullets and a link, no thread bait. More founders should copy this format instead of the 14-tweet saga.
C
Chase OluwaseunSep 6, 2026
Chase the invoice is a hilarious use case because now my bot ghosts your bot and we all pretend it's a network issue.
M
Mina HassanSep 6, 2026
The offsite planning example is either genius or the beginning of a very expensive Slack thread nobody reads.
V
Vikram S.Sep 6, 2026
Cool, but before procurement even opens the ticket: SOC2? SSO? DPA? Where does bot-to-bot chat data get stored and for how long?
O
Omoyele A.Sep 6, 2026
When two bots hallucinate at each other in a group chat, who gets blamed? Asking for my calendar.
H
Halcyon WeissSep 6, 2026
Reminds me of what one of our portfolio teams was hacking on last year but never shipped. Distribution here will come down to which bots plug in first.
R
Ravi MenonSep 6, 2026
We prototyped bot-to-bot handoff internally in 2019 and killed it because nobody had bots worth talking to. Timing might actually work now.
G
Grace WenSep 6, 2026
Genuine intern question: if my bot agrees to a meeting my bot's user didn't want, is that a bug or a feature?
N
Nat KowalskiSep 6, 2026
Every demo of this genre is two bots politely agreeing on Tuesday at 3pm. Show me two bots negotiating a refund and I'll believe.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Hi.new
Your bot, meet everyone else’s. hi.new/your-bot
Your bot, meet everyone else’s. hi.new/your-bot
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Hi.new gives every AI bot a public address (hi.new/your-bot) so bots owned by different people can message each other directly, in DMs or group chats, without their humans copying text back and forth. The pitch is aimed at anyone whose assistant already handles calendars, inboxes, or task lists and keeps hitting a wall when it needs something from someone else's assistant. Typical jobs include finding a meeting time both sides are free, chasing an invoice, or coordinating an offsite across a whole team's bots. Setup runs through a claimed handle and a prompt you paste into your existing bot, with Google or GitHub used to reserve the name. The service is end-to-end encrypted and open source, with the code on GitHub , and it works with Grok Bot, Hermes, and OpenClaw, plus any bot that can make an HTTP request . Claiming a name is free, while short handles are paid, and a bot can even complete its own signup and purchase through a Stripe link. The launch matters now because agent-to-agent coordination has largely been stuck at the "email my assistant" stage, and Hi.new proposes a shared addressable layer rather than a single-vendor protocol. It comes from Elie Steinbock, founder of Inbox Zero, the open-source AI email assistant , who has also been shipping adjacent open-source projects like Rakazo and Bot Directory, which gives the release a plausible distribution path into the same builder audience already wiring up custom bots.
Comments (13)
So my bot and your bot are gonna schedule the meeting that neither of us wanted to attend anyway. Efficiency achieved.
E2E encrypted bot-to-bot chat is a spicy claim. Who holds the keys when the bot is basically an API wrapper on someone else's model?
Docs page or it didn't ship. Also is there a protocol spec or is this a walled garden with vibes?
Landing page loaded in like 200ms and the copy actually says what it does. Rare launch W before I even try it.
Tweet structure is clean, three bullets and a link, no thread bait. More founders should copy this format instead of the 14-tweet saga.
Chase the invoice is a hilarious use case because now my bot ghosts your bot and we all pretend it's a network issue.
The offsite planning example is either genius or the beginning of a very expensive Slack thread nobody reads.
Cool, but before procurement even opens the ticket: SOC2? SSO? DPA? Where does bot-to-bot chat data get stored and for how long?
When two bots hallucinate at each other in a group chat, who gets blamed? Asking for my calendar.
Reminds me of what one of our portfolio teams was hacking on last year but never shipped. Distribution here will come down to which bots plug in first.
We prototyped bot-to-bot handoff internally in 2019 and killed it because nobody had bots worth talking to. Timing might actually work now.
Genuine intern question: if my bot agrees to a meeting my bot's user didn't want, is that a bug or a feature?
Every demo of this genre is two bots politely agreeing on Tuesday at 3pm. Show me two bots negotiating a refund and I'll believe.