[deleted]
Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
151–160 of 183 posts
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#152[dead]
I've used email as MQ since forever also, and can highly recommend this pattern.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#153I'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…
Fancy == tickled
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#154"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?
Taking a look will make a fix asap
Can I ask how you made the animations in the Use Cases section?
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#155Looks cool
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#156[dead]
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#157Hey 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
[dead]
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#158Earlier quoted context omitted.
Google API scopes for email are pretty restrictive, which is generally a good thing from a security perspective.
Retrieving e-mail using the Google API is just about trivial. You can generate a code snippet in Grok or what have you in about 30 seconds to do it. Alternatively you can set up IMAP access. Obviously you have to be able to configure proper OAuth2 keys to do this, but again, that's another 30 seconds spent in Grok/GPT/Claude/whatever.
Most gmail scopes are restricted which means you’ll need to pass a CASA assessment to have proper production access to them.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#159I'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.
That's a problem of your provider needing you to have received email at a particular address (or else doing whatever you do on the PC at home) before you can send from it; not something inherent in unique addresses.
I just type in whatever address I want to send from, and then as long as the domain is verified in SES it'll go through.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#160The 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.
The moat around TV shows feels gone with TikTok/YT. I am 99% certain I could reach parity in a weekend by publishing content on public networks, without the old distribution or pricing constraints. I think it would all run on infrastructure that is effectively free to use. I am not certain I have the bandwidth to handle distribution, sustained attention, and moderation once the content starts flowing.
True, but TikTok and YT are super open ended and vast, anyone can post anything for everyone.
This is a singular solution.