MyAgentMail
Get started
Knowledge baseInboxes

Inbox capabilities

Inboxes

Every inbox is a full two-way mailbox. Here's what you get out of the box.

Send

  • Send via REST (POST /v1/inboxes/{id}/send) or SMTP on port 587 with STARTTLS
  • to, cc, bcc, reply_to — all standard RFC 5322 envelope fields
  • Plain text, HTML, or both in the same message
  • File attachments (via drafts, or raw SMTP)
  • Reply, reply-all, and forward endpoints that preserve In-Reply-To and References correctly

Receive

  • Inbound SMTP on the default myagentmail.com domain and any verified custom domain
  • Parsed bodies (plain + HTML) and attachments available via the API
  • The full raw .eml source is preserved and downloadable via GET /messages/{id}/raw for debugging or signature verification
  • Read via REST, IMAP on port 993, or the WebSocket event stream
  • Mark read / unread, soft-delete messages — list queries hide deleted rows but thread history is preserved

Threading

Threading is automatic. When a reply comes in, we match it against existing threads via In-Reply-To and References headers. Outbound replies get the same headers set automatically when you use the /reply, /reply-all, or /forward endpoints — so agents can reason about conversations as coherent units instead of isolated messages.

Drafts

Drafts let agents compose a message across multiple turns and send in one action. Start with just a recipient, come back later and add a subject, refine the body on the next turn, then fire POST /drafts/{id}/send when everything's ready. See the Drafts guide.

Lists

Named groups of addresses stored per inbox. Useful when an agent needs to track stable audiences — "customers", "investors", "active leads" — without round-tripping to your primary DB.

Addresses & custom domains

Each inbox can accept mail at multiple addresses. Add a verified custom domain alias and it becomes the outbound From header — the canonical @myagentmail.com address stays as an accepting alias so existing threads survive. See Custom domain setup.

Real-time events

Three intake options, pick whichever fits the agent's runtime:

  • WebSocket — wss://myagentmail.com/v1/ws. Subscribe to event types + inbox ids, receive JSON frames. Compare the options.
  • HTTP webhooks — register a URL, receive signed POSTs for every event.
  • Polling — pull GET /messages?direction=inbound on a schedule.