For
Email API by team: AI agents, indie developers, support and agencies
The platform does not change per audience; the problem does. A support team is buying an inbox they can route, an agent builder is buying a mailbox an agent can call, and an agency is buying N of those without N dashboards. Pick the description that matches your team — each page makes the same claims and answers the questions that team actually asks.
AI agents
Give any AI agent an API-keyed mailbox on your own domain — SDK, skill, a hosted MCP server and a CLI. Claude Code, Cursor and Copilot install the skill; anything that speaks MCP needs nothing else.
Indie developers
Run a custom-domain email API from one connection. Send transactional mail from `hello@yourdomain.com` without ever touching an SMTP relay.
SaaS support teams
Run an email API for support@, billing@, and abuse@, then read those mailboxes from your own backend.
Agencies and studios
Manage an email API for every client from one dashboard. Per-domain API keys, and a data boundary you can show in a review.
Privacy-sensitive products
When the requirement is 'email data stays in one place, with a documented boundary', a single-provider email API is the answer — not a marketing claim.
Transactional email API
Send order confirmations, password resets, and receipts from your custom domain over a REST API — no SMTP relay, no separate SaaS.
Every persona page describes the same product. What differs is which capability leads and which objection is answered first — an agent builder asks about the key's blast radius, a support team asks whether the inbox is searchable.
Keep going
- Agent setup — the install path for a coding agent and the MCP server for everything else.
- Compare — if the decision is “which vendor”, not “which team”.
- Integrations — if the decision is already made and the runtime is the question.