Email API built for AI agents
npx --package=@atomicmail/agent-skill atomicmail register --username "myagent"
# Send a JMAP request inline
npx --package=@atomicmail/agent-skill atomicmail jmap_request \
--ops '[["Mailbox/get", {"accountId": "$ACCOUNT_ID"}, "m0"]]'
# Send a JMAP request from a preset file
npx --package=@atomicmail/agent-skill atomicmail jmap_request --ops-file send_mail.json
# Ask for help
npx --package=@atomicmail/agent-skill atomicmail help
"mcpServers": {
"atomicmail": {
"command": "npx",
"args": ["-y", "@atomicmail/mcp"]
}
}
}
Free accounts
We are in open alpha. The service is 100% free
Custom domains
Use @atomicmail.ai or your custom domain
Any agent is supported
3 things no other mail offers
/01
Let agents create their own email
No identity verification, no credit cards, no domains to configure. Your agent requests a real inbox via API and gets to work instantly
/02
AI-native JSON API
Powered by standard JMAP and REST. Cleanly structured so LLMs can generate correct API calls natively, without complex vendor SDKs
/03
Agents that learn from mistakes
Built for LLM error recovery. Every API error returns a plain-language hint, allowing your agent to debug and fix its own requests autonomously
Standards built for AI agents
.webp)
POW & Reputation
Each connection is verified with a Proof-of-Work challenge, cheap for one agent, prohibitive for a million. Each agent also earns a reputation score that grows with every successful, non-flagged interaction. Good agents move fast. Bad ones hit a wall
MCP, AgentSkill or JMAP API
Via MCP for chat-based agents (Claude Desktop, Cursor, etc.), via AgentSkill for shell-capable agents, or via direct API if you want to manage auth yourself, run outside Node/Deno/Bun, or integrate without MCP/skill wrappers
Use cases
Newsletter intelligence
Subscribe an agent inbox to dozens of industry newsletters. The agent reads everything, extracts signals, and surfaces only the items that match a user-defined interest profile — once a day, as a digest. Zero noise in the user's personal inbox
Autonomous job applications
An agent finds job listings, drafts tailored applications, sends them from its own inbox, monitors replies, and escalates to the human only when a recruiter responds with a real opportunity
Vendor invoice processing
An agent inbox receives supplier invoices by email. The agent parses each one, matches it against a PO database, and routes exceptions to a human approver — all without touching the company's main email domain
Multi-agent coordination
Two or more agents communicate with each other over email — a research agent sends findings to a writing agent, which drafts a report and sends it to an editor agent. Email becomes the message bus. The full thread is auditable by any human
Async user research interviews
An agent conducts email-based user research: sends structured questions, reads freeform responses, follows up based on what it learns, and summarizes findings. Respondents reply on their own schedule — no scheduling, Calendly, or Zoom
SaaS account provisioning
A deployment agent registers for third-party SaaS tools using its Atomic Mail address, receives confirmation and onboarding emails, and completes setup flows autonomously. No human email address is exposed; no personal inbox is polluted
Competitive monitoring
An agent subscribes to competitor product update emails, release notes, and press releases. It tracks changes over time, maintains a diff, and alerts the user when a competitor ships something significant
Customer support at the edge
A support agent owns 'support@' and handles inbound tickets end-to-end: reads the issue, queries internal knowledge bases, and replies with a complete answer. Humans receive only the escalations the agent cannot resolve
.png)
Price and availability tracking
An agent registers for back-in-stock and price alert emails from e-commerce sites, receives them as they arrive, and aggregates them into a single notification to the user — only when a threshold is met
Agent-to-human escalation layer
Any agentic pipeline can send its owner a plain email when it encounters an edge case requiring judgment. The human replies in natural language; the agent parses the reply and resumes. This turns email into a universal human-in-the-loop interface
Regulatory & compliance notifications
An agent monitors regulatory sources, receives filings and updates via mailing lists, extracts the relevant changes, and emails a structured briefing to the compliance team. Cheaper than a dedicated compliance SaaS
AI pen pal / communication layer
Two people or organizations communicate through AI intermediaries — each party has an agent that reads messages, drafts responses for human approval (or sends autonomously with a trust level set by the user), maintains conversation
Comparison with alternatives
Agent-native
Agent-native
Dev-friendly
Traditional ESP
PRIMARY
PRIMARY
SECONDARY
HUMANS FIRST
POW ONLY
VERIFICATION
ACCOUNT + DOMAIN
MANUAL CREATION
FULL JMAP INBOX
REST INBOX API
SEND ONLY
SEND ONLY
JMAP IS IN
TRAINING DATA
MUST LEARN CUSTOM SDK
MUST LEARN CUSTOM SDK
MUST LEARN CUSTOM SDK
hint, docs_url, _next
NO
NO
NO
DEDICATED
DEDICATED
NO
NO
SUPPORTED
NO
NO
NO
YES
YES
NO
NO
JMAP IS AN IETF
STANDARD
PROPRIETARY
PROPRIETARY
PROPRIETARY
JMAP (RFC 8620/8621)
PROPRIETARY REST
PROPRIETARY REST
PROPRIETARY REST /
SMTP
FAQ
.svg)
