Head to head · Email send · October 2026 research run

MailerSend vs Zoho CPaaS (formerly ZeptoMail)

MailerSend scores 69.5 (B) on agent readiness against Zoho CPaaS (formerly ZeptoMail)'s 61.8 (C), and leads in 3 of 7 scored categories. Zoho CPaaS (formerly ZeptoMail) leads on schema & documentation, security & auth, payments & pricing and transparency & trust. Both do email send.

Which one, for what

MailerSend B

Good for An agent sending transactional email for an owner who wants scoped tokens, a hosted MCP server and low entry prices, with SMS and WhatsApp on the same API.

Ahead on

  • Reliability, 95 against 41
  • Agent ergonomics, 69 against 55
  • Maintenance & community, 83 against 74

Watch for

No idempotency key documented for POST /v1/email or the bulk endpoint

Zoho CPaaS (formerly ZeptoMail) C

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

Ahead on

  • Schema & documentation, 78 against 73
  • Security & auth, 76 against 62
  • Payments & pricing, 40 against 30
  • Transparency & trust, 82 against 64

Watch for

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

Score by category

CategoryWeight this runMailerSendZoho CPaaS (formerly ZeptoMail)Edge
Reliability16%209541MailerSend +54
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27378Zoho CPaaS (formerly ZeptoMail) +5
Agent ergonomics13%16.26955MailerSend +14
Security & auth14%17.56276Zoho CPaaS (formerly ZeptoMail) +14
Payments & pricing10%12.53040Zoho CPaaS (formerly ZeptoMail) +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88374MailerSend +9
Transparency & trust7%8.86482Zoho CPaaS (formerly ZeptoMail) +18
Negative events≤1500
Total69.5 · B61.8 · C

Facts side by side

FactMailerSendZoho CPaaS (formerly ZeptoMail)
KindHTTP APIHTTP API
VendorMailerSend, Inc.Zoho Corporation
Hosted endpointhttps://api.mailersend.com/v1https://cpaas.zoho.com/v1.1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
Price for email send$4 per month (plan)not published
x402nono
LicenceProprietary service under MailerSend's terms of use. The SDKs and the CLI on GitHub are MITProprietary service under the Zoho CPaaS terms of use. The Node SDK on npm is MIT
Tools exposed127none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-29none
Terms last updated2026-10-05no date given
Privacy policy last updated2026-09-172025-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
Popularity175 stars, 128k npm/wk, 15k PyPI/wk40k npm/wk

Verdicts

MailerSend

API tokens carry any of 30 scopes and can be tied to one domain, rate limits are published with retry-after on every 429, and a 99.5 per cent SLA starts on the $35 Starter plan. Sends take no idempotency key, the Free plan allows 100 API requests a day, and the terms permit changes without notice.

Zoho CPaaS (formerly ZeptoMail)

A public OpenAPI 3.0 file covers all 42 operations, and each Agent has its own send-only key. Email costs $2.50 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

MailerSend

  1. Send Authorization: Bearer <token> to https://api.mailersend.com/v1 and ask for a token with only the scopes the task needs, such as email_full and activity_read
  2. Read the message id from the x-message-id response header. POST /v1/email answers 202 with an empty body
  3. Check for a sent message before retrying a send. No idempotency key exists, so a blind retry can deliver twice
  4. On a 429 wait the seconds in retry-after. Call GET /v1/api-quota, which isn't counted, to see the daily quota left
  5. Use POST /v1/bulk-email for batches of up to 500 emails. It isn't on the Free plan and takes 10 to 60 requests a minute by plan

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, MailerSend or Zoho CPaaS (formerly ZeptoMail)?

MailerSend scores 69.5 (B) on agent readiness against Zoho CPaaS (formerly ZeptoMail)'s 61.8 (C), and leads in 3 of 7 scored categories. Zoho CPaaS (formerly ZeptoMail) leads on schema & documentation, security & auth, payments & pricing and transparency & trust.

Do MailerSend and Zoho CPaaS (formerly ZeptoMail) need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call MailerSend and Zoho CPaaS (formerly ZeptoMail) without installing anything?

Yes. MailerSend has a hosted endpoint at https://api.mailersend.com/v1 and Zoho CPaaS (formerly ZeptoMail) at https://cpaas.zoho.com/v1.1.

Other comparisons with MailerSend 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.