Introduction

Broodnet is managed email infrastructure for AI agents. It provisions dedicated mailboxes that can receive mail from the entire internet and send mail within your organization.

The problem

AI agents need email. Not just the ability to send a transactional notification — real, addressable mailboxes that can receive OTPs, service confirmations, replies, and structured payloads from external systems.

Existing email APIs (the kind used to send password resets or marketing campaigns) are one-directional. They can send mail on your behalf, but they don’t give your agents a real inbox, a real address, or a way to receive replies. They’re delivery services, not mailboxes.

Broodnet is the mailbox layer. Every agent gets its own email address backed by real mail server infrastructure. Inbound works from day one. Outbound is intentionally constrained.

How it works

Broodnet wraps full mail server infrastructure — message routing, delivery, inbound processing — behind straightforward interfaces.

flowchart TD
    Human(["👤 Humans"])
    Agent(["🤖 Agents"])
    Internet(["🌐 Internet"])

    subgraph bn["Broodnet"]
        direction TB
        App["🖥️ Dashboard"]
        API["⚡ REST API"]
        CLI["💻 CLI"]
        MCP["🔌 MCP Server"]
        MS["📬 Mail Server\nIMAP · POP3 · SMTP"]
    end

    Human --> App
    Human --> CLI
    Agent --> CLI
    Agent --> MCP

    App -->|manage| API
    CLI -->|manage| API
    MCP -->|manage| API
    API <-->|sync| MS
    MS <-->|email| Internet

You provision a mailbox, get an address, and start sending and receiving. No mail server to run, no DNS records to manage, no deliverability tuning.

CLI

# Check your inbox
broodnet mail inbox

# Open a message by UID
broodnet mail open 1042

REST API

# List your mailboxes
curl https://api.broodnet.com/api/mailboxes \
  -H "x-organization-key: brn_your_key_here"

# Provision a new mailbox
curl -X POST https://api.broodnet.com/api/mailboxes \
  -H "x-organization-key: brn_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "localPart": "myagent" }'

CLI

Terminal interface for the same operations. Useful for automation, agent workflows, and shell scripts that need structured output.

REST API

Provision mailboxes, send and read mail, manage organizations and members. The primary interface for integrations and scripts.

Outbound is internal-only

Outbound email from Broodnet mailboxes can only be delivered to addresses within the same organization. This constraint is enforced at the mail server level — it applies to every interface (API, CLI, MCP, SMTP) and cannot be bypassed.

Anti-spam by architecture

Broodnet is built for AI-to-AI and AI-to-operator communication. It is not a platform for cold outreach, marketing, or bulk sending. If your use case requires sending to arbitrary external recipients, Broodnet is not the right tool.

flowchart TD
    Internet(["🌐 Internet"])
    You(["👤 You"])
    Agent(["🤖 Your Agent"])

    subgraph bn["Broodnet"]
        IN["📥 Inbox"]
        OUT["📤 Outbox"]
    end

    Internet -->|inbound| IN
    You -->|inbound| IN
    IN -->|"IMAP · POP3 · REST · CLI"| Agent
    Agent -->|"SMTP · REST · CLI"| OUT
    OUT -.->|org members only| You

Where things stand

Early development

Core functionality is working — provisioning mailboxes, sending and receiving mail via API and CLI. MCP integration is in progress. We’re prioritizing a solid foundation before expanding the feature surface.

The Changelog tracks what’s shipped.