Head to head · Sending email · October 2026 research run

Mailchimp Transactional (Mandrill) vs Zoho CPaaS (formerly ZeptoMail)

Mailchimp Transactional (Mandrill) scores 63.8 (B) on agent readiness against Zoho CPaaS (formerly ZeptoMail)'s 60.1 (C), and leads in 4 of 7 scored categories. Zoho CPaaS (formerly ZeptoMail) leads on security & auth, maintenance & community and transparency & trust. Both do sending email.

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

Which one, for what

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 41
  • Agent ergonomics, 60 against 55
  • Payments & pricing, 53 against 45

Watch for

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

Zoho CPaaS (formerly ZeptoMail) C

Best for Low-volume transactional senders who want prepaid credits without a monthly plan, and teams already on Zoho.

Ahead on

  • Security & auth, 78 against 68
  • Maintenance & community, 44 against 28
  • Transparency & trust, 82 against 71

Watch for

No API rate limit, 429 behaviour or Retry-After was found in the reviewed documentation or the OpenAPI file

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.

Reliability Mailchimp Transactional (Mandrill) +29

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.

Zoho CPaaS (formerly ZeptoMail) 41

Graded on the hosted email API with the hosted lines. Zoho's status site at us.zohostatus.com listed three Zepto Mail components with status and incident history sections on 8 October, and status.zoho.com points there; the line is kept as for zoho-desk and zoho-crm (20). On 2 November the host answered robots.txt with a 404 carrying an error page ("We have encountered a problem while executing your request"), read as blocked as for the other Zoho listings, so nothing else was requested. The 8 October RSS reading (last status change 29 July 2026) is struck, and no history in the window was read (5). No request rate limit was found. The docs give payload caps (500 addresses a field, 60 attachments, 15 MB each), a per-day sending limit error (SMI_115) and the sandbox allowance of 10,000 emails a day (6). No 429 handling, Retry-After or idempotency key found in the docs or the error-code table (0). No SLA found (0). The email channel is generally available, while SMS, WhatsApp and voice are marked beta (10).

Maintenance & community Zoho CPaaS (formerly ZeptoMail) +16

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.

Zoho CPaaS (formerly ZeptoMail) 44

Every dated source found was checked. What's New dates entries by month and has nothing after September 2026 (the rename with SMS, WhatsApp and voice endpoints), which lies 33 to 63 days back, and month-only entries don't set recency inside the month. The official WordPress plugin (transmail on wordpress.org, by Zoho Mail) was last updated on 28 September 2026 at 3.3.4, 35 days back. The API help pages carry no dates. The getting-started and subscription help pages say "Last updated: October 22, 2026", but a revised help page shows no API change, so the stamp doesn't set recency (omnisend's reading, where a new operation did); counted, recency would be 30 and maintenance 54. So the last change is within 90 days, not shown within 30 (20, cause time). In the 90 days from 4 August, What's New has one entry for September and one for August (28 of whose 31 days fall inside), and the plugin's 3.3.4 counts half as a package release that doesn't change the service. The July entries have left the window. 2.5 is fewer than three (0, cause time). A public changelog, a support address and a contact page that says support runs around the clock. We saw no public forum replies (10). The Node SDK zeptomail 8.0.1 of 29 May 2026 per the 8 October check (npm not re-read), the only official SDK found (10). The npm package names no source repository, so CI and dependency health couldn't be read (4). 20 + 0 + 10 + 10 + 4 = 44.

Transparency & trust Zoho CPaaS (formerly ZeptoMail) +11

Mailchimp Transactional (Mandrill) 71

Closed service with published terms and a named contracting entity. The client libraries are source-available under Mailchimp's own licence agreement, which is not an OSI licence (15). The additional terms and the docs agree that sent message content is kept 30 days, the docs add 90 days for bounce details and 48 hours for the backlog, and a data processing addendum dated 26 September 2024 covers deletion. The terms add that retention is not guaranteed (24). No deprecation policy was found, and the API Use Policy says the APIs can change by a posting or an email. Past notices carried dates, such as the TLS 1.0 and 1.1 retirement announced on 5 June 2023 for 18 July 2023 (10). A sub-processor list with locations is public but was last updated on 29 February 2024, and the security page places Mailchimp's own servers in United States data centres (15).

Zoho CPaaS (formerly ZeptoMail) 82

Closed service with its own published terms of use, and an MIT Node SDK (20). Zoho's privacy policy of 22 December 2025 covers service data, and the CPaaS pages say content is stored only on opt-in for 60 days and logs for 60 days. The pages disagree on deletion. The GDPR page says account data is deleted within 24 hours of a 48-hour grace period, the privacy policy says a clean-up every six months with backups three months later, and the April 2026 changelog entry says content can be kept up to 50 days (18). The terms commit to a six-month deprecation period after a service announcement, with no dated notices to check it against (16). Six data centre regions are named with their hosts, and Zoho publishes a sub-processor directory by service that loads by script and that we couldn't read (15).

Security & auth Zoho CPaaS (formerly ZeptoMail) +10

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).

Zoho CPaaS (formerly ZeptoMail) 78

Send keys are per Agent and per channel, can be created, listed and deleted by API, and can only send and upload attachments. Management calls use Zoho OAuth 2.0 with READ, CREATE, UPDATE and DELETE scopes per resource and one-hour access tokens. That earns 30, less 10 because the OAuth guide documents the client secret and refresh token in the token URL's query string (20). Read-only scopes, send-only keys, sandbox Agents and IP allow lists for sending, the REST API and the web console. No approval step for deletes (15). No inbound mail, so responses hold only the account's own logs and settings (10). Activity logs per user kept one year with export, and email logs for 60 days that show the triggering IP (13). security.txt valid until 30 June 2028 naming security@zohocorp.com and Zoho's bug bounty, and SOC 2 Type II and ISO/IEC 27001 on Zoho's compliance page, the same evidence zoho-crm, zoho-desk and zoho-books score 20 on. The 2 points held back on 8 October for no advisory feed aren't a checklist condition the other Zoho listings apply (20).

Payments & pricing Mailchimp Transactional (Mandrill) +8

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.

Zoho CPaaS (formerly ZeptoMail) 45

No x402, MPP or L402 (0). The pricing page and its Markdown copy state per-unit email pricing without a login (10,000 emails per credit, valid six months, counted per recipient, a dedicated IP priced by the month), but the figures are filled in by script from a data file. The 8 October price figures came from that file, a script data feed this run doesn't call, so they are struck and the amounts are unchecked. The same page renders worked prices for two other channels of the API without a script (WhatsApp, an authentication message to the US at US$0.0374 with credits at US$2, and voice credits at US$1), so pricing is public in part, with the email amount unread (10 of 20, as pirate-weather's partly public pricing). "First credit is free" on the pricing page, and the documented signup asks for a phone verification and no payment details (20). Signup is a browser form with phone verification, and Zoho staff review each new account, so there is no autonomous route (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Agent ergonomics Mailchimp Transactional (Mandrill) +5

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).

Zoho CPaaS (formerly ZeptoMail) 55

Send responses are small, and the logs endpoint takes offset and limit, with no field selection (15). Thirteen filters on email logs, among them recipient, subject, date range, client_reference and bounce or delivery state (16). Errors carry a code, a sub-code and a message, and the docs pair each with a fix (16). No idempotency key and no guidance on retrying a send (0). A send needs only from, to and subject. The one official SDK found is for Node, and managing the account needs a second credential type (8).

Score by category

CategoryWeightMailchimp Transactional (Mandrill)Zoho CPaaS (formerly ZeptoMail)Edge
Reliability16%7041Mailchimp Transactional (Mandrill) +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7978Mailchimp Transactional (Mandrill) +1
Agent ergonomics13%6055Mailchimp Transactional (Mandrill) +5
Security & auth14%6878Zoho CPaaS (formerly ZeptoMail) +10
Payments & pricing10%5345Mailchimp Transactional (Mandrill) +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2844Zoho CPaaS (formerly ZeptoMail) +16
Transparency & trust7%7182Zoho CPaaS (formerly ZeptoMail) +11
Negative events≤1500
TotalB 63.8/100C 60.1/100

Facts side by side

FactMailchimp Transactional (Mandrill)Zoho CPaaS (formerly ZeptoMail)
KindHTTP APIHTTP API
VendorIntuit MailchimpZoho
Hosted endpointhttps://mandrillapp.com/api/1.4https://cpaas.zoho.com/v1.1
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPaidPay per use
x402nono
LicenceProprietary service under Mailchimp's Standard Terms of Use and Additional Terms. The client libraries are under Mailchimp's own client library licence agreementProprietary service under the Zoho CPaaS terms of use. The Node SDK on npm is MIT
Tools exposed9none
Read-only variant documentednono
llms.txtyesyes
Last release2026-03-242026-09-28
Terms last updatedno date givenno date given
Privacy policy last updated2026-03-092025-12-22
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity226k npm/wk, 132k PyPI/wk40k npm/wk
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

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.

Zoho CPaaS (formerly ZeptoMail)

A public OpenAPI 3.0 file covers all 42 operations, each Agent has its own send-only key, and email is prepaid per 10,000 with the first credit free. No API rate limit, 429 handling, idempotency key or SLA was found in the reviewed documentation, and new accounts wait for a manual review.

Before you call either

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

Zoho CPaaS (formerly ZeptoMail)

  1. Call the base URL for the account's region (cpaas.zoho.com, .eu, .in, .com.au, .jp or .com.cn). A key from one region fails on another
  2. Send with Authorization: Zoho-enczapikey <key>. Logs, domains, templates, agents and suppressions need a Zoho OAuth token as Authorization: Zoho-oauthtoken <token>
  3. Post OAuth client secrets and refresh tokens in the request body, not the query string the guide shows, so they stay out of logs
  4. Don't retry a timed-out send blindly. There is no idempotency key, so look the message up by client_reference in the email logs first
  5. Count one email per recipient, including cc and bcc, and keep each address field to 500 entries and each attachment to 15 MB
  6. Use a sandbox Agent for tests. It accepts up to 10,000 emails a day and sends none of them

Questions

Which is better for AI agents, Mailchimp Transactional (Mandrill) or Zoho CPaaS (formerly ZeptoMail)?

Mailchimp Transactional (Mandrill) scores 63.8 (B) on agent readiness against Zoho CPaaS (formerly ZeptoMail)'s 60.1 (C), and leads in 4 of 7 scored categories. Zoho CPaaS (formerly ZeptoMail) leads on security & auth, maintenance & community and transparency & trust.

Do Mailchimp Transactional (Mandrill) and Zoho CPaaS (formerly ZeptoMail) need an API key?

Mailchimp Transactional (Mandrill) needs an API key. Zoho CPaaS (formerly ZeptoMail) takes an API key or an OAuth sign-in.

Can an agent call Mailchimp Transactional (Mandrill) and Zoho CPaaS (formerly ZeptoMail) without installing anything?

Yes. Mailchimp Transactional (Mandrill) has a hosted endpoint at https://mandrillapp.com/api/1.4 and Zoho CPaaS (formerly ZeptoMail) at https://cpaas.zoho.com/v1.1.

Other comparisons with Mailchimp Transactional (Mandrill) or Zoho CPaaS (formerly ZeptoMail)

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.