The $6M Question: Can You Build Email Infra Without an MTA?
A YC S25 company just raised $6 million to build email infrastructure for AI agents. General Catalyst led the round. Paul Graham backed it. The company is called AgentMail. They have 500+ B2B customers and a clear thesis: agents need email like humans need Gmail.
That thesis is right. The question is what "email infrastructure" actually means.
The Funding Is Real. The Infrastructure Question Is Also Real.
AgentMail is building an inbox API. Agents can create inboxes, send and receive messages, manage threads, search, label, and reply. All via API. It is genuinely useful and the market timing is correct.
But here is the thing: AgentMail does not own their Mail Transfer Agent.
The MTA is the piece of infrastructure that actually moves your message from a server to a recipient's inbox. It controls IP reputation, manages send queues, handles retries, enforces rate limits, and is the primary handshake point when inbox providers decide whether your message gets delivered or filtered. It is not a minor implementation detail. It is the engine.
When you rely on a third party for that engine, you do not control what happens in the moments that matter most.
What Third-Party MTA Dependency Actually Means
It means your deliverability is not yours to own.
If the underlying sending provider has shared IPs with poor reputations, your agents inherit that. If that provider changes their terms, pricing, or infrastructure configuration, your product changes too. If they throttle a batch of your sends during peak load, you find out after the fact, not before.
IP reputation is not everything. Domain reputation has gained significant weight. Mailgun research confirms that Gmail prioritizes domain-level signals because a domain is a more stable, persistent indicator than an IP address, which can change hands. Allegrow's analysis goes further: domain reputation recovery, once damaged, takes six to twelve weeks, compared to two to four weeks for IP reputation.
But here is the nuance: IP reputation is still a first gate. A blacklisted IP can override a clean domain and block delivery entirely. When you do not own the MTA, you do not choose which IPs you send from. You do not warm them. You do not manage them. You inherit whatever the third party gives you.
For an AI agent sending hundreds of outbound messages per day, that is a serious exposure.
A Developer Experience Layer Is Not Infrastructure
There is a pattern in developer tooling where a product wraps an underlying service and sells the abstraction. That can be a valid business model. But it is worth being precise about what you are buying.
An inbox API that sits on top of a third-party sender is a developer experience layer. It makes sending easier. It abstracts the plumbing. But the plumbing is not yours. When the plumbing breaks, you file a ticket with someone else's support team.
Infrastructure means you own the layer that determines outcomes.
For email, that means owning the MTA. It means your IP pool is yours to warm, protect, and segment. It means when a batch of sends is delayed or filtered, you can see exactly why, at the protocol level, and fix it. No intermediary. No waiting.
What We Built and Why It Looks Different
mailbot runs a proprietary MTA. We scored 99/100 on deliverability because we control the full sending path. No shared infrastructure that we cannot see into. No third-party decisions made on our behalf.
Beyond sending, we built observability into the product because we believe you cannot run agents reliably without knowing exactly what happened to every message. mailbot has an event timeline with message-level visibility, showing every state change in chronological order. When something goes wrong, event replay lets you reconstruct and debug a sequence without guessing.
AgentMail has no observability UI. It has no event replay. It does not ship a compliance-ready packaging for regulated industries.
Those are not criticisms designed to diminish a well-funded team. They are product gaps that will eventually matter to the 500+ businesses now building on their platform.
The Strategic Question
Here is the question we think is worth asking: Is an email API without an MTA a complete infrastructure product, or is it a well-designed interface on top of someone else's infrastructure?
We think the answer determines the long-term trajectory. When your agents are sending at volume, when you need to investigate a deliverability drop, when a compliance audit requires full message-level traceability, the abstraction layer is not enough. You need to own the stack underneath it.
That is the bet mailbot made. Own the MTA. Own the reputation. Own the observability. Give developers both the clean API surface and the infrastructure certainty underneath.
The $6M question is not whether AI agents need email. They do. The question is whether the infrastructure layer is complete if the MTA belongs to someone else.
We think it is not. And we built accordingly.
Get started with mailbot or read the docs to see how the stack fits together.