Agents shouldn't be the first-class users of the internet! We are creating a future we wouldn't want to live in.
Show HN: Agent.email – sign up via curl, claim with a human OTP
81–90 of 127 posts
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#82Earlier quoted context omitted.
This was likely a free tier user. We do this intentionally and don't allow free users to send from custom domains, so you can have a easier time identifying LLM emails. In this case, it seemed like it worked :)
And for paid users the receivers don’t need to have an easier time identifying the LLM email? What kind of reasoning is that?
A lot of people believe that spam issue would be largely solved if each email costed 0.001$
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#83I'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?
This is like saying - 'I don't understand why anybody would ever buy a pizza from a store. All you have to do is get some flour, water, tomato sauce, cheese, mix the flour and water together, whip the dough, add tomato sauce, put cheese on top of it, cook it for 20 minutes, and then serve it.' So __much__ value is in the fact things are easy. Money is __not__ the most valuable thing in the world.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#84Earlier quoted context omitted.
yep we're going to have a footer linked to our website, which should allow people to see that we are an email service for agents. thanks!
Can you not just make the text more descriptive? „Sent by a generative AI model“ or something? Nobody is going to click a link in a spam email.
Chances are more people would identify the service as something to block or report for spam if the text were more descriptive, so he's counting on people not clicking the link in the footer but at least he can claim it's there, even if it's ineffectual.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#85Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#86Earlier quoted context omitted.
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.
Get a domain, get webhosting that includes an email server, now you can generate unlimited emails from whichever program you want. And the email reputation will probably be the same as with this service.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#87That being said -- my agents only email each other and me! AgentMail is an OK start with the human agent requirement, but consider that is a whitelist of a single email. The feature for AgentMail should be: we let your agent sign up easily for an email, and it has a very limited list of addresses and domains it can send outgoing email. This is very unlike normal email! I actually can't think of a single (human-facing) provider that will enable me to blacklist domains at the mailserver level to prevent outgoing mail from going to forbidden destinations.
Allowing a bot/agent to send email to any domain, with only a tagline to indicate the bot, is spam. But -- just like sandboxing the network and CLI commands available to the agent on my Mac Mini -- sandboxing an agent's email would just be the smart thing to do.
Pivot to an agent email sandbox and you will get plenty of the right kinds of customers, who won't ruin your mailserver reputation. Provide some easy agent-friendly whitelists out-of-the-box like same-custom-domain, and a similar approval system for new addresses/domains built on your OTP setup.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#88I 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…
It's less work to signup a second email address for agent use than to signup with you, then signup a second email address.
After all, it's not like each agent needs their own email.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#89This service is doomed because it will immediately be taken over by automated spam.
Re: Show HN: Agent.email – sign up via curl, claim with a human OTP
#90Earlier quoted context omitted.
Get a domain, get webhosting that includes an email server, now you can generate unlimited emails from whichever program you want. And the email reputation will probably be the same as with this service.
Any hosting services with email you'd recommend? Are you talking about a service like Fastmail or something?