Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Agent.email – sign up via curl, claim with a human OTP

news.ycombinator.com

Post reply on HN
Print view View original

111–120 of 127 posts

Re: Show HN: Agent.email – sign up via curl, claim with a human OTP

#111

Post by brandonwindson »

skinfaxi wrote: post #106
replwoacause wrote: post #84

Earlier quoted context omitted.

He's obviously trying to avoid having to do this, so linking out to the website is the "hey look we're doing the right thing" when really they aren't. 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.

This service will be marked as spam anyway, it's only a matter of time.

[dead]

Re: Show HN: Agent.email – sign up via curl, claim with a human OTP

#112

Post by DigDev »

FailMore wrote: post #9

I like it. I am building something very agent-use focused ( https://sdocs.dev ) and I’ve been thinking of introducing a /agent-evaluation page, which an agent can curl to then discuss with their user if SmallDocs is right for them. I really like the agent action to email flow. I’m introducing user accounts + subscriptions soon and think I’ll use that.

[dead]

Re: Show HN: Agent.email – sign up via curl, claim with a human OTP

#114

Post by TurdF3rguson »

xigoi wrote: post #102
TurdF3rguson wrote: post #72

Earlier quoted context omitted.

> An inbox to receive mail seems good and valuable. The only receiving mail applications that come to mind are bots registering for accounts. The point of verifying email is to prove you're not a bot.

> The point of verifying email is to prove you're not a bot. I thougt it was primarily to verify that the address is actually yours, so they don’t unknowingly spam someone else and can reach you with important information such as pricing changes.

No, there's a separate way to gate that which is a captcha on the signup. If they pass the captcha that email gets sent whether it's really the right person's or not. Then if it's not, the account just never gets verified.

Re: Show HN: Agent.email – sign up via curl, claim with a human OTP

#115

Post by dgellow »

sanjayparekh wrote: post #29
dgellow wrote: post #27

Earlier quoted context omitted.

Now that I think about it I’m pretty sure that’s illegal in Germany under UWG §7 (which is insanely strict, to a fault, but is helpful here). And maybe in other parts of the EU under ePrivacy laws

I might need to move to Germany.

Long shot, but if you do come here, even just for visiting, send me an email, always happy to connect :)

Re: Show HN: Agent.email – sign up via curl, claim with a human OTP

#117

Post by morpheuskafka »

HPMOR wrote: post #61
morpheuskafka wrote: post #58

I'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.

How is it easier when you still have to human-approve the creation interactively, and we have no idea how long this service will be around or if pricing will change (which could result in being locked out of accounts agents created and later used for something important / signed up for an API used in your code)?

Re: Show HN: Agent.email – sign up via curl, claim with a human OTP

#119

Post by kurtoid »

adisingh13 wrote: post #38
mike-cardwell wrote: post #30

I 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…

Make sure it adds a header too
Post reply on HN