Skip to content
Blog / Developer Resources

AgentMail now supports IMAP

Binoy Perera

Updated

Every AgentMail inbox can now be read by any standard email client or library over IMAP. Here is what IMAP is, why it matters for agent inboxes, and how to connect one.

  • developer-resources
  • imap
  • smtp
  • agent-infrastructure
  • announcement

AgentMail now supports IMAP. Every inbox you provision can be read by any standard email client or library that speaks the protocol: Outlook, Apple Mail, Thunderbird, anything that talks to a real mail server. SMTP for sending has been there since launch. With IMAP shipped, AgentMail covers both halves of the standard email protocol surface alongside the API.

This is short. Here is what IMAP is, why it matters for agent inboxes, and how to point a client at yours.

What IMAP is

IMAP (Internet Message Access Protocol) is the standard protocol for reading and managing email on a mail server. Every time you open Apple Mail, Outlook, or Thunderbird and your inbox appears, you are using IMAP under the hood. Messages live on the server, the client syncs them, and changes (read state, deletes, moves) reflect across every device pointed at the same account.

It has been the open standard for reading email since the 1990s. The companion protocol for sending is SMTP, which AgentMail has supported since launch.

Why IMAP matters for agent inboxes

An agent's inbox is not only useful when an agent is reading it. The same inbox often needs to be reachable by humans, ops teams, debugging tools, and legacy systems that only know how to talk IMAP and SMTP.

Humans in the loop. Support inboxes, sales inboxes, and approval inboxes are agent-driven on the write side, but humans want to read them in their own mail client. Connecting Apple Mail or Outlook to an AgentMail inbox over IMAP means a teammate can monitor what the agent is doing without ever touching the API.

Debugging and observability. Sometimes the fastest way to figure out why an agent loop stalled is to open the inbox and look at the messages. IMAP makes that as simple as adding the account to whatever mail client you already have open.

Portability. IMAP is an open standard. The inbox you provision today on AgentMail can be read by software written 25 years ago. If you ever want to move data out, the protocol is right there.

Familiar tooling during development. If you already know imaplib or nodemailer, you can prototype an agent against an AgentMail inbox without learning the SDK first. The SDK is faster and more capable for production, but IMAP and SMTP cover the basics without learning anything new.

How to use it

You will need two things from the AgentMail Console:

  1. Your inbox email address (this is your IMAP username), from Dashboard then Inboxes
  2. An API key (this is your IMAP password), from Dashboard then API Keys

Connection settings:

Code

Host:     imap.agentmail.toPort:     993Username: your inbox email (e.g., myinbox@agentmail.to)Password: your AgentMail API keySSL/TLS:  required

That is it. Point any IMAP client at those settings and it connects. Full setup, including a Python imaplib example and a Node imap example, is in the IMAP and SMTP docs.

For Apple Mail, Outlook, or Thunderbird, add an account with those settings the same way you would add any other IMAP account. The inbox shows up.

For a quick programmatic test in Python:

Python

import imaplibimport osinbox_email = "myinbox@agentmail.to"api_key = os.getenv("AGENTMAIL_API_KEY")imap = imaplib.IMAP4_SSL("imap.agentmail.to", 993)imap.login(inbox_email, api_key)imap.select("INBOX")status, message_ids = imap.search(None, "ALL")for msg_id in message_ids[0].split():    status, msg_data = imap.fetch(msg_id, "(RFC822)")    # parse msg_data[0][1] with the standard library `email` moduleimap.logout()

One thing to know: IMAP currently exposes the INBOX folder. Other folders (Sent, Drafts, Trash) and label-based filtering are available through the AgentMail API, not IMAP. If you need full mailbox structure or real-time inbound notifications, the API and webhooks are the right call.

SMTP, briefly

SMTP for sending has been live since launch. The server is smtp.agentmail.to on port 465 with SSL required, and the password is the same API key. Per-send limits: 50 recipients per message, 10 MB max message size. The From address must match the inbox you are authenticating as. Full credentials and Python and TypeScript examples are in the IMAP and SMTP docs.

When to use IMAP and SMTP vs the API

Use caseUse
Connect Outlook, Apple Mail, or ThunderbirdIMAP/SMTP
Simple programmatic send from any languageSMTP
Read mail from a backup or archiving toolIMAP
Full inbox management, drafts, labels, threadsAPI
Real-time inbound notificationsAPI webhooks or WebSockets
Access all folders, not just INBOXAPI
Bulk operations across many inboxesAPI

The API is still the right surface for everything an agent does at runtime. IMAP and SMTP are there so the inbox behaves like a real email account when you need it to.

Wrapping up

The inbox you provision through AgentMail is a real, addressable mailbox. With IMAP shipped, it is also reachable by every email client and library that speaks the standard protocol. That is the bar a real email provider has to meet, and it is the bar AgentMail meets now.

If you already have an inbox, your existing API key works as the IMAP and SMTP password. If you do not, the Free plan gives you three real inboxes with no credit card required. The Quickstart gets you one in under a minute.

FAQ

Questions, answered.

Connect using host imap.agentmail.to, port 993, with SSL/TLS required. Your inbox email address is the username and your AgentMail API key is the password.

Your username is your inbox email address, found under Inboxes in the AgentMail Console. Your password is an API key generated from the API Keys section of the Dashboard.

IMAP currently exposes the INBOX folder. For other folders like Sent, Drafts, and Trash, or for label-based filtering, use the AgentMail API instead.

Use smtp.agentmail.to on port 465 with SSL required, and the same API key as your password. The From address must match the inbox you are authenticating as, with a limit of 50 recipients and a 10 MB max message size per send.

Yes, any standard IMAP client including Outlook, Apple Mail, and Thunderbird can connect to an AgentMail inbox using the provided connection settings, the same way you would add any other IMAP account.

IMAP and SMTP are best for connecting standard email clients, simple programmatic sending, or reading mail from archiving tools. The API is the right choice for full inbox management, real-time inbound notifications via webhooks, and bulk operations across many inboxes.

Real-time inbound notifications are not handled over IMAP. For that use case, the AgentMail API with webhooks or WebSockets is the recommended approach.

No, the same AgentMail API key works as the password for both IMAP and SMTP connections.

Blog

Suggested reading

View all posts

Comparisons · November 21, 2026

The 8 Best Tools for AI Agents in 2026, One for Every Job

The best tools for AI agents in 2026, picked by job: Monid for paid tools, AgentMail for inboxes, Browser Use, Firecrawl, HydraDB, Hyperspell, smol machines and Telnyx. Pricing and trade-offs for each.

Prompt

Give yourself access to AgentMail by following the guide at:

https://docs.agentmail.to/agent-onboarding.md

and refer to:

https://docs.agentmail.to/llms.txt

for the documentation index.

Start integrating AgentMail into your AI agents today.