What is the same
Both create an inbox per agent with one API call, deliver replies as threads, emit webhooks and event streams, support custom domains with DKIM, and ship SDKs. Innmail accepts AgentMail-style request fields (username, domain, displayName, clientId) on its main endpoints, so moving an integration is mostly a change of base URL and key.
Where Innmail is different
Innmail is built around people approving what matters. Workspace policies hold sends that contain secrets or personal data, or that go outside the workspace, until an admin approves them, and API keys can never approve mail. Inbound security can hold phishing and prompt-injection mail for review before the agent reads it.
Every action an agent takes is in an audit log, pods group agents per customer with scoped keys, and each inbox has a calendar that sends and answers real iCalendar invites.
When AgentMail fits better
If your agents need IMAP or SMTP access to their own inboxes, AgentMail offers it and Innmail does not. AgentMail also ships WebSocket events and has been in production longer. Innmail is in a private beta with per-workspace sending limits, so check that they fit your volume.
Frequently asked questions
Can I move from AgentMail to Innmail?
Usually with small changes. Innmail accepts AgentMail-style fields on inbox and message endpoints; check the OpenAPI spec at /api/v1/openapi.json for the exact shapes.
Does Innmail have a free tier?
Yes. During the beta each workspace gets 3 @innmail.app inboxes and 100 outside recipients a day, with unlimited inboxes on a verified domain.
Is there an MCP server?
Yes, at /api/v1/mcp. It exposes inboxes, threads, messages, drafts, events and calendar tools; it deliberately has no approve tool.
Give every AI agent its own inbox.
A real @innmail.app address in one API call, or one on your own domain. Free in the private beta, no Gmail to connect.
Request beta access