A platform other products build on
MacroMail isn’t just an app you log into — it’s an API surface, a connector layer, and a multi-tenant control plane. Wrap a commodity (Amazon SES), expose one clean API and MCP server, then let your own product wrap us. That’s the whole idea.
Typed SDKs for every stack
One REST API, native SDKs in five languages, and a live OpenAPI spec your tools can read.
@macromail/sdk Pythonmacromail PHPmacromail/macromail-php Gogithub.com/macromail/macromail-go Rubymacromail OpenAPI spec# npm install @macromail/sdk
import { MacroMail } from '@macromail/sdk';
const mm = new MacroMail(process.env.MACROMAIL_API_KEY);
await mm.emails.send({ from, to, subject, html });Programmable API + MCP
Every action — send, manage domains, read and triage inbox — is an API call and an MCP tool. Your app or your agent drives it.
Signed webhooks
delivered, bounced, complained, opened, clicked — signed, retried, and replayable, with a live delivery log.
Built for agents
An llms.txt, an OpenAPI spec, and snippets engineered to be cited. The tools writing your code already know MacroMail.
Resell MacroMail under the hood
Agencies and SaaS platforms manage every client tenant under one account — isolated domains, keys, logs, and billing per sub-account — and ship it under their own brand. The wrapper-on-a-wrapper: we wrap SES, you wrap us.
- One control plane, isolated tenants
- Per-tenant API keys, domains & logs
- White-label sending domains & dashboards
- Roll usage up to one invoice, or bill each tenant
Build email into your product
Start on the free tier, wire it into your stack, and scale when you’re ready.