Been building agents that need to sign up for services, verify email addresses, and extract OTPs. The missing piece in most agent stacks is a real email identity per agent.Lumbox gives each agent its own inbox. The main thing that makes it different from rolling your own:GET /otp is a long-poll endpoint that blocks until the OTP arrives. Your agent just calls it and waits. No polling loop, no...
Been building an AI agent pipeline for outbound email and ran into an infrastructure problem that I haven't seen discussed much.When you run multiple agents doing outreach in parallel, the default setup most people land on is having all agents share one email domain and sending identity. This breaks in a few ways at scale:1. Reputation isolation: if one agent gets flagged for aggressive sending...
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...
a few things people usually ask:
- yes it handles plain text, HTML, and subject line extraction. the parser picks the most likely OTP code across all three so you're not locked to a specific email format
- you can pass a `from` filter to only match emails from a specific sender domain, which helps avoid picking up the wrong code if your agent has multiple services sending to the same inbox
- the long-polling approach means your agent just blocks on one call instead of polling. no webhook server to maintain, no correlation logic to wire up
also wanted to mention - OTP/2FA is just the first thing we're solving. we're building out bulk email sending and marketing email support as well, so agents can do the full email loop: receive OTPs, send outreach at scale, run campaigns. the goal is to be the complete email layer for AI agents.
if you're running agents at scale and hitting edge cases, would love to hear what you're running into.
Been building agentic workflows and kept running into the same problem: 2FA walls.When an agent tries to sign up or log into a service that sends an email OTP, the options are terrible. You either dump the full email HTML into your LLM context (slow, expensive, fragile) or you write a polling loop that constantly checks for new emails.AgentMailr solves this with long-polling. You create a named...