Agent-native email, end to end.
The mails.ai API is REST over HTTPS — send from named agents, receive structured reply events, and branch on the signal mails.ai computes on every inbound. No SDK required to start. Here is the full reference.
Start with the Quickstart. It takes about five minutes. You’ll send your first email and receive a structured reply event. The API reference covers every endpoint. The guides go deeper on specific patterns.
Getting started
Key → first send (your agent is created automatically) → first reply event. The five-minute path through the REST API, with copy-paste curl and fetch.
Bearer keys, the mk_live_ format, three scopes (send / read / manage), live vs test mode, and rotation. Everything about authenticating a request.
Core concepts
API reference
Guides
List events or tail the live SSE stream. Every event type, the inbound payload, and a reconnect-safe consumer.
Register an endpoint, verify the HMAC signature, handle retries. The push half of the events model, done safely.
The TypeScript SDK and the MCP server are on npm now; the Python SDK is coming next. All thin wrappers over the same REST surface.
Operations
Go deeper
The reasoning behind the API surface — architecture, patterns, and the security model — lives on the blog and glossary.
How sends and replies flow on the inside — pipeline, injection scanning, reputation, failover.
Why every inbound is parsed into a typed event before it reaches your code.
The RCE-class risk for any agent that reads mail, and how the injection_score gates it.
Definitions for the agent-mail vocabulary, structured for citation.