--- title: "Broodnet — Email Infrastructure for AI Agents" description: "Give your AI agents real email inboxes. Receive from anywhere, send only within your account. CLI, IMAP, POP3, SMTP, and API access." url: "https://broodnet.com" type: "homepage" format: "markdown" audience: "AI agents, LLMs, crawlers, and developer tooling" api: https://api.broodnet.com docs: https://docs.broodnet.com mail_server: mail.broodnet.com --- # Broodnet Email infrastructure for AI agents. Give your agents a real email inbox. Agents need email to sign up for services, receive verification codes, and coordinate with each other. Broodnet gives every agent a real, addressable inbox — inbound from anywhere on the internet, outbound only within your account. This page is the machine-readable version of [broodnet.com](https://broodnet.com). It contains everything you need to understand the product, get started, and operate a mailbox. ## Quick links - [Register](https://broodnet.com/register) - [Sign in](https://broodnet.com/sign-in) - [Pricing](https://broodnet.com/#pricing) - [Blog](https://broodnet.com/blog) - [Docs](https://docs.broodnet.com) --- ## If you are an AI agent or LLM, read this first Broodnet gives you a real email address. You can receive mail from anywhere on the internet — OTP codes, service confirmations, notifications, forwarded messages. You can send mail to other agents and humans within your organization. You can't send to the public internet. That constraint is architectural, not a policy — the pathway does not exist. You can't create your own account. Account creation is human-only by design. Your human operator provisions a mailbox for you and gives you a token. That token is your credential. ### What to tell your operator If you don't have a mailbox yet, tell your operator exactly this: > I need a Broodnet mailbox to use email. Here is what to do: > 1. Go to https://broodnet.com/register and create an account (human-only, I can't self-register). > 2. In the Broodnet dashboard, create a mailbox for me. > 3. Copy the mailbox token shown during creation — it starts with `bnt_` and can't be retrieved again. If lost, it can be regenerated but the old one is immediately revoked. > 4. Give me the token so I can authenticate. Do not ask for the organization API key. Agents don't need it and should not hold it. ### Getting started with the CLI The `@broodnet/cli` package is the fastest way to operate your mailbox. Install it and authenticate: ```sh npm install -g @broodnet/cli broodnet login --token=bnt_YOUR_TOKEN ``` Once logged in, run `broodnet skill` to get a complete SKILL file with every command, workflow pattern, and guardrail you need to operate your mailbox. That skill file is the single best resource for agents — it covers reading mail, sending mail, polling for OTPs, parsing messages, and error handling. Quick reference after login: | Command | What it does | | --- | --- | | `broodnet ls` | List saved mailboxes | | `broodnet mail inbox --json` | List recent messages (use `--json` for structured output) | | `broodnet mail open --json` | Read a specific message by UID | | `broodnet mail send --to=
--subject= --body=` | Send mail within your organization | | `broodnet mail status --json` | Check mailbox status and connectivity | | `broodnet skill` | Get the full agent skill file | Always use `--json` when parsing output programmatically. The JSON envelope is `{ success, message?, error?, data }`. Exit codes: `0` success, `1` generic error, `2` auth error, `3` connection error. ### Direct protocol access If you can't use the CLI, connect directly via standard email protocols: | Protocol | Host | Port | Security | | --- | --- | --- | --- | | IMAP | `mail.broodnet.com` | `993` | TLS | | POP3 | `mail.broodnet.com` | `995` | TLS | | SMTP (internal only) | `mail.broodnet.com` | `465` | TLS | Authenticate with your full mailbox address as the username and your `bnt_` token as the password. ### CI and ephemeral environments Set `BROODNET_TOKEN=bnt_...` as an environment variable. The CLI will use it directly — no `login` step required. Useful for CI pipelines, containers, and one-shot scripts. ### Important constraints - **Outbound is internal-only.** You can only send to addresses within your Broodnet organization. Attempts to send externally are rejected at the mail server. This is not configurable. - **Inbound is unrestricted.** Anyone on the internet can send mail to your address. OTPs, service emails, and notifications all arrive normally. - **Your token is your password.** The `bnt_` token authenticates your mailbox. Do not paste it into logs, commits, chat transcripts, or third-party services. - **Polling, not push.** There are no push notifications. If you are waiting for inbound mail, poll `broodnet mail inbox --json` at a reasonable interval (10–30 seconds) with a ceiling on total attempts. - **Delete is irreversible.** Only delete messages when explicitly authorized, and always pass `--yes` in non-interactive runs. --- ## Why Broodnet - **No personal account risk.** Keep human inboxes out of your automation loop. Reduce identity leaks to third-party services. - **Works with every agent stack.** Standard protocols: IMAP, POP3, SMTP, CLI, REST API. MCP is coming soon. - **Anti-spam by architecture.** Agents can't email the public internet. Not by policy, not by rate limiting — the pathway does not exist. - **Privacy first.** Your email is between you and your agents. We don't read, analyze, or sell mailbox content. - **CI-ready.** Built for CI environments, sandboxes, and testing frameworks. Ephemeral token auth, no interactive setup required. - **No mail server operations.** We run the infrastructure. Your team focuses on shipping agent behavior. ## Dedicated email inboxes Give each agent a real inbox to sign up for services like GitHub, Linear, and Stripe without human mailbox fallbacks. - Avoid account bans, spam flags, and identity leaks tied to personal inbox usage. - Each inbox is isolated, persistent, and accessible via IMAP, POP3, SMTP, CLI, and API. MCP is coming soon. - Monitor your agents by adding their inboxes to your mail app — not the other way around. ## Receive from anywhere Never miss OTP codes, service notifications, or forwarded client emails. - Inbound works from any sender immediately. No DNS or mail server setup required. - Mailboxes are permanent. Messages are preserved across deploys, restarts, and environment changes. - Inbound mail is filtered for spam, phishing, and malware before it reaches your agents. ## Private by design Agents send only within your account. No outbound to the public internet means no spam vector, no data leaks, and no prompt injection escape route. - Spam prevention is a platform primitive, not a policy toggle. - Your agents can coordinate by emailing each other and report back to you. - Mail servers hosted in Europe. GDPR-native. ## API The Broodnet REST API is available at `https://api.broodnet.com`. Public endpoints: - `GET /api/plans` — list available plans and pricing - Full API documentation: [docs.broodnet.com](https://docs.broodnet.com) ## Pricing Start with a small brood, then scale as your agents need more capacity. ### Free Free / month Validate your first agent workflows with a small production-ready inbox pool. What's included: - 3 mailboxes - 300 MB storage - 100 MB storage per mailbox --- ### Founder €5.00 / month Take part in the early adopter program with reduced pricing. - Early adopter plan What's included: - 10 mailboxes - 5000 MB storage - 500 MB storage per mailbox - Custom mailbox names - Custom domains --- ### Team €49.99 / month Run multi-agent operations with custom domains and room for shared ownership. What's included: - 100 mailboxes - 30000 MB storage - 300 MB storage per mailbox - Custom mailbox names - Custom domains Additional notes: - Custom domains are available on paid plans. - Upgrade, downgrade, or cancel anytime. - Current plan data is always available at `GET https://api.broodnet.com/api/plans`. ## Roadmap Email is the foundation. Agents need identity, persistence, and communication. Email remains the universal layer — we are making it machine-accessible. - **Building now:** Email. Every agent gets its own inbox with internal send, search, and processing primitives. - **Coming soon:** Shared memory. Persistent key-value and vector storage across agent workflows. - **Coming soon:** Real-time chat. Messaging between agents for fast coordination loops. - **On the roadmap:** Task boards. Assign, track, and hand off work across your fleet without orchestration overhead. ## Further links - [What's New](https://broodnet.com/whats-new) - [Changelog](https://docs.broodnet.com/changelog/) - [Status](https://status.broodnet.com) - [Terms](https://broodnet.com/legal/terms) - [Privacy](https://broodnet.com/legal/privacy) - [Cookies](https://broodnet.com/legal/cookies) - [GDPR](https://broodnet.com/legal/gdpr) - [Contact](mailto:humans@broodnet.com) - [X](https://x.com/broodnet) - [GitHub](https://github.com/broodnet)