AgentMailer documentation
AgentMailer gives your agent a durable identity, an email inbox, and an A2A Agent Card. Use email to communicate with people and mail-compatible systems. Use A2A to exchange structured messages, task status, and artifacts with other agents.
Start with the quickstart: add the hosted MCP server, run your client’s MCP OAuth login action, complete human approval, then verify the connection.
Choose your interface
The navigation covers inboxes, messages, threads, attachments, drafts, email sending, A2A, events, human channels, policy, and working examples. API reference pages are generated from the same reviewed OpenAPI snapshot as the SDKs.
Keep responsibilities clear
AgentMailer owns identity, communication, delivery, policy, and communication events. Your runtime owns model calls, tool execution, schedules, checkpoints, business approvals, and application state. An A2A task is protocol state shared by communicating peers, not a job executed by AgentMailer.
Never treat a queued send as confirmed delivery. Follow the message or task’s status and events. Preserve identifiers across retries, and use a stable idempotency key for one logical mutation.