Why agents need their own inbox
Agents that sign up for tools, book meetings, chase invoices or answer customers need an address of their own. Borrowing a person's Gmail mixes the agent's mail with theirs, needs broad Google permissions, and makes it hard to see what the agent actually did.
With Innmail each agent has a separate inbox and a separate log. You can pause it, cap it, read everything it sent and received, and revoke its key without touching anyone's mailbox.
How it works
Sign in, create an API key, and call POST /api/v1/inboxes with a username. The agent gets an address like scheduler@innmail.app straight away. Send with POST /inboxes/{id}/messages; replies come back threaded and arrive as message.received events.
When you want branded addresses, add a domain such as agents.yourco.com under Domains. Innmail generates the DNS records (verification, DKIM and MX), checks them, and from then on agents can send and receive as that domain.
Built so people stay in control
Workspace policies catch secrets, personal data and blocked phrases, and can require approval for anything going outside the workspace. Held messages wait in Approvals for a person; no API key, including the agent's own, can approve mail.
Inbound mail is checked for spoofing, lookalike domains, pressure language and prompt injection, and can be held before the agent reads it. Every action is in the audit log.
What you get
Threads, drafts and scheduled sends, reply-all and forward, attachments and a per-inbox file drive, labels and search, verification-code extraction, a calendar per inbox with iCalendar invites, allow and block lists, signed webhooks with retries, an SSE event stream, an OpenAPI 3.1 spec, an MCP server, and TypeScript, Python and Go SDKs plus a CLI.
Frequently asked questions
Do I need to connect Gmail?
No. Agent inboxes live on @innmail.app or on your own verified domain. Sign-in with Google shares only your name and email address.
What does it cost?
Free during the beta: 3 @innmail.app inboxes and 100 outside recipients a day per workspace, and unlimited inboxes on a domain you verify. Mail between your own agents is not counted.
Can my agent use my company domain?
Yes. Add a subdomain such as agents.yourco.com, publish the records Innmail shows, and verify. A subdomain leaves your team's existing mail untouched.
Which agent frameworks work with it?
Anything that can make an HTTP request. There is an MCP server for Claude and other MCP clients, plus SDKs for TypeScript, Python and Go.
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