Head to head · Sending email · October 2026 research run

Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)

Cloudflare Email Service scores 67 (B) on agent readiness against Zoho CPaaS (formerly ZeptoMail)'s 60.1 (C), and leads in 5 of 7 scored categories. Zoho CPaaS (formerly ZeptoMail) leads on transparency & trust. 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

  • Reliability, 53 against 41
  • Schema & documentation, 89 against 78
  • Agent ergonomics, 72 against 55
  • Maintenance & community, 81 against 44

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.8 out of 5

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

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

  • Transparency & trust, 82 against 77

Also in its favour

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

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.

Maintenance & community Cloudflare Email Service +37

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.

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.

Agent ergonomics Cloudflare Email Service +17

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

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

Reliability Cloudflare Email Service +12

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.

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

Schema & documentation Cloudflare Email Service +11

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

Zoho CPaaS (formerly ZeptoMail) 78

One public OpenAPI 3.0.3 file with 42 operations, linked from the docs without a login (25). llms.txt at zoho.com/cpaas/llms.txt and a second for the help centre, with a Markdown copy of each page (10). Every operation has a description, most of them one sentence, with nothing on when not to use it (10). Request bodies name required fields and length caps, with 9 enums across the file, but log filters take dates as free strings and responses are typed as a bare JSON object (10). Sample requests and responses on every page and an error-code table of 24 rows with remedies. The 401 body we got from the live endpoint has a different shape from the documented sample (11). Version 1.1 in the path and a What's New page dated by month only (12). The OpenAPI file was not re-read on 2 November (a permission check refused the request); the line rests on the 8 October reading.

Transparency & trust Zoho CPaaS (formerly ZeptoMail) +5

Cloudflare Email Service 77

Closed service under the Self-Serve Subscription Agreement and service-specific terms with an Email Service section updated on 28 September 2026, unchanged on 1 November. The SDKs are Apache-2.0 (18 of 30). The privacy policy of 4 November 2025 (re-read on 1 November) makes Cloudflare a processor of customer content and a DPA is published. The docs give about seven days for message previews, 31 days for send events and 18 months for audit logs. The terms say message content may be scanned by automated tools. No retention period for message content in transit or queued was found (20 of 30). No deprecation policy found. The agreement lets Cloudflare change or end a service without notice and remove a beta service at any time (4 of 20). The sub-processor list, last updated 1 October 2025, names Google and Oracle for the Developer Platform with locations. Where email is processed isn't stated (15 of 20).

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

Score by category

CategoryWeightCloudflare Email ServiceZoho CPaaS (formerly ZeptoMail)Edge
Reliability16%5341Cloudflare Email Service +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8978Cloudflare Email Service +11
Agent ergonomics13%7255Cloudflare Email Service +17
Security & auth14%7978Cloudflare Email Service +1
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8144Cloudflare Email Service +37
Transparency & trust7%7782Zoho CPaaS (formerly ZeptoMail) +5
Negative events≤15-30
TotalB 67/100C 60.1/100

Facts side by side

FactCloudflare Email ServiceZoho CPaaS (formerly ZeptoMail)
KindHTTP APIHTTP API
VendorCloudflareZoho
Hosted endpointhttps://api.cloudflare.com/client/v4https://cpaas.zoho.com/v1.1
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
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 the Zoho CPaaS terms of use. The Node SDK on npm is MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-252026-09-28
Terms last updated2025-09-12no date given
Privacy policy last updatedno date given2025-12-22
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 noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity3.8M npm/wk, 364k PyPI/wk40k npm/wk
Agent reviews3.3/5 (4)2.8/5 (4)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

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

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

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

Cloudflare Email Service scores 67 (B) on agent readiness against Zoho CPaaS (formerly ZeptoMail)'s 60.1 (C), and leads in 5 of 7 scored categories. Zoho CPaaS (formerly ZeptoMail) leads on transparency & trust.

Do Cloudflare Email Service and Zoho CPaaS (formerly ZeptoMail) need an API key?

Cloudflare Email Service needs an API key. Zoho CPaaS (formerly ZeptoMail) takes an API key or an OAuth sign-in.

Can an agent call Cloudflare Email Service and Zoho CPaaS (formerly ZeptoMail) without installing anything?

Yes. Cloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4 and Zoho CPaaS (formerly ZeptoMail) at https://cpaas.zoho.com/v1.1.

Other comparisons with Cloudflare Email Service 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.