Documentation

Robotomail gives your AI agents real email addresses. Connect with MCP, build with SDKs or the REST API, or use the CLI to send, receive and manage email.

What is Robotomail?

Robotomail is managed email infrastructure purpose-built for AI agents. Instead of configuring SMTP servers, managing DNS, or wrestling with mail protocols, you make API calls or connect your agent through MCP. One mailbox works across your connected agents, the API, the CLI and our official SDKs.

Every mailbox gets a real email address that can send and receive messages. Inbound email arrives via webhooks, SSE event streaming, or polling. Outbound email is sent through Resend for reliable delivery with automatic DKIM signing.

How email reaches your application

The sender submits a message to its email service. That service uses DNS and mail routing to find the receiving domain. Robotomail receives messages for its configured mailboxes and exposes them through the API and inbound event integrations.

Your application authenticates to the API over HTTPS to read messages or send from its mailboxes. SMTP is part of mail transport; it is not the same protocol as the HTTP API your agent calls. See domains, messages and webhooks.

Key concepts

Mailboxes — Each mailbox is a real email address. Free includes 1 mailbox on robotomail.co. Paid plans support custom domains: Solo includes 1 mailbox, Starter 10, Growth 50 and Scale 200. These totals include both platform and custom-domain mailboxes. Learn more
Messages — Send and receive email with HTML bodies, custom headers, and outbound attachments. API reference
Threads — Messages are automatically grouped into conversations using standard email threading headers. Learn more
Webhooks — Real-time notifications for inbound messages, delivery confirmations, bounces, and complaints. Learn more
Domains — Bring your own domain with guided DNS setup and automatic verification. Learn more

Quick links

MCP & connectors — Connect Claude, Codex, Cursor, Grok Bot, OpenClaw or Hermes to your mailbox
SDKs — Installation and examples for TypeScript, JavaScript, Python, Go, Ruby and Rust
Quickstart — Zero to first email in 5 minutes
Authentication — API keys and scoping
Send a message — API reference for sending email
Receive and reply — Webhook-driven inbound flow
Limits and quotas — Plan details and rate limits
CLI — Command-line interface for Robotomail

Machine-readable resources

For agents and code generators, the REST API is also published as an OpenAPI 3.1 specification (https://robotomail.com/openapi.json) with a unique operation ID, typed parameters, response schemas, and auth/security definitions for every endpoint. Feed it straight into your favorite client generator or LLM function-calling setup.

SDK guide in Markdown — installation, authentication and first requests in five languages
MCP setup guide in Markdown — connection instructions, OAuth discovery and available tools. MCP publishes its tool schemas through tools/list after authentication.
openapi.json — full REST surface in OpenAPI 3.1
@robotomail/cli on npm — official CLI: npm i -g @robotomail/cli && robotomail --help
llms.txt — machine-readable site map of pages, markdown URLs, and developer resources
skill.md — end-to-end agent self-onboarding instructions

Email standards and RFCs

RFCs document internet protocols and formats. For email, message format, SMTP transport, MIME attachments and domain authentication are separate specifications that work together. Not every RFC has the same status, and later documents can update earlier ones.

Relevant starting points include RFC 5321 (SMTP), RFC 5322 (message format), RFC 2045 (MIME), RFC 7208 (SPF), RFC 6376 (DKIM), RFC 7489 (DMARC) and RFC 7505 (Null MX). Consult the RFC Editor for the current document status and updates. Use Robotomail's API reference for the JSON fields your application actually sends and receives.