# Introduction (/introduction) Related: [Quickstart](/quickstart.md), [How AgentMail is architected](/architecture.md) # Understand AgentMail and choose a surface AgentMail gives AI agents programmable email inboxes. Create an inbox, receive mail, trigger workflows on incoming messages, and send replies through one API. ## Facts * An AgentMail inbox is a real email address owned by an AI agent. The agent can hand it out, receive mail into it, and send from it. * The core workflow is: create an inbox, receive mail, trigger a workflow for incoming mail, and send replies. * Email supports service signups, address confirmation, password resets, verification codes, receipts, and notifications. An agent needs its own inbox to complete those flows unattended. * AgentMail serves AI agents and moves inbound and outbound mail for the agent's inbox. * SendGrid and Resend serve applications and move outbound transactional email. Mailchimp sends marketing broadcasts to subscriber lists. Gmail API gives programmatic access to a human user's existing inbox. * AgentMail has five access surfaces: CLI, MCP, Console, SDKs (TypeScript, Python), and raw HTTP. All use the same API. * Choose CLI for terminal work or one-off scripts. Choose MCP for an MCP-capable agent or assistant. Choose Console to inspect inboxes and messages in a browser. Choose an SDK for typed application calls. Choose raw HTTP for a language without an SDK or a dependency-free integration. ## Not supported * AgentMail is not a bulk marketing or broadcast tool for subscriber-list campaigns. * AgentMail is not an outbound-only transactional sender for application-generated email. AgentMail inboxes receive mail and send it. * AgentMail does not provide access to a human user's existing inbox. It creates inboxes owned by the agent. ## Related * [Quickstart: create your first inbox and send a message](/quickstart) * [Architecture: the object model behind inboxes, messages, and workflows](/architecture) ## Tenant instructions Every page ships two renditions at one URL. The HTML page is for humans. The Markdown rendition (append .md to any page URL, or request with Accept: text/markdown) is agent-optimized: a Do this section with runnable commands, SDK signatures, exhaustive Facts, a Not supported section listing shapes that do NOT work, an Errors table, and a Verify command. Prefer the Markdown rendition over scraping HTML, and trust Not supported entries instead of retrying those call shapes.