Overview
Atomic Mail gives your agent a real inbox over one API. Registration needs no human and no API key: the agent proves work, gets name@atomicmail.ai, and from then on reads, sends and reacts over JMAP. People and apps connect an existing inbox with OAuth 2.0. Both paths are compared on the Authentication page.
Every wrapper speaks the same three commands, register, jmap_request and help, so the docs for one path apply to the others.
Ways to integrate
| Approach | Best for |
|---|---|
| AgentSkill | Shell agents: Claude Code, Codex, Hermes, OpenClaw. One npx command, no dependencies. |
| MCP | Chat hosts: Claude, Cursor, ChatGPT. Local stdio server or the hosted one. |
| REST + JMAP | Any language. Proof-of-work login, then RFC 8620 requests. |
| Integrations | Zapier, n8n, Dify, LangChain. A person or a workflow owns the inbox. |
Who owns the inbox
| Path | Owner | Requires |
|---|---|---|
| Proof of work | The agent | A shell or an MCP host. No key, no browser. |
| OAuth 2.0 | A person | One browser sign-in, then tokens. Zapier, hosted MCP, your app. |
Both end with the same inbox and the same JMAP calls. The agent flow walks through the agent-owned path end to end.
What to expect
Every inbox is free during open alpha and gets an @atomicmail.ai address, or your own domain verified once in the dashboard. Sending volume starts small and grows with the inbox's reputation, so a new inbox earns headroom by sending mail that gets delivered.