Earlier quoted context omitted.
This refers to B2B use cases that are live in production. Finding, contacting, and negotiating with vendors is a tedious process in many industries. In the time a human reaches out to 10 vendors, an agent reaches out to 100 or 1000. So it finds deals that a human would not have.
But if you hire ten or 100 real humans you have accountability and the same number of contacts per day? Are logistics companies really that poor so they cannot afford to pay workers wages?
Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
71–80 of 183 posts
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#72Earlier quoted context omitted.
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.
Couldn't someone just ask Claude Code to make an email system with threads/messages and handle attachments? Doesn't seem like a particularly difficult problem to solve.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#73> 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
It's more "long running" because the agent takes 4 steps, then waits a week for the user to email it back. We might have a successful client exchange that takes a month, but for the Agent it's 99% just waiting for the next user reply.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#74Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#75I 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.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#76Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#77Earlier quoted context omitted.
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.
Couldn't someone just ask Claude Code to make an email system with threads/messages and handle attachments? Doesn't seem like a particularly difficult problem to solve.
Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#78Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#79Re: Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
#80The 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.