AgentMail
AgentMail is an API-first email platform that gives AI agents their own email inboxes to autonomously send, receive, reply to, and act on email. Unlike traditional transactional email APIs built for one-way notifications, AgentMail is designed for two-way threaded conversations: agents create inboxes on demand, read and semantically search messages, manage threads and drafts for human-in-the-loop review, apply labels and allow/block lists, and react to inbound mail in real time over webhooks or WebSockets. It ships a REST API (OpenAPI 3.1), an AsyncAPI 2.6 WebSocket surface, Python/Node/Go SDKs, a CLI, a hosted MCP server, and IMAP/SMTP bridges, with API-key permissions, idempotency, multi-tenant pods, custom domains, and SOC 2 Type I/II compliance.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles AgentMail the way a machine reads it — 34 machine-readable artifacts across 28 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AgentMail scores 53.7/100 (developing), with a separate agent-readiness read of 84/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile AgentMail
Each block below is one kind of artifact we hold for AgentMail. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AgentMail agent API
The agent API from AgentMail — 2 operation(s) for agent.
AgentMail api-keys API
The api-keys API from AgentMail — 2 operation(s) for api-keys.
AgentMail auth API
The auth API from AgentMail — 1 operation(s) for auth.
AgentMail domains API
The domains API from AgentMail — 4 operation(s) for domains.
AgentMail drafts API
The drafts API from AgentMail — 3 operation(s) for drafts.
AgentMail inboxes > api-keys API
The inboxes > api-keys API from AgentMail — 2 operation(s) for inboxes > api-keys.
AgentMail inboxes API
The inboxes API from AgentMail — 2 operation(s) for inboxes.
AgentMail inboxes > drafts API
The inboxes > drafts API from AgentMail — 4 operation(s) for inboxes > drafts.
AgentMail inboxes > events API
The inboxes > events API from AgentMail — 1 operation(s) for inboxes > events.
AgentMail inboxes > lists API
The inboxes > lists API from AgentMail — 2 operation(s) for inboxes > lists.
AgentMail inboxes > messages API
The inboxes > messages API from AgentMail — 11 operation(s) for inboxes > messages.
AgentMail inboxes > metrics API
The inboxes > metrics API from AgentMail — 2 operation(s) for inboxes > metrics.
AgentMail inboxes > threads API
The inboxes > threads API from AgentMail — 4 operation(s) for inboxes > threads.
AgentMail inboxes > webhooks API
The inboxes > webhooks API from AgentMail — 2 operation(s) for inboxes > webhooks.
AgentMail lists API
The lists API from AgentMail — 2 operation(s) for lists.
AgentMail metrics API
The metrics API from AgentMail — 2 operation(s) for metrics.
AgentMail organizations API
The organizations API from AgentMail — 1 operation(s) for organizations.
AgentMail pods > api-keys API
The pods > api-keys API from AgentMail — 2 operation(s) for pods > api-keys.
AgentMail pods API
The pods API from AgentMail — 2 operation(s) for pods.
AgentMail pods > domains API
The pods > domains API from AgentMail — 4 operation(s) for pods > domains.
AgentMail pods > drafts API
The pods > drafts API from AgentMail — 3 operation(s) for pods > drafts.
AgentMail pods > inboxes API
The pods > inboxes API from AgentMail — 2 operation(s) for pods > inboxes.
AgentMail pods > lists API
The pods > lists API from AgentMail — 2 operation(s) for pods > lists.
AgentMail pods > metrics API
The pods > metrics API from AgentMail — 2 operation(s) for pods > metrics.
AgentMail pods > threads API
The pods > threads API from AgentMail — 4 operation(s) for pods > threads.
AgentMail pods > webhooks API
The pods > webhooks API from AgentMail — 2 operation(s) for pods > webhooks.
AgentMail threads API
The threads API from AgentMail — 4 operation(s) for threads.
AgentMail webhooks API
The webhooks API from AgentMail — 2 operation(s) for webhooks.
Scroll within the panel for all 28 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
agentmail-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
API Reference
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for AgentMail — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/agentmail · machine-readable index on apis.io