What is myagentmail?

A multi-tenant email API purpose-built for AI agents. Real inboxes with IMAP and SMTP, real threading, real custom domains — none of the compromises you'd hit trying to use a transactional provider for agent workflows.

The problem

Most email APIs are built around one assumption: the sender is a product that blasts out receipts and marketing mail. When you try to build an agent on top of them, the rough edges show up fast:

• No real inbox. Transactional providers only speak outbound. Replies either vanish or go to a shared catch-all you can't query per-inbox.
• No threading. You end up writing your own In-Reply-To and References plumbing on top of a send-only API.
• No multi-tenancy. When your reseller customer needs isolated email infra for their own customers, you either create a new account per end-user or punt on isolation and pray no key leaks.
• No real-time intake. Polling IMAP from an agent loop is slow and flaky, and standing up a webhook receiver for every deployment is a deployment headache.

What we are

myagentmail is an email backend designed around the way agents actually work:

• Real mailboxes. Every inbox has IMAP + SMTP credentials. You can use the REST API, a stock mail client, or both. Threads, attachments, replies, forwards, drafts — everything agentmail.to-compatible, everything accessible via a single key.
• Custom domains as aliases, not new inboxes. Add a custom domain and its address becomes an alias on your existing inbox. All prior thread history is preserved. Replies to the old @myagentmail.com address still land in the same mailbox.
• Workspaces. Isolation containers under your tenant. Hand a scoped wk_ key to each of your reseller customers and they can only see their own inboxes, domains, and threads — but you still have one billing relationship with us.
• WebSocket real-time. Agents open a socket, subscribe, and receive events the moment they arrive. Perfect for the 2FA-code-in-one-turn flow where you don't want to run a public webhook receiver.
• HTTP webhooks too. When you do want durable fan-out, every event also fires your configured webhooks with HMAC signatures.

When to pick something else

myagentmail is intentionally not a transactional-email firehose. If you're sending 10M receipt emails a day to an opt-in mailing list, a dedicated high-volume provider like SES, Postmark, or Resend will serve you better. We're the right pick when:

• Your sender is an agent that reads replies and reasons about them
• Each user needs their own real inbox, not a shared one
• You need to give your customers isolated email infra under your own brand