Live data from Hacker News

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

news.ycombinator.com

61–70 of 183 posts

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

#62

Earlier quoted context omitted.

Sure, bud. Cut me in on your 500K! My Show from 14 days ago: https://news.ycombinator.com/item?id=46629191 - hmm, why didn't it get into YC?

Just trying to provide you some helpful feedback. This reply comes off pretty rude, bitter, and immature. Probably not the look you want if you're trying to get funding.

Or we could just accept reality that there is no moat around this kind of stuff.

This seems like an afternoon or weekend project to build, particularly with the promises made about how much more efficient coding is with AI tools now.

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

#64
post #54

Looks like SES + api access, isn’t Amazon offering that already?

> Because we built the same inbox infrastructure as Gmail. Inboxes have threads, threads have messages, messages have attachments. You can search, label, filter, reply, forward. None of this comes out of the box with SES.

aws just gives you a low-level smtp + api service. we are the application layer they do not offer but your agents need to actually use email as first-class users.

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

#65
post #8
post #3

"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

This is just a graphic design gripe, but on:

https://www.agentmail.to/enterprise

the cutesy ASCII art is rendered in a proportional, not monospace, font, so it looks terrible.

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

#68
post #54

Looks like SES + api access, isn’t Amazon offering that already?

No offence, but this reads to me like the classic dropbox HN comment

The idea is pretty solid, automation platforms often provision a mailbox per flow for this reason, so it makes sense to make a generic service that can be used through MCP for agents

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

#69

Earlier quoted context omitted.

Network effects - agents need to meet humans where they already work. Would rather use something standard than bespoke.

And how long will humans and agents be communicating over email? We have strict rules for our customer service people not to respond to what seems to be a bot, since all the "agent" based communication we get is for conducting scams. It is never worthwhile to engage with or pursue. If we lose a sale or two, that's okay.

I think there will be bad actors in any field, and right now, a lot of agent-based outreach might fall into that bucket, so its rational to be initially skeptical.

The more interesting shift isnt whether humans will keep using email with agents, but whether agents can become distinguishable from noise. Historically, we ignored anonymous calls but we engaged with known vendors that had reputation, contracts, and consequences.

Once an agent has a persistent identity/a domain, trust becomes something that can be accumulated over time instead of being assumed per message.

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

#70
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)?
Post reply on HN