# Botmail vs InboxAPI: two free inboxes your agent sets up itself InboxAPI and Botmail are the two closest products in agent email. Both are free to start, both make the agent solve a small proof-of-work instead of asking a developer for an API key, and both give the agent a real address that sends and receives. The differences are in what happens next: who picks the address, whether a human approves it, how the agent connects, and who it can email. ## The main difference **InboxAPI is zero-touch.** You install the CLI and add it to your MCP client. The first time the agent uses it, an account is created automatically with a generated address like `bright-fuzzy-owl@.inboxapi.ai`. No human is involved unless you later link your email for account recovery. **Botmail puts a human in the loop once.** The agent picks its own name and claims `ada@botmail.pro`, then emails you an approval link. You sign in with GitHub, Google or Apple and approve it with one click. Until then the mailbox can't send. ```sh # InboxAPI npm install -g @inboxapi/cli@latest claude mcp add inboxapi inboxapi # Botmail npx botmail claim ada --human you@example.com ``` ## Side by side | | Botmail | InboxAPI | | --- | --- | --- | | Address | A name the agent chooses, such as `ada@botmail.pro` | Generated, such as `bright-fuzzy-owl@.inboxapi.ai` | | Signup | Proof-of-work, then a human approves | Proof-of-work, automatic | | Human owner | Required before the mailbox can send | Optional, through `verify_owner`, mainly for account recovery | | External recipients | No fixed list; new free accounts can reach 25 new recipients and send 100 messages a day, rising with trust to 1,000 sends | 5 addressbook slots; the least recently used is replaced after 5 days of inactivity | | Agent-to-agent mail | Counts like any other mail | Unlimited between InboxAPI addresses | | How the agent connects | Hosted MCP at `https://botmail.pro/mcp` (OAuth or API key), REST with an OpenAPI spec, CLI | MCP tools through its local CLI | | Drafts for human review | Yes, with a review link | No | | Webhooks and waiting | Webhooks, long-poll, `wait_for_mail` | MCP tools to fetch and search | | Price | Free; paid from $5/month | Free; paid plans "coming soon" | InboxAPI details are from its [home page and FAQ](https://inboxapi.ai/), [limits page](https://inboxapi.ai/limits/) and [tools reference](https://inboxapi.ai/tools/), checked in October 2026. ## Where they differ in practice **The five-slot rule.** InboxAPI's addressbook allows 5 external recipients per account. A sixth address only gets a slot once one of the five has gone 5 days without use. That's fine for an agent that reports to you and one or two services. It's tight for an agent that emails vendors, schedules meetings or answers a support queue. Botmail limits how many *new* people a free account can reach each day instead, starting at 25. **Deliverability.** InboxAPI says each agent gets a brand-new subdomain, and that early mail may land in spam until the agent builds a reputation. Botmail addresses all live on `botmail.pro`. **Prompt injection.** InboxAPI does more here and deserves credit for it. Every email carries a trust level (`trusted`, `agent`, `unverified`, `suspicious`), untrusted text is "datamarked" with marker characters, and outbound mail that contains auth tokens is rejected. Botmail tells agents to treat email as data, keeps the mailbox limited to mail sent to the agent, and checks first-contact sends for spam and phishing. **Connecting other tools.** InboxAPI's docs cover MCP through its CLI. Botmail also has a documented REST API, webhooks and a CLI that can block until a code arrives: ```sh botmail wait --from github.com --extract code --timeout 5m ``` ## When InboxAPI is the better choice - you want no human step at all, and a random address is fine - your agents mostly email each other, where InboxAPI has no recipient limit - the agent only needs to reach a handful of outside addresses - you value built-in trust labels and datamarking on every message ## When Botmail is the better choice - the agent should have a name people recognize, chosen at claim time - you want a person to approve each address and, when you choose, each draft - the agent emails more than five outside people - you need REST, webhooks or a hosted MCP server that any client can reach - you want a paid plan today, from $5 a month Botmail isn't affiliated with InboxAPI. ## Try Botmail Paste this into your agent: ```text Read https://botmail.pro/skill.md and claim a mailbox for yourself. Send the invite to my email, then wait for me to approve it. ``` Or use the [CLI](https://botmail.pro/cli), or connect any client to the [email MCP server](https://botmail.pro/guides/email-mcp-server). ## Questions ### What is the difference between Botmail and InboxAPI? Both are free and let the agent sign itself up with a proof-of-work. InboxAPI creates a random address automatically with no human step. Botmail lets the agent choose its name and requires a human to approve the address before it can send. ### How many people can an InboxAPI agent email? InboxAPI gives each account 5 external addressbook slots, and a slot is only freed after 5 days without use. Mail between InboxAPI addresses doesn't count. Botmail free accounts can email 25 new recipients a day, rising with trust. ### Does InboxAPI have paid plans? Not yet. In October 2026 InboxAPI was free with paid plans listed as coming soon. Botmail has a free plan and paid plans from $5 a month. --- Source: https://botmail.pro/compare/inboxapi Agent instructions: https://botmail.pro/skill.md All guides: https://botmail.pro/llms.txt