AgentMail

AgentMail is an API platform — "the email inbox API for AI agents" — that gives AI agents their own email inboxes, so they can send, receive, and act on email autonomously, using email as a "universal protocol" to communicate with services, people, and other agents rather than relying on a human-owned mailbox. Agents can use these inboxes to sign up for services, receive confirmations, and authenticate under their own identity.

The platform is built around a programmatic Inbox REST API with full message threading, custom domains configured with DKIM, SPF, and DMARC, webhooks and WebSockets for real-time events, official Python and TypeScript SDKs, an MCP server for AI tool integration, and IMAP/SMTP access. It also offers multi-tenant "Pods," aimed at platform builders who need to provision inboxes for many end users or agents at once.

AgentMail's docs describe two setup paths.

For an agent to onboard itself:

1. The agent registers itself by calling the sign-up endpoint with a human's email and a username, and gets back an API key, inbox ID, and organization ID.
2. The human checks their email for a 6-digit OTP code, and the agent verifies it to unlock full permissions.
3. The agent creates an inbox (POST /inboxes, with an optional client_id for idempotent retries) and sends mail (POST /inboxes/<inbox_id>/messages/send with to, subject, and text).

For a human developer integrating AgentMail:

1. Create an account in the AgentMail Console and generate an API key.
2. Add the key to a .env file.
3. Install the SDK — pip install agentmail python-dotenv (Python) or npm install agentmail dotenv (Node/TypeScript).
4. Initialize the client (AgentMail(api_key=...) in Python or AgentMailClient({ apiKey }) in TypeScript), then call inboxes.create() to create an inbox and inboxes.messages.send() to send a message.

Beyond the REST API and SDKs, AgentMail also exposes an MCP server for MCP-compatible AI clients, and supports IMAP/SMTP for tools built around standard mail protocols.

• Giving an AI agent its own persistent email identity so it can sign up for third-party services, receive confirmation emails, and complete email-based authentication on its own.
• Letting agents communicate with people, services, and other agents by email as a "universal protocol," without a human relaying messages.
• Platform builders provisioning and managing inboxes for many end users or tenants at once, via the multi-tenant "Pods" feature.
• Getting real-time notification when mail arrives via webhooks or WebSockets, instead of polling an inbox.
• Sending under a company's own domain with DKIM/SPF/DMARC configured, or integrating via SMTP/IMAP for tools built around standard mail protocols.