Head to head · Sending email · October 2026 research run

Cloudflare Email Service vs Mailchimp Transactional (Mandrill)

Cloudflare Email Service scores 67 (B) on agent readiness against Mailchimp Transactional (Mandrill)'s 63.8 (B), and leads in 5 of 7 scored categories. Mailchimp Transactional (Mandrill) leads on reliability and payments & pricing. Both do sending email.

Best email delivery APIs for AI agents · All 174 email comparisons

Which one, for what

Cloudflare Email Service B

Best for Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.

Ahead on

  • Schema & documentation, 89 against 79
  • Agent ergonomics, 72 against 60
  • Security & auth, 79 against 68
  • Maintenance & community, 81 against 28
  • Transparency & trust, 77 against 71

Watch for

Email Sending has been in public beta since 16 April 2026. Cloudflare's terms let it remove a beta service at any time, and no SLA was found

Mailchimp Transactional (Mandrill) B

Best for Teams already paying for Mailchimp Standard or Premium that want transactional mail, inbound parsing and an MCP server on the same account.

Ahead on

  • Reliability, 70 against 53
  • Payments & pricing, 53 against 45

Also in its favour

  • No incidents deducted, where Cloudflare Email Service loses 3 points for them

Watch for

Full use needs a Standard or Premium Mailchimp marketing plan in addition to the email blocks

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Cloudflare Email Service +53

Cloudflare Email Service 81

Read for a closed service. The newest Email Service changelog entry is still 25 September 2026 (per-domain suppressions), 37 days before 1 November. The cloudflare TypeScript SDK 7.3.0, dated 2 October 2026 in its changelog, adds a per-domain scope (one sending domain or the whole account) to the emailSending.suppressions methods, a change to this service's client, so it sets the line (30). It drops to 20 after 1 November unless a newer Email Service change lands. In the 90 days from 3 August, changelog entries on 4 and 25 September, plus SDK releases counted at half, TypeScript 7.1.0 (17 August), 7.2.0 (25 September) and 7.3.0 (2 October) and Python 5.7.0 (3 September), 5.8.0 (25 September) and 5.9.0 (2 October) (20). A public changelog with RSS, a community forum and a developer Discord. We didn't sample reply times (10 of 15). The cloudflare SDKs for TypeScript, Python and Go are current, Go at v7.13.1 (20 October) by the repository tags (15). The OpenAPI file carries the sending paths. Nothing else to measure for a hosted endpoint (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.

Mailchimp Transactional (Mandrill) 28

The newest dated Transactional release is specification 1.4.1 on 24 March 2026 (commit a996b63 in the generator repository), with the Node and Python libraries at 1.4.1, 225 days before this check (0). No dated Transactional release or changelog entry in the 90 days from 6 August. The newest Transactional release-notes entry is 19 August 2025 (0). A public changelog, a support contact and an API help address in the specification. We saw no public issue replies (6). The Node and Python libraries are both at 1.4.1 and match the current API version (15). The generator repository has workflows that validate the specification and build and test each library, and the Node library was updated in February 2024 for an Axios advisory. The test workflow needs a secret key, so we could not see results (7). 0+0+6+15+7 = 28.

Reliability Mailchimp Transactional (Mandrill) +17

Cloudflare Email Service 53

Graded on the hosted Email Sending REST API with the hosted lines. www.cloudflarestatus.com is a Statuspage with Email Sending and Email Routing as separate components, both operational on 1 November (20). The incidents feed read on 8 October held 50 incidents from 19 September to 8 October 2026, and the feed read on 1 November holds 50 from 16 to 31 October. Neither names either email component. The labelled majors since 16 October are regional or limited to one product (network connectivity in North America on 23 October, customers behind an external vendor firewall on 27 October, R2 and Durable Objects on 21 October), so they read as partial. The history page loads by script, so 3 August to 18 September and 9 to 15 October went unread. 12 of 30 (10 before), as cloudflare-r2, cloudflare-mcp and cloudflare-workers-ai read the same page with an unread stretch on 1 November. 1,200 API requests per five minutes per token and 200 a second per IP, 50 recipients and 25 MiB per message. The daily sending quota and the send rate limit still have no published number (12 of 15). The send endpoint documents 429 with code 10004, the Cloudflare API returns retry-after and Ratelimit headers, and the SDKs back off. No idempotency key for sends (9 of 15). No SLA found, and the agreement gives no commitment for beta services (0). Email Sending is still marked Beta on the docs home page (updated 15 October), although the OpenAPI send operation is tagged generally-available. We scored from the docs (0). 20 + 12 + 12 + 9 + 0 + 0 = 53.

Mailchimp Transactional (Mandrill) 70

Graded on the hosted Transactional API with the hosted lines. status.mailchimp.com lists Mailchimp Transactional as its own component and keeps event history by month (20). In the 90 days from 6 August 2026 it shows three Transactional incidents, all sending delays, on 1 September (16:19 to 20:27 UTC, "select" accounts), 15 September (13:36 to 18:02 UTC, "a subset of customers") and 17 September (23:31 to 00:09 UTC, "a subset of customers"). Each hit part of the accounts and none is described as the API being down, so minor only (20). Published numbers cover /messages/search at 20 calls a minute, test mode at 10,000 messages a day and the demo at 25 emails an hour. The hourly sending quota is set from reputation with no figure, and no general request limit was found (10). The search endpoint returns 429 and the release notes say to retry 60 seconds after the first of the 20 calls. Mail over the hourly quota is queued in a backlog and not refused. No idempotency key for sends was found, so this is retry-wait guidance alone (10). No SLA found, and the additional terms supply the service as-is (0). Generally available (10). 20+20+10+10+0+10 = 70.

Agent ergonomics Cloudflare Email Service +12

Cloudflare Email Service 72

A send returns a small object grouping recipients into delivered, queued and permanent_bounces. Send events are read through the GraphQL Analytics API, where the caller picks fields (18 of 25). Suppression lists page by cursor with per_page up to 1,000 and filters for email, reason and scope. The GraphQL datasets filter by status, date and domain (17 of 20). REST errors carry a numeric code and a machine-readable message, SMTP returns enhanced status codes with a troubleshooting section, and the binding throws string codes (18 of 20). No idempotency key on send or send_raw. Only the DNS re-apply call is described as idempotent (4 of 20). A send needs to, from, subject and one body field, and Cloudflare publishes SDKs for Node, Python and Go (15).

Mailchimp Transactional (Mandrill) 60

Graded on the API. /messages/search takes a limit up to 1,000 and send responses are one small object per recipient. No field selection was found. The hosted MCP server has 9 tools and reaches the 99 operations through list_api, describe_api and call_api, which keeps the definitions small (16). Search filters by date, tag, sender and API key, with no offset or cursor, so larger result sets go through a queued export (10). Errors return status, code, name and message, and the fundamentals page pairs common ones with a cause and a fix (16). No idempotency key. Test keys let an agent try sends without delivery, and scheduled messages can be listed and cancelled. The MCP tool annotations need a key to list, so they're unread (5). A send needs a key, a sender, a recipient and content. Official libraries for Node, Python, PHP and Ruby (13).

Security & auth Cloudflare Email Service +11

Cloudflare Email Service 79

Cloudflare API tokens are revocable and scoped by permission, with separate send and read permissions, an optional expiry and an IP address filter. A send token covers every onboarded domain on the account, and the OpenAPI operation also accepts the legacy global API key (27 of 30). A read-only permission exists, and a Workers binding can be limited to named sender or destination addresses. Accounts without a sending domain can reach only verified addresses. No approval step for sends or deletes (14 of 20). Sending returns no untrusted content, but Email Routing hands inbound mail to Worker code and the docs suggest email as a way to drive agents, with no prompt-injection guidance found (6 of 15). Account audit logs record domain and suppression changes for 18 months, and each send is visible in the activity log and GraphQL datasets for about 30 days (14 of 15). security.txt, re-read on 1 November, names HackerOne and a disclosure policy and has no Expires field. Cloudflare's ISO certifications page, read on 1 November, says it is certified to ISO 27001 (since 2019, now 27001:2022), ISO 27018 and ISO 27701, with a scope of the Cloudflare global cloud platform, which doesn't name Email Service. 2 held back for the missing Expires field, which RFC 9116 requires, as cloudflare-r2, cloudflare-workers-ai and cloudflare-sandbox-sdk read the same evidence (18 of 20, 16 before, when certifications went unread). 27 + 14 + 6 + 14 + 18 = 79.

Mailchimp Transactional (Mandrill) 68

API keys are created and revoked in the web app, several to an account, and each can be limited to chosen endpoints and to IP addresses. Keys do not expire and no rotation tooling was found. A new key has full account access by default. The key travels in the JSON body or a Bearer header, not the URL (26). Per-endpoint key permissions, IP limits, test keys that send nothing and subaccounts that can be paused. No approval step for sends or deletes (15). The API and the MCP server return inbound mail and stored message content, which is untrusted text. No guidance on prompt injection was found in the MCP guide or the docs (3). The Account Security page lists the IP addresses that used the account and whether each came by API, SMTP or web, and searches can filter by API key (10). A responsible disclosure programme with no rewards, a security.txt with a contact and no Expires field, SOC 2 reports and ISO 27001 per the security page, and regular penetration tests. No public advisory feed found (14).

Schema & documentation Cloudflare Email Service +10

Cloudflare Email Service 89

Cloudflare's public OpenAPI 3.0.3 file, re-read on 1 November, still has 29 operations under /email/sending and 46 under /email/routing (25). llms.txt for the product and a Markdown copy of every docs page (10). Operation descriptions state the purpose and the guides say when to pick REST, the binding or SMTP, with little on when not to call an operation (14 of 20). Address fields are typed as a string, a named object or an array, attachments use a discriminator on disposition, and error messages are enums. Custom headers are a free map (12 of 15). Request samples in curl, TypeScript, Python, Go and Terraform, a table of 15 REST error codes (10207, sending paused for the account, added since 8 October) and 20 binding codes. The guide's sample response omits message_id and suppressed_recipients, and its error table omits the 409 the OpenAPI file documents (13 of 15). Version in the path (/client/v4) and a dated product changelog with RSS (15).

Mailchimp Transactional (Mandrill) 79

An OpenAPI 3.1 file with all 99 operations is public at mailchimp.com/developer/openapi/api-reference-2.json, and a Swagger 2.0 copy sits in the client library repository. The link to it in the Transactional llms.txt returns 404 (25). llms.txt for the developer site and for Transactional, and a Markdown copy of every page at the URL plus .md (10). Each operation has a summary and a description averaging about 120 characters. They say what a call does and seldom when not to use it (11). Request bodies carry 36 enums, required fields, date patterns and minimum and maximum values. Headers, metadata and merge variables are free-form objects (11). Reference pages show request and response samples with code in eight languages, and each operation lists typed error bodies. The OpenAPI file itself has no examples (13). The version is in the path, but the docs use 1.0, 1.3 and 1.4 in different places, and the public changelog has nothing newer than 19 August 2025, so the move to 1.4 in March 2026 is not in it (9).

Payments & pricing Mailchimp Transactional (Mandrill) +8

Cloudflare Email Service 45

No x402, MPP or L402 on the Email Sending endpoints (0). $0.35 per 1,000 emails after 3,000 a month, and the $5 Workers Paid minimum, are public without a login (20). The only free sending is to the account's own verified destination addresses, on any plan. Arbitrary recipients need the paid plan, and we didn't check whether signup asks for a card (10 of 20). An account, an API token and a domain on Cloudflare DNS are set up by a person in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Mailchimp Transactional (Mandrill) 53

No x402, MPP or L402 (0). Block prices are public without a login, $20 per 25,000 emails falling to $10, and $29.95 a month for a dedicated IP. Full use also needs a Standard or Premium marketing plan, whose price is on a separate page (20). The demo gives 500 emails once on any Mailchimp account, free plan included. We take 5 off because it sends only to the account's own verified domain and we could not confirm that signup asks for no card (15). A person signs up in a browser, enables the add-on, creates a key and sets DNS records, so there is no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightCloudflare Email ServiceMailchimp Transactional (Mandrill)Edge
Reliability16%5370Mailchimp Transactional (Mandrill) +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8979Cloudflare Email Service +10
Agent ergonomics13%7260Cloudflare Email Service +12
Security & auth14%7968Cloudflare Email Service +11
Payments & pricing10%4553Mailchimp Transactional (Mandrill) +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8128Cloudflare Email Service +53
Transparency & trust7%7771Cloudflare Email Service +6
Negative events≤15-30
TotalB 67/100B 63.8/100

Facts side by side

FactCloudflare Email ServiceMailchimp Transactional (Mandrill)
KindHTTP APIHTTP API
VendorCloudflareIntuit Mailchimp
Hosted endpointhttps://api.cloudflare.com/client/v4https://mandrillapp.com/api/1.4
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePaid
x402nono
LicenceProprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official cloudflare SDK on npm is Apache-2.0Proprietary service under Mailchimp's Standard Terms of Use and Additional Terms. The client libraries are under Mailchimp's own client library licence agreement
Tools exposednone9
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-252026-03-24
Terms last updated2025-09-12no date given
Privacy policy last updatedno date given2026-03-09
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity3.8M npm/wk, 364k PyPI/wk226k npm/wk, 132k PyPI/wk
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Cloudflare Email Service

Cloudflare API tokens can be limited to sending, given an expiry and restricted by IP address, and a public OpenAPI file covers 29 Email Sending operations. Sending is still in beta, with no SLA, no idempotency key and no published daily quota, and it needs a domain on Cloudflare DNS and the Workers Paid plan.

Mailchimp Transactional (Mandrill)

A public OpenAPI 3.1 file covers all 99 operations, the docs serve Markdown and llms.txt, and keys can be limited by endpoint and IP address. Sending needs a Standard or Premium Mailchimp plan plus $20 blocks of 25,000 emails. No send idempotency key or SLA was found, and the newest dated release is from 24 March 2026.

Before you call either

Cloudflare Email Service

  1. POST to https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send with Authorization: Bearer <token>. The body needs to, from, subject and one of html or text
  2. Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the emailSendingAdaptive GraphQL dataset first
  3. On 429 (code 10004) wait for the retry-after header. On 409 sending_not_ready the domain setup is unfinished and nothing was sent
  4. Read result.delivered, result.queued and result.permanent_bounces in the response. A 200 does not mean every recipient was accepted
  5. Keep to 50 recipients across to, cc and bcc, and 25 MiB per message including attachments
  6. For SMTP use smtp.mx.cloudflare.net on port 465 with implicit TLS, username api_token and the API token as password. Port 587 is not supported
  7. By default one suppressed recipient fails the whole send. Turn on Drop suppressed recipients for the domain to send to the rest

Mailchimp Transactional (Mandrill)

  1. Send every call as POST with the key in the JSON body as key. The MCP server takes the same key as Authorization: Bearer
  2. Use a test API key while building. Test sends are free, capped at 10,000 a day, and deliver nothing
  3. Verify the sending domain with DKIM and DMARC first. Mail from an unverified domain is rejected with the reason unsigned
  4. Keep /messages/search under 20 calls a minute and set limit (default 100, maximum 1,000). There is no offset, so use an activity export for more
  5. For a restricted key that must also use the MCP server, enable the AI Agents permission group on the key

Questions

Which is better for AI agents, Cloudflare Email Service or Mailchimp Transactional (Mandrill)?

Cloudflare Email Service scores 67 (B) on agent readiness against Mailchimp Transactional (Mandrill)'s 63.8 (B), and leads in 5 of 7 scored categories. Mailchimp Transactional (Mandrill) leads on reliability and payments & pricing.

Do Cloudflare Email Service and Mailchimp Transactional (Mandrill) need an API key?

Both need an API key.

Can an agent call Cloudflare Email Service and Mailchimp Transactional (Mandrill) without installing anything?

Yes. Cloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4 and Mailchimp Transactional (Mandrill) at https://mandrillapp.com/api/1.4.

Other comparisons with Cloudflare Email Service or Mailchimp Transactional (Mandrill)

Machine-readable

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.