The problem
Email tools weren't built for AI agents
No complete stack
Sending services handle outbound. Inbox providers handle receiving. You stitch together two or three services, manage separate APIs, and pay separate bills.
Not built for agents
Gmail and Outlook return full HTML email bodies that consume thousands of LLM tokens. Your agents waste compute parsing formatting instead of acting on content.
Zero provider flexibility
Current platforms lock you into their sending infrastructure. If deliverability degrades, you're stuck. No way to bring your own providers or route across multiple accounts.
One platform
Send, receive, route, and react
One API surface for outbound mail, agent mailboxes, routing controls, and delivery events.
Agent-shaped inboxes
Create mailboxes on verified domains or shared myagent.mx. Read raw messages when needed, or request clean JSON with signatures, quotes, links, headers, and attachment metadata handled.
- Signatures and quoted history stripped by default
- Links, headers, and attachments available on request
- Batch message actions accept up to 100 IDs
GET /api/v1/mailbox/messages/{id}/content ?strip_signature=true &strip_quotes=true &include_links=true { "body": { "text": "Got it. Paid on Tuesday.", "signature_stripped": true, "quotes_stripped": true }}Inbound mailboxes
Built for agents. Open to your team.
Create dedicated inboxes for your AI agents, with full visibility for your team when they need it. Receive email as clean, structured JSON. Not thousands of tokens of HTML noise.
Dedicated mailboxes on @myagent.mx or your custom domain
Clean JSON, not raw HTML. Signatures and quoted history stripped by default.
Extracted text isolates new replies from quoted thread history
Labels, threads, allowlists, and blocklists. All via API.
Every agent inbox, one view
Give every agent its own inbox, then watch the whole fleet from one place and jump into any thread when it counts.


Search the whole fleet
Built for the keyboard
Compose with attachments
Act in bulk
Colour-coded labels
Outbound sending
Your providers. Our routing.
Connect Gmail, SendGrid, Mailgun, Resend, or any SMTP-compatible provider. Not ready to configure? Send through the built-in account straight away.
Weighted distribution with automatic failover. If a provider goes down, traffic reroutes before your users notice.
Quotas at four levels: per-second, minute, hour, and day. No throttle logic needed.
Health monitoring that acts on its own. Failing providers get disabled automatically. No 3 AM pages.
HTTP API and SMTP on port 587. Drop-in compatible with any agent framework you’re already using.
How it works
From zero to sending in under five minutes
Connect your providers
Add any provider over SMTP or OAuth. Or skip this and use the built-in account.
Create agent mailboxes
Dedicated inboxes on @myagent.mx or your domain. One per agent.
Send and receive via API
HTTP API, SMTP, or both. Routing and failover are automatic.
Scale from one agent
to thousands.
Built for companies running email for their customers' agents. Multi-tenant from the first request.
Multi-tenancy via teams
One Sendmux account, isolated workspaces for every customer you serve.
Inbox-scoped API keys
Issue keys that can read and send for one mailbox, and nothing else.
Complete tenant isolation
Data, quotas, and provider routing are scoped per team. No cross-tenant leakage by design.
Usage-based billing that scales with you
No per-mailbox or per-seat fees. Spin up 10,000 mailboxes. Pay nothing until they send.
Pricing
Pay for what you use. Nothing else.
No per-seat fees. No per-mailbox fees. No minimum commitments. Pay only when emails flow.
Included with every account:
Standard email pricing covers incoming mail and outgoing mail through your own providers. Sendmux SES pricing applies only when you send through our managed Amazon SES account, which is intended for triggered and transactional mail.
Need dedicated infrastructure, SLAs, or volume pricing?
Talk to us about enterpriseCommon Questions