Features
One pipeline, several doors into it.
Whether a message enters through the REST API, an SMTP client, or a broadcast to an audience, it runs the same path: DKIM signing, suppression checks, tracking, rate limits, and delivery from mail servers we operate ourselves inside the EU. These pages describe each door.
REST APIPOST /emails
SMTP:465 · TLS
Broadcastto an audience
Authenticatekey or credentials
Verify domainDKIM · SPF · DMARC
Suppress & meterbounces · ceilings
Sign and relayEU MTA · TLS
deliveredbouncedopenedclicked
Webhooksigned · retried
Email APIOne REST call to send. Typed SDKs for Node, Python, and Go.SMTP relayPoint WordPress, Supabase, Django, or Rails at one host.React EmailWrite templates as components — rendered before they ship.Webhooks & eventsDelivery, bounce, complaint, open, and click — signed and pushed.Broadcasts & audiencesContacts, lists, and one-off sends with unsubscribe handled.DeliverabilityDKIM, suppression, and reputation monitoring on every send.
Built for AI workflows
Most eusend integrations are now written with an assistant in the loop. We ship the tooling that makes that go well — an MCP server your agent can call, a skill that teaches it how eusend behaves, and docs it can read in full.
AI & agentsHow eusend is built for assistants that write and run your email code.MCP serverSend mail and manage domains from Claude, Cursor, or Codex.Claude Code pluginA skill that teaches Claude how eusend actually behaves.Migrate with AIPaste one prompt and let your assistant do the swap.
Try the whole pipeline before you send anything real.
Every account gets eu_test_ keys. Test sends are accepted, recorded, and fire the full webhook lifecycle — but never reach a real inbox. Verify a domain when you’re ready and swap in a live key.