# Send to a list: newsletter, product update or outreach batch

> Send to a list: newsletter, product update or outreach batch: 3 companies fully do it, 10 with a limit, 47 carry the tag. Every listing in Email delivery APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/email.bulk-to-list/
- Markdown: https://www.anchorterminal.com/niches/email.bulk-to-list/index.md (~1,650 tokens)
- Slim: https://www.anchorterminal.com/niches/email.bulk-to-list/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/email.bulk-to-list/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 10 | 47 | 9 | 4 |

## What counts as done

A batch or broadcast call accepts the list, unsubscribe and suppression are applied, and the per-recipient delivered count is reported, without the transactional stream's reputation dropping.

How agents ask for it: send this update to all users; email everyone on this CSV; send the monthly newsletter

## Does the job

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

- **AhaSend API + MCP (AhaSend B.V.)**: Campaign Builder runs from the API, CLI or MCP, adds one-click unsubscribe, honours suppressions and reports delivered counts, on separate marketing infrastructure with its own daily limit. Campaigns share the monthly allowance.
- **Brevo API + MCP (Sendinblue SAS)**: Email campaigns run from the API and an MCP module with lists, segments, unsubscribe and campaign analytics; batch transactional sends take 1,000 versions per call, and dedicated IPs are managed by API.
- **Mailtrap Email API + MCP (Railsware Products Studio LLC)**: Bulk mail goes to a separate Bulk Stream host from transactional, with unsubscribe footers, suppressions and per-recipient logs, and Email Marketing campaigns sit on the same account.

## Does the job, with a limit

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.

- **Amazon SES (Amazon Web Services, Inc.)**: Contact lists with topics add unsubscribe, suppression applies per account, configuration set or tenant, and dedicated IP pools separate streams. Bulk sends take 50 destinations a call, and the sandbox gate still applies.
- **Groundmail API + MCP (Power Only Transit Inc. dba Groundmail)**: Transactional, product and newsletter mail send from separate IPs with per-category one-click unsubscribe, but newsletters need Groundmail's approval, marketing campaigns are not yet offered, and one suppressed recipient fails the whole send with 422.
- **Loops API + MCP (Astrodon Corporation)**: Campaigns are created and audienced by API with unsubscribe, suppression and campaign metrics, but the docs read show no separation of marketing and transactional sending reputation, and the Free plan caps sends at 4,000 to the 1,000 newest contacts.
- **MailerSend (MailerSend, Inc.)**: POST /v1/bulk-email takes up to 500 emails a call but isn't on the Free plan, and MailerSend has no list or newsletter tool with unsubscribe management in the API index read.
- **Mailgun API + MCP (Mailgun Technologies, Inc.)**: Mailing lists and batch sending with recipient variables apply unsubscribe and suppressions, and events give per-recipient delivery. Separating newsletter reputation needs dedicated IPs or subaccounts on higher plans.
- **Mailjet API + MCP (Mailjet SAS)**: Contact lists, segmentation, campaigns with an exclusion list and statcounters cover list sends with unsubscribe and counts. Nothing read separates campaign reputation from transactional sends below dedicated IPs.
- **Mailchimp Transactional (Mandrill) (The Rocket Science Group LLC d/b/a Mailchimp)**: Lists, unsubscribes and campaigns live in the Mailchimp marketing product, not the Transactional API; Transactional separates reputation with subaccounts and dedicated IP pools but has no list send of its own.
- **Postmark API + MCP (AC PM, LLC)**: Broadcast message streams keep bulk off the transactional stream and /email/bulk sends to them, with suppressions per stream, but the Bulk API needs support approval (error 14) and Postmark keeps no lists or campaigns.
- **Resend API + MCP (Plus Five Five, Inc.)**: Broadcasts go to contacts and segments with unsubscribe and suppressions on a separate contact-priced plan, but whether broadcasts send from different IPs than transactional mail isn't documented; e07 was warned about warm-up for CSV batches.
- **Twilio SendGrid (Twilio Inc.)**: Marketing Campaigns Single Sends go to contact lists with unsubscribe groups, IP pools and subusers separate streams. e09 sent a 10,000-subscriber newsletter through the transactional account and saw responses fall.

- not this job: Cloudflare Email Service (Cloudflare, Inc.): The FAQ says Email Service supports transactional email only, not marketing.
- not this job: MailPace (OhMySMTP Ltd): The introduction says MailPace can only be used for transactional email, and marketing and bulk newsletters are strictly prohibited.
- not this job: SendLayer (SendLayer, LLC): No list, campaign or broadcast endpoint; recipients are capped at 10 To and CC and 5 BCC per send, and the service is aimed at transactional mail.
- not this job: SMTP2GO API + MCP (Sand Dune Mail Ltd): No list, campaign or broadcast endpoint in the API index; an unsubscribe footer can be switched on, but list sending is left to the caller.
- not this job: Zoho CPaaS (formerly ZeptoMail) (Zoho Corporation): Zoho CPaaS sends transactional email only; the API has no list, campaign or unsubscribe management.

## What stops agents finishing

- terms allow transactional mail only (Cloudflare, MailPace)
- automated content filter suspends the whole account
- bulk endpoint not on the free plan

## Around it

Before: lead-data.verify-before-send, contacts.list. After: lifecycle-marketing.campaign-report.

## Where this comes from

Weight 9 of 100 in Email delivery APIs: 4 of 32 accounts: newsletters through transactional streams (e09, e24), a CSV lead-gen tool (e07) and a SendGrid account hold (e05); the category is transactional-first so this is weighted low

As data: https://www.anchorterminal.com/api/v1/use-cases/email.bulk-to-list.json, or the MCP tool get_use_case with id email.bulk-to-list. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
