AgentMail Is Giving AI Agents an Inbox

Email may be the least glamorous piece of infrastructure on the internet. It is also one of the hardest to avoid.

Want to open an account? You need an email address. Reset a password? Email. Receive an invoice, confirm a reservation, send a document, or communicate with a customer? Somewhere in the process, there is usually an inbox.

That was fine when the internet assumed a person was on the other side.

AI agents are beginning to break that assumption. They can navigate websites, use software, write code, schedule meetings, process documents, and complete increasingly complicated workflows. But when an agent needs to communicate with the outside world, it often runs headfirst into infrastructure designed for humans.

That is the problem AgentMail is solving.

The Problem Was the Inbox

Haakam Aujla, Michael Kim, and Adi Singh arrived at AgentMail while trying to build email agents of their own.

The idea was to create agents that people could forward work to and get back a completed task. Email was a natural interface: it is asynchronous, supports files and long-running conversations, and already connects nearly every person and business on the internet.

But the agents kept running into the infrastructure underneath them. Gmail wasn’t designed for software that might need to create and operate large numbers of inboxes programmatically. Provisioning was cumbersome, APIs were restrictive, and existing email tools were generally designed around sending messages rather than giving autonomous software a persistent inbox of its own.

After talking with developers facing similar problems, the founders realized the agents weren’t the bottleneck. Email was.

So they built AgentMail: an API that lets developers create persistent inboxes for agents, then send, receive, search, label, and manage email programmatically. Instead of forcing an agent to borrow a person’s Gmail account, the agent can have an address and history of its own.

The idea is almost comically simple: give an agent an inbox.

The implications are much larger.

The Internet Already Speaks Email

One of the more interesting things about AgentMail is that it doesn’t require the rest of the world to change.

Businesses have spent decades wiring email into nearly everything they do. Customers send questions through it. Vendors send purchase orders. Banks send alerts. SaaS products send authentication codes. Recruiters schedule interviews. Companies exchange documents, invoices, contracts, receipts, and countless other pieces of information through the same basic system.

An agent with an email address can participate in all of it.

That matters because agents are increasingly moving from generating information to actually doing things. The moment software begins acting on someone’s behalf, it needs a way to communicate with people and services that were never designed to talk directly to AI.

Email becomes a surprisingly powerful compatibility layer.

And as agents become more capable, the infrastructure starts to look different from traditional email. A company might operate many specialized agents, each with its own inbox, identity, permissions, history, and relationships. AgentMail was designed around that model from the beginning, with inboxes as programmatically provisioned infrastructure rather than another human seat in Google Workspace.

Built for a New Kind of User

The founding team came to the problem with backgrounds across quantitative systems, autonomous vehicles, and technology investing. Haakam previously worked as a quantitative researcher at Optiver. Michael worked on autonomous vehicles at NVIDIA. Adi came from Accel.

But the more interesting founder-market fit came from building the product themselves. They wanted autonomous agents that could communicate and get work done through email, encountered the limitations of the existing infrastructure, and decided the underlying primitive needed to be rebuilt.

That perspective has continued to shape the company. AgentMail isn’t trying to make Gmail better for humans. It is asking what email should look like when the user on the other side of the inbox is software.

That distinction sounds small, but it leads to a very different product.

From Communication to Identity

An email address is more than a place where messages arrive. On the internet, it has become part of how we establish identity. We use it to create accounts, authenticate ourselves, recover credentials, receive permissions, and maintain relationships with services over time.

Agents will need many of those same capabilities.

Today, many agents still operate by borrowing a human’s identity. They use our accounts, credentials, and inboxes. That works while agents are essentially assistants. It becomes harder as they begin operating more independently and as companies deploy larger numbers of them.

AgentMail sees email as an early piece of a broader communication and identity layer for this new population of software users. The company itself increasingly describes the opportunity in those terms: persistent identity, reliable communication, permissions, memory, and a system of record for agents.

That is a much bigger idea than email infrastructure, and it’s what makes the company particularly compelling to us.

Why We Invested

We’ve been fortunate to invest in developer infrastructure through several generations of computing, and one pattern keeps repeating. New platforms eventually need primitives built specifically for them.

Agents are creating another one of those moments.

They need browsers they can operate, identity they can control, permissions they can carry, ways to move money, and ways to communicate. AgentMail is starting with perhaps the most universal of those primitives: an inbox.

What we like about the company is how naturally the opportunity can expand from there. If agents become a meaningful new class of internet user, email could be the beginning of a much larger communication and identity layer built around them.

Haakam, Michael, and Adi didn’t arrive at that thesis by drawing a market map. They were trying to build agents that could work through email and discovered the infrastructure wasn’t there.

So they built it.

For now, AgentMail gives AI agents an inbox. Someday, that inbox may be how the rest of the internet knows who they are.

Visit AgentMail at https://www.agentmail.to.