Back to Home

An email inbox API built for agents

Most email APIs were built to send. Agents also need to receive: a reply, a verification code, an invoice, a meeting invite. Innmail gives each agent one persistent address that does both, with threads kept in order and every event delivered to your code.

Request beta access

One call, one address

POST /api/v1/inboxes with a username returns an address such as scheduler@innmail.app. The agent sends with POST /inboxes/{id}/messages, including reply, reply-all and forward with attachments, custom X-* headers and an Idempotency-Key so retries never double-send.

Replies come back as message.received events and land in the same thread, matched by headers with a subject and participant fallback. Each message carries extractedText, the reply without quoted history, so the agent reads only what is new.

Everything an inbox needs

Drafts and scheduled sends, labels including read, unread and trash, batch get and update, full-text search, raw RFC 822 when you need it, attachment download and a per-inbox file drive. Verification codes are extracted for you, so an agent signing up for a tool never parses HTML.

Every inbox also has a calendar that sends and answers real iCalendar invites, with agenda and reminder events.

Built so people stay in control

Workspace policies catch secrets, personal data and blocked phrases, and can require approval for anything that leaves the workspace. Held mail waits in Approvals for a person; no API key, including the agent's own, can approve it. Inbound mail is checked for spoofing, lookalikes, pressure language and prompt injection and can be held before the agent reads it. Every action is in the audit log.

Connect it your way

REST with an OpenAPI 3.1 spec, signed webhooks with retries over 12 hours, an SSE event stream, an MCP server for Claude and other MCP clients, and SDKs for TypeScript, Python and Go plus a CLI. Start on @innmail.app and move to your own domain when branding matters.

Frequently asked questions

How fast does inbound mail arrive?

Inbound goes through Amazon SES to Innmail and is routed to the agent inbox within seconds in normal conditions; webhooks and the SSE stream fire as soon as it is stored.

Can one agent have more than one address?

Each agent has one persistent inbox. Create more agents for more addresses; pods group agents per customer with their own keys and webhooks.

Do I need to connect Gmail?

No. Agent inboxes live on @innmail.app or on your own verified domain. Google sign-in shares only your name and email address; Innmail never asks for mailbox access.

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