Inkbox Wants to Give Every AI Agent an Address of Its Own

Picture an AI agent, mid-task, doing everything right. It fills out a signup form, clicks the button, and then stops. A message appears: please confirm your email address. There is no email address. There is no inbox to open, no code to fetch. The agent, moments ago fluent and capable, is now standing outside a locked door with no key. This small, unglamorous gap is where a surprising number of agent demos quietly die - and it is exactly the gap Inkbox was built to close.

Inkbox, a Y Combinator Summer 2026 company based in San Francisco, describes itself plainly: the identity and communication layer for AI agents. The pitch fits in a breath. Give an agent its own email, its own phone number, iMessage, a persistent internet address, and a place to keep its logins. Do it through one API instead of a weekend of plumbing.

01 / The problemThe internet assumes a human is on the other end

For a few decades, the web has been built around one quiet assumption: somewhere behind every form, every login, every two-factor prompt, there is a person. A person has an inbox. A person has a phone that buzzes with a six-digit code. A person can be reached. Software agents break that assumption the moment they try to act on their own behalf.

The founders of Inkbox ran into this the hard way while building web-automation agents. Every time an agent needed to log into a portal, it had to receive a confirmation email or a 2FA code. Reaching an agent, or letting it reach out, meant stitching together Gmail, Twilio, ngrok and a handful of other tools - each one designed for humans, none of them sharing identity or context. The result was a pile of glue code that broke the instant you tried to run more than one agent at once.

"Inkbox pulls together what your agent sees across email, calls, iMessage, and more, so your agent can act on the full context." Inkbox, on why one identity beats five disconnected services

02 / The productWhat an agent actually gets

With one Inkbox API call, an agent is issued a bundle of real, working infrastructure. It is less a feature list than a starter kit for existing in the world.

The clever part is not any single channel. Twilio has done phone numbers for years; plenty of tools tunnel a webhook. The difference is that Inkbox treats all of it as one identity. Email, calls and iMessage flow through the same layer, so an agent is not just receiving isolated messages - it is accumulating context it can reason over. The confirmation email, the follow-up text, the callback all belong to the same agent, and the agent can see across them.

03 / Before & afterFrom glue code to a single call

04 / Who it is forThe people building the agents

Inkbox is developer infrastructure, and its earliest users are the people wiring up agentic workflows today - the ones who have already felt the confirmation-code wall firsthand. The company launched where those developers already work: as one-line plugins for Claude Code and Cursor, with support for agent frameworks like Hermes. An agent can even sign itself up by following the docs. It is a deliberate distribution choice - meet builders inside the tools they already have open rather than asking them to adopt a new one.

"With one Inkbox API, every agent gets a unique email inbox, a phone number that can call and text, iMessage, a persistent HTTPS address for webhooks, and an encrypted credential vault with TOTP/2FA." The one-sentence version of the product

05 / The teamThree researchers, one narrow idea

The founding trio arrives from unusually academic corners. Ray Liao, the CEO, holds a computer science PhD from MIT, where he studied machine learning, and previously cofounded Empallo, an AI-powered virtual clinic for cardiovascular care. Alex Wilcox, the CTO, comes out of Northeastern with a background in ML engineering and computer networking research. Dima Vremenko, the chief AI officer, was a research associate at Harvard Medical School building clinical prediction pipelines, with a stack of peer-reviewed publications behind him.

It is a notable swerve. Two of the three came from healthcare and biochemistry ML backgrounds before landing on something far narrower and more infrastructural: an email address for a robot. The company traces its lineage back to an earlier name, Vectorly - a thread still visible in the founders' contact addresses.

06 / The businessWhere it sits in the market

Inkbox sells to developers and companies building AI agents, a developer-facing API and SaaS model priced on access and usage. Its competition, for now, is mostly the do-it-yourself alternative: the tangle of Gmail, Twilio, ngrok and a password manager that a team assembles and then maintains. Inkbox's bet is that as agents multiply, that tangle stops being a weekend project and starts being a liability - and that a purpose-built identity layer becomes standard plumbing.

There is a quieter bet underneath the product, too. In one version of the agent economy, software acts anonymously, borrowing human credentials, hard to trace. Inkbox is building for the other version - where agents carry persistent, accountable identities of their own. Publicly, the company has raised a seed round of roughly $130,000 tied to its YC batch, with Tyler Bosmeny as its partner. Early, small, and pointed at a problem that grows every time someone spins up another agent.

Whether Inkbox becomes the default identity layer or one of several is still an open question. But the question it answers - how does an autonomous agent receive its own confirmation email - is one almost nobody thought to ask, right up until their agent hit that locked door. Inkbox asked it first, and turned the answer into a company.