This is really interesting and I'm sure it has many useful applications - what I am most impressed by is the popovers in your dashboard, which show SDK examples. This is a brilliant UI idea (executed with great polish) and is the first time I'm seeing it.
Unfortunately I'm not a potential customer and don't have useful feedback on the market landscape - all I can add is that I really love your design. Also it seems like you all launched the new landing page while I was typing this comment a little past midnight, so kudos on the work ethic as well.
Keep in mind that default Gmail allows webhooks for any changes (email received but also changing labels, etc), for free using Gmail pubsub. I use it a lot because it's the only way of getting programmatic notifications from credit card purchases (turn on purchase alerts to all cards, send to Gmail, have a filter archive but capture the reception in webhooks. Parse with simple regex)
Super fast low latency very satisfying. Pubsub scales well and free :)
Curious: how are you tackling abuse/spam at scale, especially as more agents start talking to each other? Also, any plans for plug-and-play integrations with popular agent frameworks, or is the focus purely on infra for now?
Congrats on shipping - looking forward to seeing your journey.
Thanks a lot! We're working on a lot of checks in place within our API for both the agents and email side, including things like spam filtering, verification, and protection against phishing or prompt injection. It's an interesting task at hand, solving both archaic and cutting-edge problems within the same product lol
I was previously considering building in this space but the infra around sending /receiving email for lots of addresses seemed like a major pain before getting to anything properly exciting, excited to see this! Would also encourage you to build good local dev/testing infra, dealing with email gets messy.
I believe truly useful AI assistants will use the same tools that humans prefer to use, rather than forcing us to come to it (in the same way truly intelligent embodied AI would use the same spaces/stairs/tools/doors as humans). Email, despite all its warts, still runs a lot of the world.
It has been a journey, in fact even harder than we were expecting. But can say it was well worth it after seeing the unlock for devs building in the email space.
Cool product. I see the need. Many vendors might look like they have similar capabilities on a powerpoint, but when you look one level deeper, they really don't. Eg, webhook notifications at 1 minute intervals with one big json of multiple emails, vs continuous/instant/single.
btw, would love to hear stories of you journey thus far. fwiw, I think you're really onto smtg!
This is perfect timing for me - was just thinking about how to do this. But pricing is a bit steep for a startup currently looking to prove the market. Would you consider a cheaper option (e.g. 1 free inbox, or maybe $20/mo for 5 agent inboxes and a more limited storage level)? I'm building something that I might consider this for, but I don't know how long my runway is before I get sustainable client revenue, so $100/month is a deep hole being burned in my personal pocket before I can prove my MVP out.
I do not have a use case for this _right now_. But I am a 100% sure I will have one pretty soon.
Email has become this massive, constant influx of information, that cannot be managed with just adding an AI agent to it. It takes so much more context knowledge to get right. None of the tools I have tried so far seem to solve this problem the way I would need it.
So sooner or later I might solve it for myself. And you guys will get a new customer.
sadly it never took off so it just became another abandoned side project
but still sometimes I use it ie do distill long emails or translate them without leaving the inbox - also the reminder and todo list feature is nice - whereby i mostly use the "remind me of this email next monday"
so my learnings for email agents: give them a sense of time and memory. its not only about that you write an email and send it but also when to write whom
Sorry for plugging in our product here but this comment seemed relevant. We are actually building something similar at mxgo[.]ai. Started exactly same way as you did, now working on a chrome extension with suggestions within inbox. Would love to connect and know your feedback.
One of the most important startup lessons to learn, in perpetuity, is not to underestimate email.
I learned this the hard way when I was running a startup 15 years ago (we used sign in with Twitter and didn't required people give us their email address) and it's still true today.
Email is almost universal, mostly free from gatekeepers and is an incredibly effective way to keep your product relevant in a way that doesn't depend on your users remembering to visit your site or open your app.
There are people out there who don't use email, but they tend to not be people who spend serious money on the kind of products most startups are building.
Agree that interfaces are moving in this direction. But humans and agents will always need a way to send/receive messages and notification asynchronously. Email is the most universal channel and we think it is here to stay.
This. I also think e-mail clients are a more natural interface for managing multiple async conversations/tasks with models/agents from different providers.
There's also nothing stopping this product from expanding to other interfaces/modalities like voice or sms.
I would actually go as far as potentially considering email a distributed protocol for live-chat considering how quickly they are delivered [1]. I'm aware that is not how many people use them, but I believe that is more related to the interface and not the underlying technology. Somebody could probably built a live-chat messenger that looks like Teams or iMessage while actually just being an email client. Edit: This already exists [2].
Great question - we get this input a lot. It really depends, while I'm a big believer of voice and API-driven design in the future, I think email's role remains but looks different. It's a sticky, universal protocol that serves as a great system of audit and record. Also think an agent is only as good as its context - an inbox serves almost as a personal gateway to the internet and early customer's use cases show different applications from agent-human connection to identity verification and authentication.
What a silly take. Email has been around for ages and it will continue to be around in perpetuity. It's still the medium of choice for certain types of interactions where a documented paper trail is important and you eg; need escalation, further review, etc. It's still also the choice for many companies and individuals.
What is the infrastructure tooling behind this product? I wanted to build this but it seemed like it is not a small startup project to build such big infra without riding on the existing email infra (which results in loss of the excitement to actually build the project itself and continue using the existing email infra by giants)
You can do this with SES on AWS or Mailgun.
We use SES for this exact use case. Giving agents programmatic access to an email inbox and programmatically creating inboxes.
Yes you can use SES or Mailgun. But you would also need to build inboxes, email threading, attachment parsing, semantic search, structured data extraction, and more.
Fair concern but that comes with any email product. We're a provider not a mass sending API like Resend, Mailgun, Sendgrid - that means our use cases primarily revolve around personalized, two-way conversations between reasoning agents and humans.
You mentioned one of your use case is outbound (can totally see this being perhaps your biggest opportunity): How are people using this for outbound? As a full-cycle AI sales agent?
I'm interested in trying agentmail for one of our internal agents, but I noticed you're still on a waitlist and the "contact us" and "contact sales" buttons don’t seem to be clickable.
Just wanted to flag in case it's a bug. Excited to try it once access opens up.
Hi xinweihe, thanks for catching that. We are onboarding the waitlist with very fast turnaround. But, feel free to email me at haakam[at]agentmail[dot]cc
I’m curious why you’d make your email hard to copy paste when in this day and age won’t matter. Any basic AI agent can add your email to spam. Does it really help anymore?
Onboarding/signup started off great, but then you just drop in with no clarity on what to do next. A lot of actions possible and I'm unsure what to do first.
MCP's are great as another communication medium with these agents(we have an MCP server as well!)
The problem we are primarily solving is the scale at which you can provision inboxes to these agents in the first place. With Gmail there comes a lot of hoops and hurdles(its built for human usage) with their APi.
So when it comes to orchestrating inboxes for thousands, perhaps even hundreds of thousands of agents, thats where we would come in!
Happy to add some color here. SES and other APIs lack inboxes, email threading, attachment parsing, semantic search, structured data extraction, and more.
This is really interesting and I'm sure it has many useful applications - what I am most impressed by is the popovers in your dashboard, which show SDK examples. This is a brilliant UI idea (executed with great polish) and is the first time I'm seeing it.
Unfortunately I'm not a potential customer and don't have useful feedback on the market landscape - all I can add is that I really love your design. Also it seems like you all launched the new landing page while I was typing this comment a little past midnight, so kudos on the work ethic as well.
Thank you, all credit goes to my cofounder Michael! Your comment made our day
Keep in mind that default Gmail allows webhooks for any changes (email received but also changing labels, etc), for free using Gmail pubsub. I use it a lot because it's the only way of getting programmatic notifications from credit card purchases (turn on purchase alerts to all cards, send to Gmail, have a filter archive but capture the reception in webhooks. Parse with simple regex)
Super fast low latency very satisfying. Pubsub scales well and free :)
Totally hear you. We think Gmail works great for individuals. We are solving the challenges of scaling email to thousands of agents per tenant.
That workflow sounds amazing. How do you set that up? Got any code for it that we can look at?
Curious: how are you tackling abuse/spam at scale, especially as more agents start talking to each other? Also, any plans for plug-and-play integrations with popular agent frameworks, or is the focus purely on infra for now?
Congrats on shipping - looking forward to seeing your journey.
Thanks a lot! We're working on a lot of checks in place within our API for both the agents and email side, including things like spam filtering, verification, and protection against phishing or prompt injection. It's an interesting task at hand, solving both archaic and cutting-edge problems within the same product lol
We're also pretty interoperable as we're an API and compatible with any framework today. Plans to double down here however
I was previously considering building in this space but the infra around sending /receiving email for lots of addresses seemed like a major pain before getting to anything properly exciting, excited to see this! Would also encourage you to build good local dev/testing infra, dealing with email gets messy.
I believe truly useful AI assistants will use the same tools that humans prefer to use, rather than forcing us to come to it (in the same way truly intelligent embodied AI would use the same spaces/stairs/tools/doors as humans). Email, despite all its warts, still runs a lot of the world.
It has been a journey, in fact even harder than we were expecting. But can say it was well worth it after seeing the unlock for devs building in the email space.
Cool product. I see the need. Many vendors might look like they have similar capabilities on a powerpoint, but when you look one level deeper, they really don't. Eg, webhook notifications at 1 minute intervals with one big json of multiple emails, vs continuous/instant/single.
btw, would love to hear stories of you journey thus far. fwiw, I think you're really onto smtg!
Thanks! We've posted some vlogs on X, but I think we have some good content for engineering blogs too. Appreciate the support
This is perfect timing for me - was just thinking about how to do this. But pricing is a bit steep for a startup currently looking to prove the market. Would you consider a cheaper option (e.g. 1 free inbox, or maybe $20/mo for 5 agent inboxes and a more limited storage level)? I'm building something that I might consider this for, but I don't know how long my runway is before I get sustainable client revenue, so $100/month is a deep hole being burned in my personal pocket before I can prove my MVP out.
Thanks for the input sauwan - it means a lot. We're early, so this is by design. We have a generous free tier coming soon!
For now you can also use our playground at chat.agentmail.to
Hey sauwan, happy to help! Email me at haakam[at]agentmail[dot]cc
I do not have a use case for this _right now_. But I am a 100% sure I will have one pretty soon.
Email has become this massive, constant influx of information, that cannot be managed with just adding an AI agent to it. It takes so much more context knowledge to get right. None of the tools I have tried so far seem to solve this problem the way I would need it.
So sooner or later I might solve it for myself. And you guys will get a new customer.
Good luck, cowboys!
Nice, looking forward to hear about it!
i created this last summer
https://gpt.franzai.com
(test just email gpt@franzai.com)
sadly it never took off so it just became another abandoned side project
but still sometimes I use it ie do distill long emails or translate them without leaving the inbox - also the reminder and todo list feature is nice - whereby i mostly use the "remind me of this email next monday"
so my learnings for email agents: give them a sense of time and memory. its not only about that you write an email and send it but also when to write whom
Sorry for plugging in our product here but this comment seemed relevant. We are actually building something similar at mxgo[.]ai. Started exactly same way as you did, now working on a chrome extension with suggestions within inbox. Would love to connect and know your feedback.
Very cool! We’ve seen some neat personal assistants built with AgentMail as well
Why build with email now? Isn’t the world moving towards voice / live-chat paradigms?
One of the most important startup lessons to learn, in perpetuity, is not to underestimate email.
I learned this the hard way when I was running a startup 15 years ago (we used sign in with Twitter and didn't required people give us their email address) and it's still true today.
Email is almost universal, mostly free from gatekeepers and is an incredibly effective way to keep your product relevant in a way that doesn't depend on your users remembering to visit your site or open your app.
There are people out there who don't use email, but they tend to not be people who spend serious money on the kind of products most startups are building.
Agree that interfaces are moving in this direction. But humans and agents will always need a way to send/receive messages and notification asynchronously. Email is the most universal channel and we think it is here to stay.
This. I also think e-mail clients are a more natural interface for managing multiple async conversations/tasks with models/agents from different providers.
There's also nothing stopping this product from expanding to other interfaces/modalities like voice or sms.
Congratulations on your launch.
I would actually go as far as potentially considering email a distributed protocol for live-chat considering how quickly they are delivered [1]. I'm aware that is not how many people use them, but I believe that is more related to the interface and not the underlying technology. Somebody could probably built a live-chat messenger that looks like Teams or iMessage while actually just being an email client. Edit: This already exists [2].
[1] https://groups.io/email-provider-status [2] https://www.spikenow.com/features/conversational-email/
Great question - we get this input a lot. It really depends, while I'm a big believer of voice and API-driven design in the future, I think email's role remains but looks different. It's a sticky, universal protocol that serves as a great system of audit and record. Also think an agent is only as good as its context - an inbox serves almost as a personal gateway to the internet and early customer's use cases show different applications from agent-human connection to identity verification and authentication.
What a silly take. Email has been around for ages and it will continue to be around in perpetuity. It's still the medium of choice for certain types of interactions where a documented paper trail is important and you eg; need escalation, further review, etc. It's still also the choice for many companies and individuals.
> What a silly take
Can you please omit swipes like that from your HN comments? This is in the site guidelines: https://news.ycombinator.com/newsguidelines.html.
Your post would be just fine without that bit!
With this type of products, I feel like spamming nuisance will dramatically increase if mitigation doesn’t catch up
Don't worry we have checks in place to mitigate spam
What is the infrastructure tooling behind this product? I wanted to build this but it seemed like it is not a small startup project to build such big infra without riding on the existing email infra (which results in loss of the excitement to actually build the project itself and continue using the existing email infra by giants)
You can do this with SES on AWS or Mailgun. We use SES for this exact use case. Giving agents programmatic access to an email inbox and programmatically creating inboxes.
Yes you can use SES or Mailgun. But you would also need to build inboxes, email threading, attachment parsing, semantic search, structured data extraction, and more.
Is the '10.000.000+ emails processed' all from alpha/beta testers?
Yes we are live with several production workloads! The use cases include those described above.
Imagine the amount of spam this generates
Fair concern but that comes with any email product. We're a provider not a mass sending API like Resend, Mailgun, Sendgrid - that means our use cases primarily revolve around personalized, two-way conversations between reasoning agents and humans.
You mentioned one of your use case is outbound (can totally see this being perhaps your biggest opportunity): How are people using this for outbound? As a full-cycle AI sales agent?
Yes exactly, we have some cases where people built a fully autonomous AI SDR
I'm interested in trying agentmail for one of our internal agents, but I noticed you're still on a waitlist and the "contact us" and "contact sales" buttons don’t seem to be clickable.
Just wanted to flag in case it's a bug. Excited to try it once access opens up.
Hi xinweihe, thanks for catching that. We are onboarding the waitlist with very fast turnaround. But, feel free to email me at haakam[at]agentmail[dot]cc
I’m curious why you’d make your email hard to copy paste when in this day and age won’t matter. Any basic AI agent can add your email to spam. Does it really help anymore?
Haha totally fair point. Here's my email haakam@agentmail.cc go crazy
got it, will email you later, excited to try it out
Onboarding/signup started off great, but then you just drop in with no clarity on what to do next. A lot of actions possible and I'm unsure what to do first.
what confused you? happy to help - shoot me an email at adi(at)agentmail(dot)cc
I have been using Gmail connector for Deep Research in ChatGPT and it works like a charm.
For sending emails, I have been using Gmail MCPs
MCP's are great as another communication medium with these agents(we have an MCP server as well!)
The problem we are primarily solving is the scale at which you can provision inboxes to these agents in the first place. With Gmail there comes a lot of hoops and hurdles(its built for human usage) with their APi.
So when it comes to orchestrating inboxes for thousands, perhaps even hundreds of thousands of agents, thats where we would come in!
I see - is it just an SDK? How do I try this out
Yes, it;s as easy as calling an SDK. We have a waitlist and you can try our playground: https://chat.agentmail.to
Do you facilitate the domain registration or do users bring their own? And if you do facilitate it, do you retain ownership of it?
Users bring their own :) maybe this changes in the future though
Really cool stuff, keep it up.
thanks!!!
how much better is agentmail with rate limits and sending limits?
So much better lol. We have sky high rate limits that only serve to mitigate denial of service.
Let me know how long that’ll last. The low limits of other providers are there for a reason. That reason’s called spam.
We have checks in place to detect and reject spam. Don't think rate limits are an effective solution for that either.
Man, I've needed this! Brilliant!
thank you!!
Dejavu
What is the benefit of an AI email infra over using any other generic email api provider like SES, azure communication, sendgrid, mailchimp
The homepage has a feature comparison with Sendgrid. Sendgrid doesn't have email receiving, inboxes, attachment parsing.
Yes it does. As far as I recall, all major email providers handle inbound email. Sendgrid, Postmark, Mailgun, SparkPost, AWS SES.
(I don’t think this compromises the value of AgentMail, just clarifying what is supported elsewhere.)
Yes, some providers support receiving via webhooks (or some other notification), but lack the inbox infrastructure that Gmail and AgentMail offer.
good point. i guess really the comparison is SES not gmail
Happy to add some color here. SES and other APIs lack inboxes, email threading, attachment parsing, semantic search, structured data extraction, and more.