mailhook

from zero to inbox in 2 API calls. no signup form. just curl. → create inbox → receive email as JSON → self-destructs when you're done programmable temp inboxes for AI agents. mailhook.co

@motatclankspace @ClawiAi exactly. the real question is how — polling IMAP on a shared Gmail? or a dedicated inbox per task with emails pushed as JSON. one creates race conditions at scale, the other doesn't.

@ClawiAi just give your agent its own email address, why wouldn't you?

Your AI agent can’t create accounts without email. Now it can. Zero setup inbox.

@realdancro the difference is subtle but real. existing email APIs are for sending. agents need the opposite — spin up an inbox, receive the verification email, parse the OTP, move on. can't do that with Sendgrid. it's the receive side that never got an API.

I see the new 'saas hack' is just creating everything that already exists but for agents. email for agents. phone numbers for agents. life coach for agents. You name it. All of this shit exists, and has an API... I'm so foncused.

@pedrorhumb the 82% isn't even a hard technical problem. email verification just needs the agent to have its own inbox. phone checks are harder. "contact sales" is unsolvable lol. the gap is infrastructure, not intelligence.

Saturday morning number that surprised me: only 18% of the APIs I've tested let an AI agent sign up, get credentials, and make its first call without a human clicking anything. The other 82%? Manual signup forms, email verification, phone checks, or "contact sales." That's the gap.

@bdleasure the Gmail sharing thing is the real risk nobody talks about. one prompt injection and your agent is forwarding password resets somewhere you don't control. throwaway inboxes per session fix this. isolated, no access to personal mail, clean JSON instead of raw MIME.

Why can your AI agent write a contract but can't sign up for Slack? I was digging into agent identity and something clicked. The internet still works like 1999 — email verification is how you prove you're real. Thread:

@ShipAloneCEO simplest fix: let agents get an API key on first call. no signup form, no email loop. one POST → key in the response. done. captchas and tutorials are harder, but the email wall is a solved problem if you stop requiring human-style onboarding.

Your onboarding flow was designed for a human clicking buttons What happens when an AI agent tries to sign up for your product instead? - captchas block it - email verification loops it - interactive tutorials confuse it The first products that nail agent onboarding will have a massive edge.