It looks interesting as a hackathon project. I might be short sighted but how does this is YC S25 level good?
This looks like one of the easiest way to get your domain blacklisted in all the email providers.
Show HN: Agent.email – sign up via curl, claim with a human OTP
51–60 of 127 posts
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#52> We give AI agents their own email inboxes.
An inbox to receive mail seems good and valuable.
But I'm seeing that your service is also for sending e-mail.
Having a domain oriented toward AI e-mail sending feels like a fast path straight to spam block lists.
However good your intentions are, this will be used for AI spam. People hate AI spam. They will press the report spam button.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#53> The internet was made for humans exclusively, designed to keep machines out by default.
This feels like a wrong assumption. Internet was not intended for humans explicitly. If anything browsers were the explicit medium made to allow the humans to interact with internet in safe manner.
> Every signup flow assumes a browser, a person reading a page, and clicking a confirmation link. Unless agents can't do that, they can't be first class users of the internet.
This again feels like a misconception. The systems just work with an identity verified by credentials, it doesn't matter if its a program or program prompted by a human that uses it
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#54Any automation-friendly email hosting is going to have a serious spam problem, and therefore a blacklisting problem.
I suggest taking a look at what providers like Sendgrid, Mailchimp, etc are doing to prevent abuse.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#55Why is this even funded?
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#56> We give AI agents their own email inboxes. An inbox to receive mail seems good and valuable. But I'm seeing that your service is also for sending e-mail. Having a domain oriented toward AI e-mail sending feels like a fast path straight to spam block lists. However good your intentions are, this will be used for AI spam. People hate AI spam. They will press the report spam button.
maybe if they charge $, then there's a hashcash like PoW deterrent
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#57> The internet was made for humans exclusively, designed to keep machines out by default. This feels like a wrong assumption. Internet was not intended for humans explicitly. If anything browsers were the explicit medium made to allow the humans to interact with internet in safe manner. > Every signup flow assumes a browser, a person reading a page, and clicking a confirmation link. Unless agents can't do that, they…
As somebody who spent a lot of time trying to get an agent to register an email address, their assumptions were correct. It is a PITA.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#58I'm just not seeing why anyone would buy a paid plan for this when they could buy a domain for For a home user not even willing to do/pay for that, do they really need a whole API for making inboxes? Couldn't they just set up a second Gmail for LLMs and then put the password in their agent's memory?
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#59[dead]
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#60I received this email the other day: From: Kushal Date: Mon, 18 May 2026 05:03:11 +0000 Saw your question on the Agent Vault thread about websocket-frame auth (Home Assistant) and the worry about the model reflecting the bearer token back into its own context. chrome-relay's answer is structurally different: the credential never enters the agent's context because the agent never touches it — the HA session lives in y…
Appreciate the concern Mike, and I actually read your email complaining, which helped us ship this next feature. We have a "sent via AgentMail" footer being added soon to outbound emails to identify emails coming from LLM's. We also are working on adding more robust checks and LLM-based filtering to prevent messages which contain spam or outbound-like copy. Re; AgentMail next to Claude, we're working on stateful inbo…
"sent via AgentMail" - removable by a higher plan later on