Show HN: AgentMailr – dedicated email inboxes for AI agents

7 points by kumardeepanshu 11 hours ago

I kept running into the same problem while building AI agents: every agent that needs email ends up sharing my personal inbox or a single company domain. That breaks attribution, creates deliverability risk, and makes it impossible to test sender identities per agent.

So I built AgentMailr. You call an API to create an inbox, your agent gets a unique email address, and replies route back to that specific agent. Works for both inbound (OTP parsing, reply routing) and outbound (cold email, notifications).

Bring your own domain is supported so emails come from your domain, not ours. REST API and MCP server are live. Node/Python SDKs are in progress.

Happy to answer questions about the architecture or how I'm handling multi-agent routing.

kwstx - 11 hours ago

Interesting problem I’ve run into the same thing when building agents that need their own identity for email workflows.

Quick question: are these real mailboxes (IMAP/SMTP) or more of an API abstraction over email for agents? Also curious how you handle deliverability and domain reputation if many agents are sending from the same infrastructure. Feels like something like this could become part of the identity layer for agents, not just email. Nice idea.

kumardeepanshu - an hour ago

these are real mail box, you can send and receive the email at once.

TZubiri - 3 hours ago

Why does the agent need an API different than the ones we have for humans? (SMTP, IMAP/POP, AWS SES, etc..)

heyarviind2 - 6 hours ago

github link in the footer doesnt work