TL;DR: Inkbox is the identity and communication layer for AI agents: giving agents their own email, phone, iMessage, and internet address. Inkbox pulls together what your agent sees across email, calls, iMessage, and more, so your agent can act on the full context.
Hey YC! We're Ray, Alex, and Dima building Inkbox.
How we got here
A few months ago we were building web-automation agents. Every time an agent needed to log into a portal, it had to receive a confirmation email or get a 2FA code. And when we were away from our desks, we wanted to seamlessly contact the agents themselves: text them, check in, get a reply. We ended up stitching together services like Gmail, Twilio, and ngrok: separate services, each built for humans, none of them sharing any identity or context.
That's the problem we set out to fix. We didn't need another email or voice API. We needed one service to tie its identity together with rich context. So we built it.
A persistent internet address (HTTPS tunnel) to receive internet traffic, like webhooks
An encrypted credential vault with TOTP/2FA
Who we are
Ray (CEO): CS PhD from MIT; previously cofounded Empallo, an AI virtual clinic for cardiovascular patients.
Alex (CTO): MS in CS @ Northeastern. Previously ML engineering and computer networking research.
Dima (CAIO): built ML pipelines on gigapixel pathology images at Harvard Medical School; co-author on 6+ peer-reviewed publications.
Quick demo with Claude: Watch Claude Code provision an email, phone, and iMessage in a Minute.
Our ask
Try it. Drop Inkbox into your preferred agent harness: we have plugins for Hermes, OpenClaw, Claude Code, and Codex. Each one runs a wizard that provisions Inkbox resources for your agent.
Intros. We'd love intros to teams running fleets of agents that each need their own identity to act in the real world: reaching out to people and businesses (email/phone/iMessage), holding their own accounts, and authenticating with a built-in credential vault.
Contact Ray at ray@inkbox.ai. Would love your feedback.