atomicmail.ai valid

Atomic Mail for Agents

Atomic Mail gives AI agents a real email inbox they can run on their own. An agent self-registers a username@atomicmail.ai address with a Proof-of-Work challenge — no human, no account, no domain, no credit card, no CAPTCHA — then sends, receives, and manages mail programmatically. It is built on JMAP, the open IETF standard (RFC 8620/8621), so there is no proprietary SDK and no vendor lock-in, and it is free during the open alpha.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T15:22:35.606Z. Cached copy · Source on atomicmail.ai

# Atomic Mail for Agents

> Atomic Mail gives AI agents a real email inbox they can run on their own. An agent self-registers a username@atomicmail.ai address with a Proof-of-Work challenge — no human, no account, no domain, no credit card, no CAPTCHA — then sends, receives, and manages mail programmatically. It is built on JMAP, the open IETF standard (RFC 8620/8621), so there is no proprietary SDK and no vendor lock-in, and it is free during the open alpha.

Atomic Mail is agent-native email infrastructure. Unlike send-only email APIs, every agent gets a full inbox and can read and reply, not just send. Because the API is JMAP — a standard most LLMs already know — agents can call it directly, or through a hosted MCP server, a local MCP server, an AgentSkill for shell-capable agents, a LangChain toolkit, an n8n node, a Make integration, or a Dify plugin. Each connection is verified with Proof-of-Work and every agent earns a reputation score, which keeps registration cheap for a single agent but prohibitive for abuse at scale. Operated by AtomicMail Systems OÜ, Tallinn, Estonia.

## Quickstart for AI agents

If you are an AI agent, you can connect and get a working inbox in under a minute:

1. Connect the hosted MCP server at https://mcp.atomicmail.ai/mcp (OAuth sign-in, or one-step API-key connect — no local code), or run the local stdio server: `npx -y @atomicmail/mcp`.
2. Call the `register` tool once to create your own `username@atomicmail.ai` inbox via a Proof-of-Work challenge (no human, no domain, no credit card, no CAPTCHA).
3. Use `jmap_request` — or raw JMAP at https://api.atomicmail.ai (auth at https://auth.atomicmail.ai) — to send, receive, search, and reply. Call `help` for a JMAP cheatsheet and worked examples.

## Getting started

- [Website](https://atomicmail.ai): What it is, how it works, use cases, and comparisons.
- [Getting Started](https://docs.atomicmail.ai/getting-started.html): Register an inbox and send a first message.
- [Dashboard](https://dashboard.atomicmail.ai): Web UI for humans to view and manage agent inboxes.
- [Full text (llms-full.txt)](https://atomicmail.ai/llms-full.txt): The complete text of this website plus the full developer documentation in one file.

## Integration methods

- [Hosted MCP Server](https://docs.atomicmail.ai/mcp-remote.html): The hosted remote MCP server at https://mcp.atomicmail.ai/mcp — OAuth sign-in or one-step API-key connect, no local code.
- [MCP Server (local)](https://docs.atomicmail.ai/mcp.html): Local stdio Model Context Protocol server for chat-based agents such as Claude Desktop and Cursor.
- [AgentSkill](https://docs.atomicmail.ai/skill-install.html): Install as a skill for shell-capable / CLI agents.
- [Raw JMAP API](https://docs.atomicmail.ai/jmap.html): Call the open JMAP protocol directly from any language, with no SDK.
- [OAuth 2.0](https://docs.atomicmail.ai/oauth.html): Authorization-code + PKCE flow for third-party apps (Make, n8n, Zapier, remote MCP).
- [LangChain To
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=atomicmail.ai · GET /v1/domain/atomicmail.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for atomicmail.ai:
1. POST https://agentwebmap.com/v1/sites/atomicmail.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://atomicmail.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/atomicmail.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/atomicmail.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.