Now in early access · 7-day free trial

Email built for
the agents you ship.

Give every AI agent its own dedicated inbox. Send, receive, and thread email via one clean REST API — with IMAP and SMTP if you need it.

Start free trial Read the docs

npm install myagentmail

~ provision scout agent 
# Create a new inbox for your agent
curl -X POST https://myagentmail.com/v1/inboxes \
  -H "X-API-Key: tk_..." \
  -d '{"username": "scout"}'

# → scout-abc123@myagentmail.com
# → Ready to send & receive in 50ms

Features

Everything your agents
need to run on email.

Instant inboxes

One API call. Your agent gets scout@myagentmail.com in under 50ms.

Send & receive

Full inbound SMTP. Outbound relay. Automatic threading across conversations.

Custom domains

Bring your own domain. Any TLD — .cc, .io, .ai, .dev. No restrictions.

Multi-tenant

Each customer is fully isolated with their own API keys and inbox scope.

IMAP & SMTP

Standard mail protocols so agents can connect from any client or library.

Verified sending

MX validation and verified-recipient enforcement keep bounce rates low.

Webhooks

Real-time events for every message sent, received, bounced, or replied to.

Bounce monitoring

Inboxes auto-pause above 5% bounce rate to protect sender reputation.

How it works

Three steps.
Your agent is live.

STEP 01

Sign up & get your key

Create an account, start your 7-day trial, and grab your tenant master key from the dashboard.

X-API-Key: tk_...
# tenant master key
STEP 02

Provision inboxes

One API call per agent. Each inbox gets its own address and scoped ak_ key.

POST /v1/inboxes
→ { email, apiKey }
STEP 03

Send & receive

REST, IMAP, or SMTP — whatever your agent needs. Webhooks fire on every reply.

POST /v1/inboxes/:id/send
→ { messageId, threadId }

The API

Simple.
Predictable.
REST.

Three key types give you exactly the scope you need. No OAuth, no SDK required — just X-API-Key.

Full API Reference
Authentication
Key Scope
sa_... Manage tenants
tk_... Manage inboxes
ak_... Send & receive messages
Tenants sa_...
POST /v1/tenants Create tenant → masterKey
GET /v1/tenants List tenants
GET /v1/tenants/:id Get tenant + inboxes
DELETE /v1/tenants/:id Delete all data
Inboxes tk_...
POST /v1/inboxes Create inbox → email + apiKey
GET /v1/inboxes List inboxes
GET /v1/inboxes/:id Get inbox
DELETE /v1/inboxes/:id Soft-delete
Messages & Threads ak_... or tk_...
POST /v1/inboxes/:id/send Send email
POST /v1/inboxes/:id/reply/:msgId Reply in thread
GET /v1/inboxes/:id/messages List messages
GET /v1/inboxes/:id/threads List threads
Webhooks
POST /v1/webhooks
GET /v1/webhooks
DELETE /v1/webhooks/:id
Custom Domains
POST /v1/domains
GET /v1/domains/:d/verify
DELETE /v1/domains/:domain

Deliverability

Deliverability
by design.

MyAgentMail validates every outbound email with MX record checks and requires explicit verification. Send to addresses verified via services like Apollo, ZeroBounce, or NeverBounce — or to addresses that have previously replied to your agent.

Pass verified: true in your send request to assert an address has been verified. If the recipient has already replied, sends are always permitted.

~ verified send 
curl -X POST https://myagentmail.com/v1/inboxes/INBOX_ID/send \
  -H "X-API-Key: ak_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "lead@example.com",
    "subject": "Following up",
    "plainBody": "Hi! Quick question about your workflow.",
    "verified": true
  }'

Pricing

Start small.
Scale when you're ready.

All plans include a 7-day free trial. Credit card required — cancel anytime before the trial ends.

Starter

$5 / month

For solo builders and side projects.

  • 1 inbox
  • 2,000 emails / month
  • 1 custom domain
  • IMAP + SMTP access
  • REST API + webhooks
Start 7-day trial
Most Popular

Developer

$15 / month

For developers shipping agents to production.

  • 10 inboxes
  • 15,000 emails / month
  • 10 custom domains
  • IMAP + SMTP access
  • Email support
Start 7-day trial

Startup

$199 / month

For teams running agents at scale.

  • 200 inboxes
  • 150,000 emails / month
  • 200 custom domains
  • IMAP + SMTP access
  • Priority Slack support
Start 7-day trial

Enterprise

Custom

For large deployments with custom needs.

  • Unlimited inboxes
  • Custom email volume
  • Unlimited domains
  • Dedicated support + SLA
  • Custom limits
Contact sales

FAQ

Common
questions.

What TLDs are supported for custom domains?
All of them. .cc, .io, .ai, .co, .dev, .app — any domain your DNS provider supports. Unlike agentmail.to which restricts certain TLDs, myagentmail imposes no TLD restrictions whatsoever.
How is this different from agentmail.to?
Three key differences: (1) Any TLD is supported for custom domains — agentmail.to doesn't support .cc and others. (2) Full IMAP and SMTP access — your agents can connect with standard email clients, not just REST. (3) Multi-tenant by design — each customer is isolated with their own API keys and inboxes.
Can I use this for cold outreach?
Yes — myagentmail supports cold outreach with built-in safeguards. Before sending, we run MX record validation to confirm the recipient domain can receive email. You pass verified: true in the request body to assert the address is valid. Attempting to send to an unverified address returns a 400 error, and invalid domains are rejected with a 422. This protects your sender reputation and keeps bounce rates low. We recommend pairing myagentmail with an email verification service (like Apollo, ZeroBounce, or NeverBounce) for best deliverability on cold campaigns.
What happens when someone replies to my agent?
The inbound SMTP server receives the reply, stores it in the database with full threading metadata, and fires your configured webhook with a message.received event. Your agent can then poll the messages API or react to the webhook in real time. Threading is automatic — replies are grouped by thread.
Is there a free tier?
Yes — contact us for enterprise pricing on custom domains. We handle the infrastructure, deliverability, and scaling so your team can focus on building agents.
What outbound relay does it use?
We use enterprise-grade SMTP relay infrastructure for outbound delivery with DKIM signing, SPF, and DMARC fully configured. Inbound email is handled by our own SMTP server with direct MX delivery — no third-party dependencies in the receive path.