Niches · Email delivery APIs

Relay mail from a tool or server that only speaks SMTP

Four or more companies' docs show a full fit.

6companies, full fit
12companies, fit with a limit
47companies carry the tag
11share of the category's work
5first-hand accounts

What counts as done

SMTP credentials scoped to one domain or project, accepted on 465 or 587, and a message from the tool delivered with DKIM aligned, revocable without affecting other projects.

How agents ask for it: give Supabase custom SMTP settings, relay outbound mail from my mail server, set the SMTP host for WordPress

Does the job 6

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
AhaSend API + MCP BB
AhaSend B.V.
send.ahasend.com takes 587 (STARTTLS) and 465 (implicit TLS); SMTP credentials are created per domain scope and revoked alone. The llms.txt summary still says 465 is unsupported, contradicting the SMTP page. source
Amazon SES BB
Amazon Web Services, Inc.
SMTP credentials are derived from an IAM user, so each project gets its own user and policy, revocable alone, on ports 465 and 587; IAM conditions can restrict the From identity. e10 found SES free-tier deliverability worse than SMTP2GO. source
Mailgun API + MCP BB
Mailgun Technologies, Inc.
SMTP credentials are set per domain and managed through the HTTP API or UI, on ports 25, 465, 587 and 2525; e28 sends personal-domain mail through Mailgun SMTP. source
MailPace C
OhMySMTP Ltd
SMTP takes ports 25, 587, 2525 (STARTTLS) or 465 (TLS) with the domain's own API token as username and password, so each domain has a separate credential. source
Postmark API + MCP B
AC PM, LLC
Each server and message stream has its own SMTP token (access key and secret), revocable alone, on ports 25, 2525 or 587 with STARTTLS; 465 is not listed. source
Resend API + MCP A
Plus Five Five, Inc.
smtp.resend.com takes 465 or 2465 (implicit TLS) and 25, 587 or 2587 (STARTTLS) with an API key as password; a sending_access key per project, restricted to one domain, is revocable alone, as e01 does. source

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Brevo API + MCP E
Sendinblue SAS
SMTP relay has a Supabase guide and separate SMTP keys revocable alone, but the docs read show no key scoped to one domain or project. source
Cloudflare Email Service B
Cloudflare, Inc.
SMTP runs on port 465 only, with an API token as password, and the token can send from every onboarded domain on the account; port 587 tools must be reconfigured. source
Groundmail API + MCP B
Power Only Transit Inc. dba Groundmail
smtp.groundmail.dev takes 587 or 2525 with STARTTLS (no 465) and credentials are created and revoked one by one, but the docs read show no SMTP credential limited to a domain, unlike API keys. source
Loops API + MCP B
Astrodon Corporation
smtp.loops.so on 587 with an API key as password, with Supabase, Django, Rails and Laravel guides. The key has full account access, so the credential isn't scoped to one project, and SMTP still sends published templates. source
MailerSend BB
MailerSend, Inc.
SMTP users are created per domain through the API and revoked alone, but the relay accepts only port 587 with TLS, not 465. source
Mailjet API + MCP C
Mailjet SAS
SMTP Relay is documented with custom headers, but credentials are the API key pair; scoping one to a project means a subaccount or separate API key with its own senders, not a per-domain SMTP credential. source
Mailtrap Email API + MCP B
Railsware Products Studio LLC
SMTP on 587 with an API token as password, with separate transactional and bulk hosts. Tokens get per-resource permissions, but the pages read don't show a credential limited to one domain, or port 465. source
Mailchimp Transactional (Mandrill) B
The Rocket Science Group LLC d/b/a Mailchimp
smtp.mandrillapp.com accepts 25, 587, 2525 or 465, and any active API key is the password, so a project gets its own key; the key isn't limited to one domain. source
Twilio SendGrid BB
Twilio Inc.
SMTP uses an API key as password, and a restricted key carrying only mail.send, per subuser, can be revoked alone; the pages read don't tie a key to one domain. e10 found free-tier deliverability worse than direct sending. source
SendLayer D
SendLayer, LLC
smtp.sendlayer.net on port 587 with a username and password unique to the domain; 465 isn't listed, and the docs read don't show revoking one credential alone. source
SMTP2GO API + MCP B
Sand Dune Mail Ltd
SMTP users are created, listed and disabled through the API, and e10 and e11 found SMTP2GO the low-cost relay that delivered well. The pages read show no per-domain scope on an SMTP user and don't list the ports. source
Zoho CPaaS (formerly ZeptoMail) C
Zoho Corporation
Each Mail Agent has its own SMTP short passwords, generated and listed by API, so a project's credentials are separate and revocable. Ports weren't on the pages read. source

What stops agents finishing

  • SMTP outage or rate limit leaves sign-ups stuck
  • port 587 not offered (Cloudflare is 465 only)

Around it

Before: agent-auth.sign-up-flow. After: email.delivery-diagnosis.

Where this comes from

Weight 11 of 100 in Email delivery APIs: 5 of 32 accounts: self-hosted relays (e10, e11, e28) and Supabase auth SMTP failures (e25, e26)

The same as data: /api/v1/use-cases/email.smtp-relay.json, or the MCP tool get_use_case with id email.smtp-relay. Other jobs in this category: /api/v1/niches?category=email.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.