Skip to content
AgentMail logo

AgentMail

Dedicated email inboxes for AI agents

AgentMail screenshot

Stats

Rating
8.1
Price
Freemium
Updated
November 1, 2026
Category
Email

We may earn commissions from some links. Learn more.

Get more AI tool alerts:

About AgentMail

A support agent needs an address customers can reply to, not access to your personal inbox. AgentMail gives it a dedicated email identity, with stored conversations, attachments and events that let it respond when a message arrives. I recommend it for builders who want email to be part of an agent's job rather than another mailbox a person has to manage.

Its appeal is the combination of programmatic inboxes and controls for running them across customers. Resend is a strong alternative when conversational inboxes belong alongside your application's transactional email, while Cloudflare Email Service suits builders who want to run a custom email-agent workflow on Workers.

Start building with AgentMail free.


What is AgentMail?

AgentMail is hosted email infrastructure for AI agents. You create an inbox through its API, give your agent access, and use that address to send, receive and reply to email. AgentMail stores the messages and groups replies into threads, so your application can retrieve the conversation later.

That makes it useful for work that continues beyond one request. A customer could email a support agent a document, answer its follow-up question the next day, and receive a reply in the same thread. Your agent supplies the reasoning; AgentMail supplies the mailbox and email operations.

It isn't an AI email client that cleans up your existing Gmail. The starting point is a new address for the agent, not handing it your personal correspondence.


Who is AgentMail for?

AgentMail makes the most sense for developers building support agents, operational assistants and products that give each customer an agent with its own address. Agencies building those workflows can use separate customer workspaces instead of putting every client's conversations into one shared inbox.

I recommend deciding who should own the conversation before choosing an email tool. If customers need to contact an agent directly and return to it later, a dedicated inbox is a good fit. If you mainly want help writing your own replies, the wider email tools category is the more useful place to look.

For a small business, AgentMail is a component of an assistant, not the finished assistant itself. Our guide to AI agents for small businesses is useful if you're still choosing the broader workflow rather than its email infrastructure.

Cold outreach is prohibited. AgentMail is for conversations with people who wrote first, requested contact or expect operational email, not automated prospecting to scraped or purchased lists.


AgentMail pros and cons

Pros
Cons
Dedicated inboxes with stored threads and attachments
Doesn't turn an existing personal mailbox into an AI assistant
Drafts, labels and scheduled sending support ongoing workflows
Free mail includes a "Sent via AgentMail" footer
Pods and scoped keys help separate customer resources
Inboxes cannot move between pods after creation
API, SDK and hosted MCP access
Calendar is currently available only in US production

The strongest reason to choose it is control over the agent's email identity and conversations. The main commitment is that you're still building or connecting the agent workflow, including deciding when it can send a reply.


AgentMail features

Inboxes and conversation context

Each inbox has its own address. You can start with AgentMail's default domain or use a verified custom domain, which is useful when an agent should communicate under your business's name.

Threads automatically group related messages, and full-text search works within one inbox or across the organization. A supervisor workflow could retrieve a customer's earlier conversation before preparing a response, rather than treating every incoming email as a new task.

Attachments, labels and drafts round out that workflow. An agent can prepare a reply for a person to review before sending, and scheduled drafts let you arrange later delivery. Those are building blocks for an approval process, not a promise that every agent action automatically requires approval.

Events and incoming mail

Webhooks notify your server about incoming mail and delivery events. WebSockets provide a persistent connection without a public endpoint, while polling webhooks queue events for agents that run intermittently. Polling webhooks are currently US-only.

The choice should follow how your agent runs. A hosted service can accept webhooks; an agent that starts and stops needs a way to collect what arrived while it was away. WebSockets alone don't deliver events while the connection is offline.

For production workflows, handle duplicate events and monitor the connection or endpoint. AgentMail's webhook delivery is at least once, and events can arrive out of order, so an incoming notification shouldn't automatically trigger the same reply twice.

Domains and customer workspaces

Pods group a customer's inboxes and domains within your organization. For an agency or SaaS product, that gives each customer's email resources a defined home rather than relying on naming conventions alone.

Pair pods with pod-scoped or inbox-scoped API keys. An organization-level key can access resources across pods, so creating separate pods doesn't restrict a broadly privileged key. Permissions let you further limit what a key can read, send or change.

Choose the pod structure before provisioning customer inboxes, because an inbox cannot be moved to another pod later. Custom domains also require DNS setup and verification; selecting a paid plan doesn't do that setup for you.

Agent interfaces and calendar

AgentMail has Python and TypeScript SDKs, a CLI and a hosted MCP server. Compatible assistants can work with inboxes, messages, threads, drafts and attachments through MCP, rather than requiring you to build every email operation into a custom application.

There are also official integration paths for coding assistants and frameworks, including Claude Code, Cursor, Codex, the OpenAI Agents SDK and Vercel AI SDK. That range is useful if you already have an agent and want to add email to it, though the connection and permissions still need configuring.

Every inbox also has a native calendar. In US production, agents can create events, receive emailed invitations and respond to them. That's useful for a support or scheduling workflow that needs to carry a conversation into a meeting without giving the agent a separate calendar identity.


AgentMail pricing

AgentMail has a free plan with no credit card required, followed by Developer, Startup and custom Enterprise plans. Prices below are in US dollars.

Plan
Price
Inboxes
Custom domains
Included usage
Free
$0/month
3
1 in beta, new users only
3,000 emails/month, 100/day and 3 GB storage
Developer
$20/month or $192/year
10
10
10,000 emails/month, 1,000/day, 100 per five minutes and 10 GB storage
Startup
$200/month or $1,920/year
150
150
15,000 emails/day, 1,500 per five minutes and unlimited storage
Enterprise
Custom
Custom capacity
Custom
Contract-specific capacity and deployment options

Free includes the core mail features, pods, webhooks, WebSockets and MCP access. Developer adds email support and removes the AgentMail footer. Enterprise is the route for EU cloud, white-label deployment, a bring-your-own-cloud arrangement or an SLA.

For a small product, Developer is the sensible paid starting point if you need several agent identities and domains. Startup buys substantially more inbox capacity, but its daily and five-minute sending limits still matter when many agents act at once.

You don't have to jump straight from Developer to Startup just because you need another inbox. Developer and Startup support recurring add-ons: $2/month per extra inbox or domain, $2/month per additional 1,000 monthly sends, and $5/month per extra seat. Annual add-on prices are $19.20 for an inbox, domain or 1,000 monthly sends, and $48 for a seat.

Agent self-signup is a separate, restricted starting state: one inbox and up to ten emails a day only to the attached human. Without an attached human it is receive-only; verification or claiming moves the account to Free, with an initial limit on new recipients.

I would size the plan around the number of identities you need and the busiest periods of email activity, not just average monthly volume. The free plan is useful for a small workflow, while Developer's ten inboxes give you more room to separate agents and projects.

Build your agent's email workflow with AgentMail.


AgentMail vs alternatives

Feature
Main fit
Dedicated agent identities and customer email workspaces
Conversational inboxes alongside transactional email
Custom email-agent workflows on Workers and the Agents SDK
Conversation handling
Stored threads, drafts, labels and attachments
Hosted Inboxes with stored threads, drafts and labels
Threaded replies; conversation storage belongs to your app or deployed inbox reference app
Entry paid plan
Developer: $20/month
Pro: $20/month
Workers Paid: $5/account/month minimum for arbitrary-recipient sending
Identity setup
10 hosted inboxes on Developer
3 hosted inboxes on Pro
Addresses and routing rules on your domain, with your own mailbox layer
Entry paid email allowance
10,000 emails/month
50,000 sent and received emails/month
3,000 outbound emails/account/month; unlimited inbound routing
Main cost consideration
Inbox/domain capacity and sending limits
Extra inboxes cost $1/month each with paid pay-as-you-go
$0.35/1,000 extra outbound emails, plus applicable compute, storage and AI usage

AgentMail vs Resend

Resend is a direct alternative for two-way agent email. Its hosted Inboxes store and organize conversations, support replies and attachments, and are accessible through the dashboard, API, CLI and MCP. Shared-team thread assignment is another reason to consider it.

At $20/month, Pro includes 50,000 emails but only three inboxes. Additional inboxes cost $1/month each with pay-as-you-go enabled, and both incoming and outgoing inbox mail count toward the transactional quota. That makes conversation volume part of your email budget, even when the agent is mostly receiving.

I recommend Resend if you want to keep agent conversations alongside an existing transactional email setup. AgentMail Developer is appealing when ten included inboxes and ten domains fit the product you're building better than a larger message allowance with fewer included identities.

AgentMail vs Cloudflare Email Service

Cloudflare Email Service is the better fit when you already build on Workers and want email inside that application. It sends through Workers, REST or SMTP, routes incoming messages to your code, and connects to the Agents SDK for receiving and replying.

Cloudflare supports threaded replies and durable agent state. It also publishes a self-hosted inbox reference app with threads, drafts, search and attachments, so this isn't a choice between having conversations and simple forwarding. The difference is who supplies the mailbox layer: you deploy and operate it on Cloudflare, while AgentMail provides hosted inboxes and conversation resources directly.

Arbitrary-recipient sending requires Workers Paid, with a $5/account/month minimum, 3,000 outbound emails included and $0.35 per additional 1,000. Inbound routing is unlimited, but compute, storage and AI usage have separate meters. Sending is in beta, Cloudflare DNS is required, and daily sending capacity depends on account reputation.

Choose Cloudflare for control over an email workflow on your existing stack. I recommend AgentMail when you want managed inboxes, stored threads and scoped customer resources without owning that mailbox application. Cloudflare's lower base commitment isn't an all-in price for running the same product.


Verdict

I recommend AgentMail for builders giving agents their own email identities, especially when separate customer workspaces, scoped access and ongoing conversations matter. Developer is a practical starting plan for a small product with several agents or domains.

Choose Resend when hosted inboxes should sit beside your transactional email infrastructure. Choose Cloudflare Email Service when you want to build and operate the email-agent workflow on Workers, including its conversation storage.

For AgentMail, start with the identities your workflow actually needs: who receives the message, which conversation the agent retrieves, and whether the response goes through a draft. That is a better basis for choosing capacity than buying the largest sending allowance.

Give your agent an inbox with AgentMail.


FAQ

Does AgentMail manage my existing Gmail?

Its main job is hosting new inboxes for agents, not acting as an assistant inside your personal Gmail. Its Google Workspace integration routes mail for unrecognized addresses to AgentMail and requires domain and routing setup; it isn't personal Gmail synchronization.

Is AgentMail free?

Free includes three inboxes, 3,000 emails a month, 100 a day and 3 GB storage without a credit card. One custom domain is available in beta for new users, and free messages retain the AgentMail footer. Unverified agent self-signup has tighter limits than the normal Free plan.

Can agents receive email and reply in the same thread?

Yes. AgentMail stores conversations as threads and supports replies, attachments and drafts. Webhooks, WebSockets or polling webhooks can connect incoming mail to your agent's workflow.

Can I use AgentMail without building a custom app?

You can connect a compatible assistant through the hosted MCP server or an official plugin path. You'll still need an AgentMail account and a configured connection; email access doesn't supply the rest of the agent's instructions or workflow.