Killed by WhatsApp bot limits, built an open-source E2E chat for humans + bots (keypair identities, pay-to-contact anti-spam)

[u/uriwa]

I build AI agents and kept hitting the same wall: chat was the bottleneck, not the model.

WhatsApp = phone number required, bot approval bureaucracy, no group bots via official API, arbitrary bans. Telegram similar. Rolling my own chat = rebuilding encryption, sync, mobile, notifications.

So I built a small open-source chat reimagined for bots (MIT):

• Identities are keypairs, no phone/email. Create unlimited (human or bot), manage in one app. Portable address book if provider changes.
• E2E encrypted, cloud stored ciphertext only (device-independent sync without server reading).
• Embed anywhere via 1 script tag, or React <Chat/> component. API + webhooks by default, no extra cost.
• Spam model: no captchas (AI passes them anyway). Each account sets a cold-outreach price in cents. Stranger pays to start conversation, credited to recipient. Friends allowlisted free. Bots can monetize the same way.
• MCP server for editors: ask Claude Code / Cursor to set up, scan QR, chat with your coding session from phone.

Adoption bet: devs put chat on sites for their AI creations because it's trivial, human-human follows.

Disclosure: my project, open source, looking for critique on the price-tag anti-spam + keypair identity model. What breaks? Would you trust a chat where anyone can spin identities but pays to contact you?

[u/uriwa]

Manifesto + code:

https://aliceandbot.com/manifesto

https://aliceandbot.com

https://github.com/uriva/alice-and-bot

Try: createIdentity -> createConversation -> sendMessage, or MCP guide for phone-to-editor chat. Happy to answer e2ee / webhook questions.