Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes

169 points by Haakam21 ↗ HN
Hey HN, we're Haakam, Michael, and Adi. We're building AgentMail (https://agentmail.to), the email inbox API for agents. We’re not talking about AI for your email, this is email for your AI.

Email is an optimal interface for long-running agents. It’s multithreaded and asynchronous with full support for rich text and files. It’s a universal protocol with identity and authentication built in. Moreover, a lot of workflow critical context already lives in email.

We wanted to build email agents that you can forward your work to and get back a completed task. The agents could act entirely autonomously as you wouldn't need to delegate your identity. If they did get stuck they could just send you, or anyone else, an email.

Using Gmail, we kept getting stuck on the limitations of their API. No way to create inboxes programmatically. Rate and sending limits. OAuth for every single inbox. Keyword search that doesn't understand context. Per-seat pricing that doesn't work for agents.

So we built what we wished existed: an email provider for developers. APIs for creating inboxes and configuring domains. Email parsing and threading. Text extraction from attachments. Realtime webhooks and websockets. Semantic search across inboxes. Usage-based pricing that works for agents.

Developers, startups, and enterprises are already deploying email agents with AgentMail. Agents that convert conversations and documents into structured data. Agents that source quotes, negotiate prices, and get the best deals. Agents that emulate internet users for training models on end-to-end tasks.

Here's demo of Clawdbots communicating using AgentMail: https://youtu.be/Y0MfUWS3LKQ

You can get started with AgentMail for free at https://agentmail.to

Looking forward to hearing your thoughts and feedback.

60 comments

[ 0.59 ms ] story [ 64.7 ms ] thread
The 2FA via email case is great. I recently had to build a browser automation workflow that required 2FA. I ended up using Zapier to monitor email inbox and then extract the code and send back to our API. It was a bit slow.
"Application error: a client-side exception has occurred while loading www.agentmail.to (see the browser console for more information)."

> Looks at developer console...

- "Failed to create WebGL context: WebGL is currently disabled." Dafuq does an email website need WebGL for?

- "Cookie “dmn_chk_xxxxxxxx-yyyy-dead-beef-123456789ABC” has been rejected for invalid domain."

Let me guess...vibe-coded?

hah this is a great idea! sending email is such a common way to communicate and having agents with an inbox makes so much obvious sense. heh just don't let their addresses get out who knows how they'll respond to spam and phishing attempts.
Hey I’m also working on this what a coincidence: https://ai-chat.email

Second time at least HN is launching YC on one of my products:

BrowserBox - hyperbeam

Mailpilot/AI-chat.email - agentnail

amazing now do the same for voice and sms!
In the future all the agent communication will be using agentmail!
Finally agents can spam other agents, instead of humans.
Cool launch. Assuming you guys view email (and therefore SMTP) as becoming the de facto agent communication protocol in the long run. My question — why not something bespoke, similar to OpenAI’s Agentic Commerce Protocol or x402 from Coinbase?
Very interesting. I have a lot of enterprise AI use cases that would really benefit from being email native.

We’re an O365 GCC shop. Appreciate that your enterprise options include Bring Your Own Cloud, that makes things much easier for us.

It would be nice to have integrations with n8n and Glean.

AgentMail looks amazing!
> Agents that source quotes, negotiate prices, and get the best deals.

Didn't Alexa fail miserably with the "have AI buy something for me" theory?

There is a significant mental in allowing someone else make purchase decisions on my behalf:

- With a human, there is accountability.

- With deterministic software, there is reproducibility.

With an agent, you get neither.

FWIW - I am not anti-LLM. I work with them and build them full time.

How does this differentiate from a solution like AWS SES? (Which I assume AI Agents would be quite adept at using to send email)

I understand the differentiator vs GMail, but API-based scripted email access isn’t new.

How do you think this will help with identity verification in the future?
> Email is an optimal interface for long-running agents.

Long-running agents are themselves not optimal though. There are a ton of these coordination layers for long running agents now but they don't make any sense under other paradigms

I'm concerned that this fits in "using today's innovation to solve outdated paradigms".

Google has A2A: An Agent-to-Agent Protocol. SaaS is plumetting in value.

Arbitrary semantics made sense when communications were human-dominated.

If agents dominate these fields, why wouldn't they simply set their own protocols and methods to communicate both text, binary, and agreed data structures?

There's an assumption that email is somehow the best channel, when you've found yourself that the most popular, functional interfaces don't align with your expectations.

Then, ultimately I have a single agent that can sit in numerous communication platforms, such as email

And you probably don't want to dump the emails first thing into the agent's context. You should insert a cup of coffee and the morning newspaper into the context, and only then the emails.
So AgentMail uses Mail Agent
Looks like SES + api access, isn’t Amazon offering that already?
It’s a really nice idea actually. There will be some concerns, maybe some mistakes, but it really works as a mean to communicate much easier with an agent
Thanks, yes we are continuously learning
This is super interesting. Interesting to see how I'll be able to use this to help my customers with handling email responses. Gmail sucks for this. Super excited to see what you guys develop this into. Will this be able to eventually expand to other forms of agent communication (i.e. payment or phone numbers)?
(comment deleted)
The moat for SaaS is gone.

I am 99% certain I could build to parity in a weekend using Cloudflare without the the pricing limitations.

I am thinking it would be within the free tier of CF usage.

I am not certain I have the bandwidth to communicate over delivery and plain text inspection concerns.