Seems like you're using email as a long lived task queue/journal system. Definitely optimizing for customer recognition/novelty over technical merits. Best of luck!
Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
131–140 of 183 posts
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#132The 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.
This is not true. And it's easy to disprove.
Most SaaS pre-AI had an open source alternative. Most people didn't use them not because the open source alternative lack some features, it was because mainteinance was hard. It's way easier to pay a small monthly fee and forget about it.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#133Very 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.
i'd love to know more about these use cases. open to chatting sometime? adi@agentmail.cc is my email
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#134I'm 100% for this, but I think you can go even more granular than "gives agents their own inboxes". Thanks to Action Mailbox in Rails[1], I give all my records email addresses. Eg let ecommerce "order" records accept forwarded emails that are pinned as comments. It opens you up for doing things like forwarding a purchase order and having the PO number pulled out and attached to an order, or forwarding tracking inform…
The only problem I have experienced few times with those unique email addresses is, sometimes they/utilities ask me to email from my official email address, and my setup is a catch-all, so I have to log in my pc at home, set up that address, send email.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#135Earlier quoted context omitted.
> The moat for SaaS is gone. What does this even mean? I could spend $1,000s on tokens asking an agent to build (some semblance of) Sentry, or New Relic, but why would I bother? I have real work to do in the near-term, and I'm happy to pay for services that help me do it.
All the hard work is always chasing down edge cases, scaling, operational issues and other things that don't show up the user-exposed features. And talking about features, the innovation in coming up with them, or iterating on making them work with real customer experience is a ton of value, even if copying the ideas that work later is much easier - which is why I generally prefer betting on an innovator with just of…
and a lot of those features only really matter if you are serving a lot of customers. PHP is just fine if your serving 10-20 internal customers.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#136Earlier quoted context omitted.
Once vendors are getting AI spam sent to 1,000 of them and their competitors, they will stop responding and find other sales channels. This won't be sustainable.
Unless they have agents reading those emails and responding ...
wait till you find about B2B procurement marketplaces... ya'll this stuff exists
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#137congrats, I have been following you guys along for a while on LinkedIn. Good Luck
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#138i think they figured this out in the unix era
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#139[dead]
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#140If the agent is sending emails to people you don’t know (“sourcing quotes”) wouldn’t this be a violation of Amazon SES (and all other email providers) terms? Dont they expect permission from the people you are contacting? How’d you get around that?