Broodnet is dedicated email infrastructure for AI agents, providing each agent with a real inbox that receives inbound mail from any sender and restricts outbound sending by default to prevent spam.
What is Broodnet?
Broodnet gives AI agents persistent, real email addresses to sign up for services, receive verification codes, and coordinate with other agents. It eliminates the need for personal human inboxes or self-hosted mail servers by provisioning isolated mailboxes accessible via CLI, IMAP, POP3, SMTP, and soon MCP. Broodnet is built and operated by the Broodnet team (broodnet.com). Inbound mail works immediately with no DNS setup; outbound to external recipients requires consent or a recent inbound thread.
Key Features
- Real, permanent mailboxes — Each agent gets a dedicated inbox that persists across deploys, restarts, and environment changes. Messages are preserved indefinitely (subject to storage limits).
- Inbound from anywhere — Receive email from any sender without configuring DNS or mail servers. Inbound filtering blocks spam, phishing, and malware before delivery.
- Outbound safety by default — Agents cannot email strangers. External sending requires recipient consent or a reply within a time-bounded window, keeping strangers out of the blast radius.
- Multi-protocol access — Use the CLI (
@broodnet/cli) to read and send mail, or connect via IMAP, POP3, or SMTP. MCP server is on the roadmap.
- Privacy-first design — Broodnet does not read, analyze, or sell mailbox content. Servers are hosted in Europe (GDPR-native).
- CI-ready — Built for automated testing, CI pipelines, and sandbox environments. No mail server operations burden on your team.
- Provision multiple mailboxes — Create individual inboxes for each agent, isolated from human accounts. Supports custom mailbox names and custom domains on paid plans.
Who is it for?
- AI agent developers — Give each agent a real inbox to sign up for services like GitHub, Linear, or Stripe and receive OTPs or notifications without using personal email addresses.
- Platform teams running agent fleets — Provision isolated mailboxes for dozens or hundreds of agents, avoid account bans and identity leaks tied to shared human inboxes.
- QA and CI engineers — Use Broodnet in automated test environments to verify email-dependent flows (e.g., verification codes, billing alerts) without managing a local mail server.
What can you do with Broodnet?
- Agent onboarding and verification — Agents receive OTPs, account activation links, and service notifications in their own inbox, keeping human email out of the loop.
- Inter-agent coordination — Agents can email each other within your account to share status, hand off tasks, or report results — no external infrastructure needed.
- CI test fixture — Automate email receipt in test suites: use the CLI to poll inboxes, parse verification codes, and assert delivery without human intervention.
How does Broodnet work?
- Install the CLI (
npm install -g @broodnet/cli) and authenticate with a token.
- Provision mailboxes via the dashboard or CLI (Free plan gives 3 mailboxes).
- Agents read and send mail through the CLI (
broodnet mail inbox, broodnet mail open), or via IMAP/POP3/SMTP in your framework.
- Inbound mail is filtered for abuse and delivered instantly. Outbound mail is restricted unless the recipient has consented or replied to a recent thread.
