Back to Home

An AgentMail alternative where people keep the keys

If you like the idea of AgentMail (an inbox per agent, over an API) but want tighter control over what agents send and read, Innmail is built for that. Same core shape, AgentMail-compatible request fields, and a policy layer that only people can override.

Request beta access

What you keep

Inbox per agent in one call, threads, drafts and scheduled sends, labels, attachments, pods, signed webhooks, custom domains with DKIM, a hosted MCP server and SDKs. Innmail accepts AgentMail-style fields such as username, domain, display_name and client_id, so most integrations move with a base URL and key change.

What you gain

Outbound policies that hold secrets, personal data and outside sends for approval, with no approve path for API keys. Inbound security that checks for spoofing, lookalike domains, pressure language and prompt injection and can hold mail before the agent reads it. A calendar per inbox, a file drive, verification-code extraction and a full audit log.

What you give up

IMAP and SMTP access to agent inboxes, WebSocket events, and a product that has been generally available longer. Innmail is a private beta with per-workspace limits.

Innmail and AgentMail at a glance

InnmailAgentMail
Inbox per agentOne API call creates a real inbox per agentYes, inboxes per agent over the API
Receiving and threadsReceives, stores and threads replies; read them over the APIYes, with threads, labels and drafts
Human approvalPolicies hold risky outbound mail for a person to approve; no key can approveNo built-in approval queue; the documented pattern is drafts plus scoped keys
Inbound securityChecks for spoofing, lookalike domains, pressure language and prompt injection; can hold mail before the agent reads itSpam and virus scanning; prompt-injection scanning and an inbound hold mode in beta
EventsSigned webhooks with retries, an SSE stream and a 30-day event logSvix-signed webhooks and WebSockets
MCP and SDKsMCP server, OpenAPI 3.1, SDKs for TypeScript, Python and Go, and a CLIHosted MCP server, SDKs and a CLI
Custom domainsYour own domain with DKIM, verified from the UI; unlimited inboxes on itCustom domains on paid plans
Free tierFree beta: 3 @innmail.app inboxes and 100 outside recipients a day per workspaceFree: 3 inboxes, 3,000 emails a month, 100 a day; paid from $20 a month

Based on each product's public description as of 2026. Check AgentMail's site for current details.

Frequently asked questions

How hard is the migration?

Usually small. Compare the OpenAPI spec at /api/v1/openapi.json with your current calls; inbox and message endpoints accept the familiar field names.

Can I run both during a switch?

Yes. Create agents in Innmail, point new flows at them, and keep old inboxes until their conversations finish.

What does it cost?

Nothing during the private beta: 3 @innmail.app inboxes and 100 outside recipients a day per workspace, unlimited inboxes on a domain you verify. Mail between your own agents is not counted.

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