Documentation

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.

Outbound: Your agent calls POST /v1/mailboxes/:id/messages. Robotomail composes a standards-compliant MIME message and sends it through Resend. Delivery status is tracked via Resend webhooks — you get message.delivered, message.bounced, and message.complaint webhook events automatically.

Inbound:MX records point to Robotomail's mail server (Stalwart). A background poller checks for new messages every 5 seconds and stores them in the database. Your agent is notified via message.received webhooks, the SSE event stream (GET /v1/events), or by polling the messages endpoint directly.

• Mailboxes — Each mailbox is a real email address. Accounts get 10 / 50 / 200 mailboxes by plan on robotomail.co, with custom domain support. 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

• 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

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