Introduction
What AgentMail is, why an agent needs its own inbox, and which surface to start with.
AgentMail is an API platform that gives AI agents their own email inboxes to send, receive, and act on email.
What your agent can do with its own inbox
- Sign up for services and read the verification codes and receipts that come back.
- Hold a real identity on your own domain that teammates can CC and forward to.
- Reach anyone, and be reached, over the protocol everyone already speaks.
- Keep agent mail out of human mailboxes.
Why AgentMail
- Create an inbox in one call, then send, receive, and reply from it.
- Webhooks and WebSockets wake your agent the moment mail lands.
- Threads arrive assembled, quotes stripped, attachments extracted to text.
- Viruses and spam are screened out before your agent sees them. Nothing to configure.
- Server-side allow and block lists bound who an inbox can mail. Drafts act as a human-approval gate.
- SPF, DKIM, and DMARC pass out of the box. A custom domain gets its DNS records generated.
Examples
- An outbound SDR agent that researches leads, sends first touches, and follows up.
- A customer support agent that answers a support inbox from your docs.
- An AI employee with an address teammates can CC and forward to.
Get started
Quickstart
Get a key, create an inbox, and run the send, receive, reply loop.
Architecture
The organization, pod, and inbox hierarchy, and where every other resource attaches.
MCP and Skills
Give any MCP-capable client these operations as tools instead of code.
Console
The web dashboard: API keys, webhooks, domains, metrics, and billing.
Connect it to your agent
Support
The fastest way to get help is the AgentMail Discord, where the team answers questions. For anything you’d rather not post publicly, email [email protected].