For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
contact@agentmail.ccDiscord
DocumentationAPI ReferenceKnowledge BaseChangelog
DocumentationAPI ReferenceKnowledge BaseChangelog
    • Introduction
  • Getting Started
    • What is AgentMail?
    • What can I do with an inbox?
    • Creating your first inbox
    • Getting your API key
  • Agent Patterns
    • Handling inbound emails
    • Allowlists & blocklists
    • Managing threaded conversations
    • Human-in-the-loop workflows
    • Pods for multi-tenant email
    • Using labels to track state
  • Domains & Deliverability
    • Custom domain setup
    • SPF, DKIM, and DMARC setup
    • Emails going to spam
    • Warming Up
    • MX record conflicts
  • Troubleshooting
    • API 403 error
    • Rate limits
    • Preventing duplicate sends
    • Domain not verifying
    • Emails bouncing
    • Why are my emails not showing up?
  • DNS Guides
    • Cloudflare
    • GoDaddy
    • Route 53 (AWS)
    • Namecheap
LogoLogo
contact@agentmail.ccDiscord
On this page
  • Key differences
  • When to use AgentMail
  • Can I migrate from other platforms?
Getting Started

What is AgentMail and how is it different?

Understand how AgentMail compares to traditional email providers.
Was this page helpful?
Edit this page
Previous

What can I do with an AgentMail inbox?

A complete overview of inbox capabilities for AI agents.
Next
Built with

AgentMail is email infrastructure built specifically for AI agents. Unlike transactional email APIs that focus on one-way sending, AgentMail is built for two-way agent communication: dedicated inboxes, native threading, and full receiving support with no shared sending domains.

Key differences

CapabilityAgentMailTransactional API
InboxesCreate thousands of unique inboxes via API, each with its own email addressShared sending domains, no per-agent inboxes
Receiving emailFirst-class support: agents read, parse, and reply to incoming emailsSimple webhook
Threaded conversationsNative threading, support for multi-threaded (cc, bcc, forwarding)Build threading yourself
Agent identityEach agent gets its own email identity (address, display name)Not available
Allowlists / BlocklistsControl who each agent can send to and receive fromNot available
Multi-tenant (Pods)Built-in tenant isolation for SaaS applicationsBuild it yourself
Real-time eventsWebhooks and WebSockets for instant email event streamingWebhooks only (no WebSocket option)
IMAP / SMTPFull protocol access for connecting to email clientsAPI only (no IMAP/SMTP access)
Reply extractionBuilt-in extracted_text and extracted_html to strip quoted text from repliesNot available
Semantic searchSearch across inboxes by meaning, not just keywordsNot available

When to use AgentMail

AgentMail is the right choice when:

  • Your agents are first-class users that need threading, identity, and storage
  • Your agent needs its own email identity rather than a shared noreply@ address
  • You are building conversational email workflows like outreach, support, or scheduling
  • You need per-agent or per-customer inbox isolation (Pods)
  • Your agent needs to sign up for services, receive verification codes, or act as a user on the internet

Can I migrate from other platforms?

Yes. AgentMail’s send API works similarly. Replace your existing send call with client.inboxes.messages.send() and you get the same sending capability plus full receiving, threading, and agent identity features on top. See the Quickstart to get started in minutes.