Introduction

What AgentMail is, why agents need their own inboxes, and which surface (CLI, MCP, Console, SDK, or raw HTTP) to start with.

AgentMail gives AI agents programmable email inboxes. Create an inbox, receive mail, trigger workflows, and reply through one API.

Give an agent an inbox

Email handles service signups, address confirmation, password resets, verification codes, receipts, and notifications. An agent that completes these flows needs an address that can receive mail.

With its own inbox, an agent can register for services, complete verification flows, and maintain correspondence without a human operating an email client.

An agent creates and monitors an AgentMail inbox; services and people send email to it; incoming mail triggers the agent's workflow, and the agent sends replies back — The loop: the agent owns an inbox, incoming mail triggers its workflow, and it replies from the same address.

Choose AgentMail instead of an outbound sender

AgentMail gives an agent an inbox it can send from and receive into. Other email tools serve different jobs.

Tool	Who it serves	What it moves
AgentMail	AI agents	An agent’s own inbox: send and receive, with workflows on incoming mail
SendGrid / Resend	Your application	Outbound transactional email your app generates
Mailchimp	Marketers	Outbound marketing broadcasts to a subscriber list
Gmail API	A human user	Programmatic access to that person’s existing inbox

Start from the surface that fits your workflow

All five surfaces use the same API.

CLI

Run calls from a terminal or script one-off checks.

MCP

Give an MCP-capable agent or assistant inbox tools.

Console

Inspect inboxes and messages in a browser.

SDK (TypeScript, Python)

Use typed calls in application code.

Use raw HTTP when you work in a language without an SDK or want no dependency.

Whichever surface you pick, the console shows every inbox and its mail, so you can watch what your agent does as it does it.

AgentMail console showing an agent's inbox with two received threads in the thread list — An agent's inbox in the AgentMail console — each row is a thread of correspondence the agent is holding.

Create an account and API key

Every API request authenticates with an API key sent as a bearer token.

Sign up or sign in at console.agentmail.to.
Open API keys in the dashboard and create a key.
Copy the key when it appears. It is shown once and cannot be retrieved later. If you lose it, create a new key.

Continue with a working inbox

Quickstart: create your first inbox and send a message.
Architecture: understand inboxes, messages, and workflows.