{ "data": { "a": { "slug": "cloudflare-email-service", "name": "Cloudflare Email Service", "vendor": "Cloudflare", "vendorUrl": "https://developers.cloudflare.com/email-service/", "kind": "http-api", "category": "email", "summary": "Cloudflare Email Service sends transactional email through a REST API, a Workers binding or SMTP, and routes inbound mail to Workers or verified addresses. Email Sending is in public beta and needs the Workers Paid plan for arbitrary recipients.", "url": "https://www.anchorterminal.com/tools/cloudflare-email-service", "markdownUrl": "https://www.anchorterminal.com/tools/cloudflare-email-service.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cloudflare-email-service.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json", "dns": "cloudflare-email-service.grade.anchorterminal.com", "license": "Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official `cloudflare` SDK on npm is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://api.cloudflare.com/client/v4", "packages": [ { "registry": "npm", "name": "cloudflare" }, { "registry": "pypi", "name": "cloudflare" } ], "auth": "api-key", "authNotes": "A Cloudflare API token as a Bearer header, created by the account owner in the dashboard. The SMTP guide names the permission Email Sending: Edit, and the OpenAPI file lists `com.cloudflare.api.account.email.sending.create` for sends and `.read` for limits and reputation. Tokens can carry an expiry and an IP address filter. The same token is the SMTP password. The OpenAPI file also accepts the legacy global API key. Access is self-serve, but the sending domain must be on Cloudflare DNS and new accounts start with a daily quota that Cloudflare raises over time.", "pricing": "usage", "pricingNotes": "$0.35 per 1,000 outbound emails after 3,000 included a month, on the Workers Paid plan (minimum $5 a month). Sending to arbitrary recipients is not available on Workers Free. Sends to the account's own verified destination addresses are free on every plan, and inbound Email Routing is free and unmetered. Hard bounces count towards the quota. Sends rejected at the API boundary or by the suppression list don't (https://developers.cloudflare.com/email-service/platform/pricing/).", "priceSummary": "$5 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Email Service docs, the pricing page or the Email Sending paths of the OpenAPI file (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 3766696, "pypiWeekly": 363923, "asOf": "2026-10-08" }, "docsUrl": "https://developers.cloudflare.com/email-service/", "llmsTxt": "https://developers.cloudflare.com/email-service/llms.txt", "openapi": "https://raw.githubusercontent.com/cloudflare/api-schemas/main/openapi.json", "capabilities": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "tags": [ "hosted", "usage", "beta", "openapi", "llms-txt", "smtp", "typescript", "python", "go", "graphql", "status-page", "bug-bounty" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 65.2, "grade": "B", "agentReady": false, "rank": 425, "ranked": true, "rankOf": 1486, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 81, "payments": 30, "reliability": 53, "schema": 89, "security": 79, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "25 September 2026, -3. The `cloudflare` SDKs in the listing's packages shipped changes they label breaking in minor releases with no advance notice found. TypeScript 7.2.0 and Python 5.8.0 changed `emailRouting.dns.delete()` to return Settings in place of a page of DNS records and removed the `body` parameter from `emailRouting.enable()` and `disable()`. The migration guide came with the release (https://github.com/cloudflare/cloudflare-python/blob/main/CHANGELOG.md)" ], "verdict": "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.", "bestFor": "Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.", "strengths": [ "Public OpenAPI 3.0.3 file with 29 Email Sending and 46 Email Routing operations, plus llms.txt and a Markdown copy of every docs page", "$0.35 per 1,000 emails after 3,000 included a month on Workers Paid. Sends rejected at the API boundary or blocked by the suppression list don't count", "API tokens carry separate send and read permissions, an optional expiry and an IP address filter, and Workers bindings can be limited to named senders and recipients", "The Cloudflare API returns 429 with `retry-after` and `Ratelimit` headers, and the send endpoint has its own throttled error code 10004", "Email Sending and Email Routing are separate components on cloudflarestatus.com, and both components showed no incident in the status feed from 16 to 31 October 2026" ], "weaknesses": [ "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", "No idempotency key on `/email/sending/send`, in the docs or the OpenAPI file", "The daily sending quota for new accounts is described as conservative with no number. It can be read per account from `/email/sending/limits`", "The sending domain must use Cloudflare DNS, and sending to arbitrary recipients needs the Workers Paid plan at $5 a month", "A token with the send permission can send from every onboarded domain on the account. No per-domain token scope was found", "No template storage, and the terms and FAQ allow transactional email only", "The `cloudflare` SDKs shipped labelled breaking changes to Email Routing methods in minor releases on 25 September 2026 with no advance notice" ], "agentNotes": [ "POST to `https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send` with `Authorization: Bearer \u003ctoken\u003e`. The body needs `to`, `from`, `subject` and one of `html` or `text`", "Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the `emailSendingAdaptive` GraphQL dataset first", "On 429 (code 10004) wait for the `retry-after` header. On 409 `sending_not_ready` the domain setup is unfinished and nothing was sent", "Read `result.delivered`, `result.queued` and `result.permanent_bounces` in the response. A 200 does not mean every recipient was accepted", "Keep to 50 recipients across to, cc and bcc, and 25 MiB per message including attachments", "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", "By default one suppressed recipient fails the whole send. Turn on Drop suppressed recipients for the domain to send to the rest" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.2 } ], "editorialScores": { "ergonomics": 72, "maintenance": 81, "payments": 30, "reliability": 53, "schema": 89, "security": 79, "transparency": 57 }, "provenanceScore": 96, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send\" \\\n --header \"Authorization: Bearer \u003cAPI_TOKEN\u003e\" \\\n --header \"Content-Type: application/json\" \\\n --data '{\"to\":\"recipient@example.com\",\"from\":\"welcome@yourdomain.com\",\"subject\":\"Welcome to our service!\",\"html\":\"\u003ch1\u003eWelcome!\u003c/h1\u003e\u003cp\u003eThanks for signing up.\u003c/p\u003e\",\"text\":\"Welcome! Thanks for signing up.\"}'" }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/cloudflare-email-service" }, "sameCompany": [ "cloudflare-ai-gateway", "cloudflare-workers-ai", "cloudflare-sandbox-sdk", "cloudflare-workers-oauth-provider", "cloudflare-web-search", "cloudflare-clairic", "cloudflare-ai-search", "cloudflare-cli", "cloudflare-mcp", "cloudflare-r2", "cloudflare-clef" ], "area": "communication", "unitPrices": [ { "item": "Outbound email", "unit": "1k-emails", "usd": 0.35, "note": "After 3,000 included a month, Workers Paid plan only. Sends to verified destination addresses are free" }, { "item": "Workers Paid plan", "unit": "month", "usd": 5, "note": "Minimum monthly charge for the plan that Email Sending to arbitrary recipients needs" } ], "provenance": { "legalEntity": "Cloudflare, Inc.", "domain": "cloudflare.com", "domainRegistered": "2009-02-17", "endpointOnVendorDomain": true, "terms": "https://www.cloudflare.com/terms/", "privacy": "https://www.cloudflare.com/privacypolicy/", "statusPage": "https://www.cloudflarestatus.com", "changelog": "https://developers.cloudflare.com/changelog/product/email-service/", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "Terms are the Self-Serve Subscription Agreement, last updated 12 September 2025, which names Cloudflare, Inc. at 101 Townsend St, San Francisco. Its section 5 covers beta services.", "The Developer Platform service-specific terms (https://www.cloudflare.com/service-specific-terms-developer-platform/), last updated 28 September 2026, have their own sections for Cloudflare Email Service and Email Routing and supplement the agreement.", "The privacy policy is effective from 4 November 2025 and makes Cloudflare a data processor for customer content that crosses its network. A customer DPA is at https://www.cloudflare.com/cloudflare-customer-dpa/.", "www.cloudflare.com/.well-known/security.txt, re-read on 1 November 2026, names HackerOne and a disclosure policy and has no Expires field. It is recorded as valid to match the other Cloudflare listings.", "The REST endpoint is on api.cloudflare.com. The SMTP endpoint is on smtp.mx.cloudflare.net, a different registered domain.", "The status page lists Email Sending and Email Routing as separate components, both operational on 1 November 2026.", "RDAP for cloudflare.com gives a registration date of 2009-02-17." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cloudflare-email-service.json", "live": { "slug": "cloudflare-email-service", "probe": { "target": "https://api.cloudflare.com/client/v4", "method": "get", "lastAt": "2026-11-07T18:20:17.937782363Z", "lastOk": true, "lastStatus": 404, "lastMs": 61, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 37, "p95ms24h": 97, "samples24h": 239, "samples30d": 7420, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://www.cloudflarestatus.com", "indicator": "major", "summary": "Partial System Outage", "checkedAt": "2026-11-07T18:20:43.696161926Z" }, "versions": [ { "registry": "npm", "name": "cloudflare", "version": "7.3.0", "seenAt": "2026-11-06T23:15:47.285388648Z" }, { "registry": "pypi", "name": "cloudflare", "version": "5.10.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:15:47.318174532Z" } ], "npmWeekly": 4306549, "pypiWeekly": 584250, "securityTxt": { "url": "https://cloudflare.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:23.467095484Z" }, "llmsTxt": { "url": "https://developers.cloudflare.com/email-service/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:00.977057403Z" }, "domain": { "domain": "cloudflare.com", "registered": "2009-02-17", "source": "https://rdap.verisign.com/com/v1/domain/cloudflare.com", "checkedAt": "2026-11-01T14:18:56.122446983Z" }, "pages": [ { "url": "https://developers.cloudflare.com/changelog/product/email-service/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:04:00.748163747Z", "changedAt": "2026-11-07T14:04:00.748163747Z", "fingerprint": "db92509386da" }, { "url": "https://developers.cloudflare.com/email-service/platform/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:04:08.818558342Z", "changedAt": "2026-10-15T21:23:51.47765183Z", "fingerprint": "6b2b078d1df0" } ], "updatedAt": "2026-11-07T18:20:17.937782363Z" } }, "answer": "Cloudflare Email Service scores 65.2 (B) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on reliability.", "b": { "slug": "mailpace", "name": "MailPace", "vendor": "OhMySMTP Ltd", "vendorUrl": "https://mailpace.com", "kind": "http-api", "category": "email", "summary": "MailPace is a UK transactional email service, formerly OhMySMTP, hosted in the EU. It sends mail through an HTTPS API or SMTP, turns inbound mail into webhooks and has a Domains and Email Status API.", "url": "https://www.anchorterminal.com/tools/mailpace", "markdownUrl": "https://www.anchorterminal.com/tools/mailpace.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mailpace.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mailpace.json", "dns": "mailpace.grade.anchorterminal.com", "repo": "https://github.com/mailpace/mailpace-mcp", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@mailpace/mailpace.js" } ], "auth": "api-key", "authNotes": "Each domain has its own server token, sent in the `MailPace-Server-Token` header, which can send from that domain and read its email status. An organisation token in `MailPace-Organization-Token` manages domains and domain tokens through the Domains API, including revoking them. Both are made in the dashboard after a browser signup.", "pricing": "paid", "pricingNotes": "$10 a month includes 10,000 emails sent or received, then $1 per 1,000, per the Paddle prices the pricing page loads and the comparison pages ($100 for 100,000, $1,000 for 1 million). A free plan of up to 100 emails a month is given on request by email. Paddle is the merchant of record; card, PayPal, Apple Pay or Google Pay.", "priceSummary": "$10 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs repository, the pricing page or the MCP server source (checked 2026-11-06). Payment is by Paddle subscription; the FAQ says crypto isn't accepted.", "endpoints": [] }, "toolCount": 12, "popularity": { "githubStars": 1, "npmWeekly": 207, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.mailpace.com/", "capabilities": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "tags": [ "hosted", "closed-source", "smtp", "webhooks", "idempotency", "status-page", "sla", "eu", "mcp", "typescript", "ruby", "go", "php" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 58.4, "grade": "C", "agentReady": false, "rank": 750, "ranked": true, "rankOf": 1486, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 65, "payments": 25, "reliability": 70, "schema": 54, "security": 50, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.", "bestFor": "Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.", "strengths": [ "Sends accept an `Idempotency-Key` header kept for 24 hours, so a retry after a timeout doesn't send twice", "Per-domain server tokens limit a leaked key to one domain, and organisation tokens can create and revoke them by API", "Webhooks are signed with Ed25519 and inbound mail is retried five times before it fails", "Status page on Upptime with GitHub issues as incident reports, and a 99% monthly availability promise with credits in the terms", "Sub-processors and their locations are listed, and mail is kept 30 days plus 7 in backups per the DPA" ], "weaknesses": [ "No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages", "Rate limits aren't published; the docs say they vary by organisation age, plan and history", "No free plan without emailing support, and the paid plan starts at $10 a month", "MCP server 2.0.0 exists only in the repository; npm and the MCP registry had nothing for it on 6 November 2026", "No security.txt, disclosure policy or certification found" ], "agentNotes": [ "Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token", "Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403", "On 429 `You are sending emails too quickly` back off; no Retry-After is documented", "Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms", "Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.4 } ], "editorialScores": { "ergonomics": 71, "maintenance": 65, "payments": 25, "reliability": 70, "schema": 54, "security": 50, "transparency": 69 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://app.mailpace.com/api/v1/send -X POST -H \"Accept: application/json\" -H \"Content-Type: application/json\" -H \"MailPace-Server-Token: $MAILPACE_TOKEN\" -H \"Idempotency-Key: $(uuidgen)\" -d '{\"from\":\"you@yourdomain.com\",\"to\":\"person@example.com\",\"subject\":\"Hello\",\"textbody\":\"Hello\"}'" }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/mailpace" }, "area": "communication", "unitPrices": [ { "item": "Scaling plan", "unit": "month", "usd": 10, "note": "includes 10,000 emails sent or received" }, { "item": "Emails beyond 10,000", "unit": "1k-emails", "usd": 1 } ], "provenance": { "legalEntity": "OhMySMTP Ltd", "domain": "mailpace.com", "domainRegistered": "2022-01-10", "endpointOnVendorDomain": true, "terms": "https://mailpace.com/terms", "privacy": "https://mailpace.com/privacy", "statusPage": "https://status.mailpace.com", "changelog": "https://mailpace.com/category/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms and privacy policy name OhMySMTP Ltd, incorporated in England and Wales, company number 13200428. Companies House lists two active directors.", "Terms last updated 9 January 2026, privacy policy 30 August 2026, DPA updated in October 2026 per the landing repository.", "mailpace.com/robots.txt allows all paths. The terms contain no clause on automated access to the website beyond the usual licence limits.", "RDAP gives mailpace.com a registration date of 10 January 2022; the service ran as OhMySMTP before that.", "/.well-known/security.txt returns 404 on mailpace.com and app.mailpace.com." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mailpace.json", "live": { "slug": "mailpace", "vendorStatus": { "page": "https://status.mailpace.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:01.553362214Z" }, "versions": [ { "registry": "npm", "name": "@mailpace/mailpace.js", "version": "0.1.3", "seenAt": "2026-11-06T23:42:02.752996422Z" } ], "githubStars": 1, "npmWeekly": 207, "securityTxt": { "url": "https://mailpace.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:07.630537329Z" }, "pages": [ { "url": "https://mailpace.com/category/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:13:40.841899008Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "38f92a159d1b" }, { "url": "https://mailpace.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:45.28058492Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e6b0fea49c1d" }, { "url": "https://mailpace.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:45.480605157Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "24f1eed01dad" } ], "updatedAt": "2026-11-07T16:01:07.630537329Z" } }, "edges": [ { "by": 35, "category": "schema", "leads": "cloudflare-email-service", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "No OpenAPI or other machine-readable contract for the HTTPS API. The MCP server's 12 tools have typed zod inputs and output schemas, but that server isn't published yet, so partial credit (8 of 25). llms.txt answers 404 on mailpace.com and docs.mailpace.com, and no Markdown copies are served (0). The reference states what each endpoint does, and the introduction says when not to use it (transactional only, no batch, no static IPs) (12 of 20). Field tables give type, examples and required or optional, with enums for status, sort and direction and the 50-recipient cap in text (9 of 15). Examples in curl and six languages and a full table of error responses with messages, though several listed messages have a broken quote (`{\"error:\"...`) and the send reference says 30 MB where the home page says 25 MB (12 of 15). Version in the path with a promise that an old version runs until a published end-of-life date, and dated changelog posts (13 of 15). Total 54." }, "scores": { "a": 89, "b": 54 } }, { "by": 29, "category": "security", "leads": "cloudflare-email-service", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Per-domain server tokens that can only send from and read status for their domain, and an organisation token that creates, renames and revokes domain tokens through the Domains API. Tokens travel in headers only. The authentication page still tells users to contact support to regenerate a leaked token (25 of 30). No read-only token. A domain token can't touch other domains, and the unpublished MCP server has an optional recipient allowlist. No approval step on the hosted API (8 of 20). Inbound mail reaches the customer's webhook as untrusted content, and Email Status returns bounce text. The MCP README warns about prompt injection and suggests the allowlist (9 of 15). The dashboard keeps sent mail for 30 days; no log of API calls was found (6 of 15). No security.txt (404 on mailpace.com and app.mailpace.com), no disclosure policy, bug bounty, SOC 2 or ISO 27001. WebAuthn-only two-factor sign-in and Ed25519-signed webhooks are documented (2 of 20). Total 50." }, "scores": { "a": 79, "b": 50 } }, { "by": 17, "category": "reliability", "leads": "mailpace", "name": "Reliability", "reasons": { "a": "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.", "b": "Graded with the hosted lines. A public Upptime status page at status.mailpace.com, driven by the mailpace/status repository, with monitors for the application, SMTP, docs, blog and landing page and GitHub issues as incident reports (20). The 90 days from 8 August hold two incidents, an application outage on 22 September 2026 that the operator put down to an upstream provider returning 5xx (issue open for two minutes), and SMTP down on 2 November 2026 for about 35 minutes, which leaves SMTP at 99.65% for the week. Minor incidents only (20). No rate limit numbers are published; the docs say limits vary by organisation age, plan and history (0). A documented 429 with its message, no Retry-After or backoff guidance, and an `Idempotency-Key` on sends with written retry rules (10 of 15). The terms guarantee 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes (10). The API is at v1 with no beta label (10). Total 70." }, "scores": { "a": 53, "b": 70 } }, { "by": 16, "category": "maintenance", "leads": "cloudflare-email-service", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Email Status API documented on 22 October 2026, and the MCP server rewritten as 2.0.0 on 4 November 2026, two days before this check (30). In the 90 days from 8 August, the Q3 changelog post of 31 August, the Email Status docs of 22 October, a mailpace-rails push on 17 October and the MCP rewrite, but only one changelog post (15 of 20). A closed service with email support. Three pull requests to the MCP repository from 2025 have no reply (8 of 15). Not in the official MCP registry (search for mailpace returned nothing on 6 November). The Node library was last pushed in October 2024 and Go in January 2024, while mailpace-rails is current (7 of 15). The MCP server gained CI with tests on 4 November; the older SDKs weren't checked for CI (5 of 10). Total 65." }, "scores": { "a": 81, "b": 65 } }, { "by": 5, "category": "payments", "leads": "cloudflare-email-service", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "No x402, MPP or L402 (0). $10 a month for 10,000 emails and $1 per 1,000 after, loaded from Paddle on the pricing page and stated in the comparison pages' tables without login (20). A free plan of up to 100 emails a month is available only by emailing support, so it isn't self-serve (5 of 20). Signup, DKIM verification and payment happen in a browser (0). Total 25." }, "scores": { "a": 30, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Cloudflare", "b": "OhMySMTP Ltd", "name": "Vendor" }, { "a": "https://api.cloudflare.com/client/v4", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official `cloudflare` SDK on npm is Apache-2.0", "b": "none", "name": "Licence" }, { "a": "none", "b": "12", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-25", "b": "2026-10-22", "name": "Last release" }, { "a": "2025-09-12", "b": "2026-01-09", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-08-30", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3.8M npm/wk, 364k PyPI/wk", "b": "1 stars, 207 npm/wk", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Cloudflare Email Service scores 65.2 (B) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on reliability.", "question": "Which is better for AI agents, Cloudflare Email Service or MailPace?" }, { "answer": "Both need an API key.", "question": "Do Cloudflare Email Service and MailPace need an API key?" }, { "answer": "Cloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4. No hosted endpoint is listed for MailPace.", "question": "Can an agent call Cloudflare Email Service and MailPace without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 89 against 54", "Security \u0026 auth, 79 against 50", "Payments \u0026 pricing, 30 against 25", "Maintenance \u0026 community, 81 against 65" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.", "slug": "cloudflare-email-service", "watchFor": "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" }, { "aheadOn": [ "Reliability, 70 against 53" ], "also": [ "No incidents deducted, where Cloudflare Email Service loses 3 points for them" ], "goodFor": "Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.", "slug": "mailpace", "watchFor": "No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages" } ], "history": { "cloudflare-email-service": [ { "causes": [ "evidence", "correction", "event" ], "date": "2026-11-01", "delta": -2.2, "from": 67.4, "fromGrade": "B", "to": 65.2, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 67.3, "fromGrade": "B", "to": 67.4, "toGrade": "B" } ], "mailpace": null }, "job": { "capability": "email.send", "name": "Sending email" }, "others": [ { "json": "https://www.anchorterminal.com/compare/ahasend-vs-cloudflare-email-service.json", "title": "AhaSend API + MCP vs Cloudflare Email Service", "url": "https://www.anchorterminal.com/compare/ahasend-vs-cloudflare-email-service" }, { "json": "https://www.anchorterminal.com/compare/ahasend-vs-mailpace.json", "title": "AhaSend API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/ahasend-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.json", "title": "Amazon SES vs Cloudflare Email Service", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.json", "title": "Amazon SES vs MailPace", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service.json", "title": "Brevo API + MCP vs Cloudflare Email Service", "url": "https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service" }, { "json": "https://www.anchorterminal.com/compare/brevo-vs-mailpace.json", "title": "Brevo API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/brevo-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-groundmail.json", "title": "Cloudflare Email Service vs Groundmail API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-groundmail" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops.json", "title": "Cloudflare Email Service vs Loops API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend.json", "title": "Cloudflare Email Service vs MailerSend", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun.json", "title": "Cloudflare Email Service vs Mailgun API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet.json", "title": "Cloudflare Email Service vs Mailjet API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.json", "title": "Cloudflare Email Service vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill.json", "title": "Cloudflare Email Service vs Mailchimp Transactional (Mandrill)", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark.json", "title": "Cloudflare Email Service vs Postmark API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend.json", "title": "Cloudflare Email Service vs Resend API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid.json", "title": "Cloudflare Email Service vs Twilio SendGrid", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendlayer.json", "title": "Cloudflare Email Service vs SendLayer", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go.json", "title": "Cloudflare Email Service vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.json", "title": "Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail" }, { "json": "https://www.anchorterminal.com/compare/groundmail-vs-mailpace.json", "title": "Groundmail API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/groundmail-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/loops-vs-mailpace.json", "title": "Loops API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/loops-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailersend-vs-mailpace.json", "title": "MailerSend vs MailPace", "url": "https://www.anchorterminal.com/compare/mailersend-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailgun-vs-mailpace.json", "title": "Mailgun API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/mailgun-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailjet-vs-mailpace.json", "title": "Mailjet API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/mailjet-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.json", "title": "MailPace vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-mandrill.json", "title": "MailPace vs Mailchimp Transactional (Mandrill)", "url": "https://www.anchorterminal.com/compare/mailpace-vs-mandrill" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-postmark.json", "title": "MailPace vs Postmark API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-postmark" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-resend.json", "title": "MailPace vs Resend API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-resend" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.json", "title": "MailPace vs Twilio SendGrid", "url": "https://www.anchorterminal.com/compare/mailpace-vs-sendgrid" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.json", "title": "MailPace vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailpace-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.json", "title": "MailPace vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.json", "title": "MailPace vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail" } ], "panel": null, "scores": [ { "by": 17, "cloudflare-email-service": 53, "edge": "mailpace", "key": "reliability", "mailpace": 70, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 35, "cloudflare-email-service": 89, "edge": "cloudflare-email-service", "key": "schema", "mailpace": 54, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 1, "cloudflare-email-service": 72, "edge": "cloudflare-email-service", "key": "ergonomics", "mailpace": 71, "name": "Agent ergonomics", "weight": 13 }, { "by": 29, "cloudflare-email-service": 79, "edge": "cloudflare-email-service", "key": "security", "mailpace": 50, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "cloudflare-email-service": 30, "edge": "cloudflare-email-service", "key": "payments", "mailpace": 25, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "cloudflare-email-service": 81, "edge": "cloudflare-email-service", "key": "maintenance", "mailpace": 65, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 2, "cloudflare-email-service": 77, "edge": "cloudflare-email-service", "key": "transparency", "mailpace": 75, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Cloudflare Email Service scores 65.2 (B) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on reliability. Both do sending email.", "tasks": null, "tutorials": [], "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.", "mailpace": "A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace", "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.min.md" }, "markdown": "Cloudflare Email Service scores 65.2 (B) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on reliability. Both do sending email.\n\n- Cloudflare Email Service: grade B, 65.2/100, rank #425 of 1486. Markdown https://www.anchorterminal.com/tools/cloudflare-email-service.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json\n- MailPace: grade C, 58.4/100, rank #750 of 1486. Markdown https://www.anchorterminal.com/tools/mailpace.md · JSON https://www.anchorterminal.com/api/v1/tools/mailpace.json\n- Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md\n- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md\n\n## Which one, for what\n\n### Cloudflare Email Service (B)\n\nGood for: Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.\n\nAhead on:\n- Schema \u0026 documentation, 89 against 54\n- Security \u0026 auth, 79 against 50\n- Payments \u0026 pricing, 30 against 25\n- Maintenance \u0026 community, 81 against 65\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch 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\n\n### MailPace (C)\n\nGood for: Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.\n\nAhead on:\n- Reliability, 70 against 53\n\nAlso in its favour:\n- No incidents deducted, where Cloudflare Email Service loses 3 points for them\n\nWatch for: No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Cloudflare Email Service +35\n\n- 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).\n- MailPace (54): No OpenAPI or other machine-readable contract for the HTTPS API. The MCP server's 12 tools have typed zod inputs and output schemas, but that server isn't published yet, so partial credit (8 of 25). llms.txt answers 404 on mailpace.com and docs.mailpace.com, and no Markdown copies are served (0). The reference states what each endpoint does, and the introduction says when not to use it (transactional only, no batch, no static IPs) (12 of 20). Field tables give type, examples and required or optional, with enums for status, sort and direction and the 50-recipient cap in text (9 of 15). Examples in curl and six languages and a full table of error responses with messages, though several listed messages have a broken quote (`{\"error:\"...`) and the send reference says 30 MB where the home page says 25 MB (12 of 15). Version in the path with a promise that an old version runs until a published end-of-life date, and dated changelog posts (13 of 15). Total 54.\n\n### Security \u0026 auth: Cloudflare Email Service +29\n\n- 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.\n- MailPace (50): Per-domain server tokens that can only send from and read status for their domain, and an organisation token that creates, renames and revokes domain tokens through the Domains API. Tokens travel in headers only. The authentication page still tells users to contact support to regenerate a leaked token (25 of 30). No read-only token. A domain token can't touch other domains, and the unpublished MCP server has an optional recipient allowlist. No approval step on the hosted API (8 of 20). Inbound mail reaches the customer's webhook as untrusted content, and Email Status returns bounce text. The MCP README warns about prompt injection and suggests the allowlist (9 of 15). The dashboard keeps sent mail for 30 days; no log of API calls was found (6 of 15). No security.txt (404 on mailpace.com and app.mailpace.com), no disclosure policy, bug bounty, SOC 2 or ISO 27001. WebAuthn-only two-factor sign-in and Ed25519-signed webhooks are documented (2 of 20). Total 50.\n\n### Reliability: MailPace +17\n\n- 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.\n- MailPace (70): Graded with the hosted lines. A public Upptime status page at status.mailpace.com, driven by the mailpace/status repository, with monitors for the application, SMTP, docs, blog and landing page and GitHub issues as incident reports (20). The 90 days from 8 August hold two incidents, an application outage on 22 September 2026 that the operator put down to an upstream provider returning 5xx (issue open for two minutes), and SMTP down on 2 November 2026 for about 35 minutes, which leaves SMTP at 99.65% for the week. Minor incidents only (20). No rate limit numbers are published; the docs say limits vary by organisation age, plan and history (0). A documented 429 with its message, no Retry-After or backoff guidance, and an `Idempotency-Key` on sends with written retry rules (10 of 15). The terms guarantee 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes (10). The API is at v1 with no beta label (10). Total 70.\n\n### Maintenance \u0026 community: Cloudflare Email Service +16\n\n- 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.\n- MailPace (65): Email Status API documented on 22 October 2026, and the MCP server rewritten as 2.0.0 on 4 November 2026, two days before this check (30). In the 90 days from 8 August, the Q3 changelog post of 31 August, the Email Status docs of 22 October, a mailpace-rails push on 17 October and the MCP rewrite, but only one changelog post (15 of 20). A closed service with email support. Three pull requests to the MCP repository from 2025 have no reply (8 of 15). Not in the official MCP registry (search for mailpace returned nothing on 6 November). The Node library was last pushed in October 2024 and Go in January 2024, while mailpace-rails is current (7 of 15). The MCP server gained CI with tests on 4 November; the older SDKs weren't checked for CI (5 of 10). Total 65.\n\n### Payments \u0026 pricing: Cloudflare Email Service +5\n\n- Cloudflare Email Service (30): 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).\n- MailPace (25): No x402, MPP or L402 (0). $10 a month for 10,000 emails and $1 per 1,000 after, loaded from Paddle on the pricing page and stated in the comparison pages' tables without login (20). A free plan of up to 100 emails a month is available only by emailing support, so it isn't self-serve (5 of 20). Signup, DKIM verification and payment happen in a browser (0). Total 25.\n\n## Score by category\n\n| Category | Weight | Cloudflare Email Service | MailPace | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 70 | MailPace +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 89 | 54 | Cloudflare Email Service +35 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 71 | Cloudflare Email Service +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 50 | Cloudflare Email Service +29 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | Cloudflare Email Service +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 65 | Cloudflare Email Service +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 75 | Cloudflare Email Service +2 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **65.2 · B** | **58.4 · C** | |\n\n## Facts side by side\n\n| Fact | Cloudflare Email Service | MailPace |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Cloudflare | OhMySMTP Ltd |\n| Hosted endpoint | `https://api.cloudflare.com/client/v4` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official `cloudflare` SDK on npm is Apache-2.0 | none |\n| Tools exposed | none | 12 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-25 | 2026-10-22 |\n| Terms last updated | 2025-09-12 | 2026-01-09 |\n| Privacy policy last updated | no date given | 2026-08-30 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 3.8M npm/wk, 364k PyPI/wk | 1 stars, 207 npm/wk |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Cloudflare Email Service\n\n- -2.2 on 1 November 2026: new evidence, correction, negative event\n- +0.1 on 27 October 2026: checklist\n\n### MailPace\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**MailPace.** A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.\n\n## Before you call either\n\n### Cloudflare Email Service\n\n1. POST to `https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send` with `Authorization: Bearer \u003ctoken\u003e`. The body needs `to`, `from`, `subject` and one of `html` or `text`\n2. Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the `emailSendingAdaptive` GraphQL dataset first\n3. On 429 (code 10004) wait for the `retry-after` header. On 409 `sending_not_ready` the domain setup is unfinished and nothing was sent\n4. Read `result.delivered`, `result.queued` and `result.permanent_bounces` in the response. A 200 does not mean every recipient was accepted\n5. Keep to 50 recipients across to, cc and bcc, and 25 MiB per message including attachments\n6. 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\n7. By default one suppressed recipient fails the whole send. Turn on Drop suppressed recipients for the domain to send to the rest\n\n### MailPace\n\n1. Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token\n2. Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403\n3. On 429 `You are sending emails too quickly` back off; no Retry-After is documented\n4. Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms\n5. Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned\n\n## Questions\n\n### Which is better for AI agents, Cloudflare Email Service or MailPace?\n\nCloudflare Email Service scores 65.2 (B) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on reliability.\n\n### Do Cloudflare Email Service and MailPace need an API key?\n\nBoth need an API key.\n\n### Can an agent call Cloudflare Email Service and MailPace without installing anything?\n\nCloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4. No hosted endpoint is listed for MailPace.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cloudflare-email-service\", \"b\": \"mailpace\"}`. From a terminal: `anchor compare cloudflare-email-service mailpace`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json and https://www.anchorterminal.com/api/v1/tools/mailpace.json\n\n## Other comparisons with Cloudflare Email Service or MailPace\n\n- [AhaSend API + MCP vs Cloudflare Email Service](https://www.anchorterminal.com/compare/ahasend-vs-cloudflare-email-service.md)\n- [AhaSend API + MCP vs MailPace](https://www.anchorterminal.com/compare/ahasend-vs-mailpace.md)\n- [Amazon SES vs Cloudflare Email Service](https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.md)\n- [Amazon SES vs MailPace](https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.md)\n- [Brevo API + MCP vs Cloudflare Email Service](https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service.md)\n- [Brevo API + MCP vs MailPace](https://www.anchorterminal.com/compare/brevo-vs-mailpace.md)\n- [Cloudflare Email Service vs Groundmail API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-groundmail.md)\n- [Cloudflare Email Service vs Loops API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops.md)\n- [Cloudflare Email Service vs MailerSend](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend.md)\n- [Cloudflare Email Service vs Mailgun API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun.md)\n- [Cloudflare Email Service vs Mailjet API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet.md)\n- [Cloudflare Email Service vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.md)\n- [Cloudflare Email Service vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill.md)\n- [Cloudflare Email Service vs Postmark API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark.md)\n- [Cloudflare Email Service vs Resend API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend.md)\n- [Cloudflare Email Service vs Twilio SendGrid](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid.md)\n- [Cloudflare Email Service vs SendLayer](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendlayer.md)\n- [Cloudflare Email Service vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go.md)\n- [Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.md)\n- [Groundmail API + MCP vs MailPace](https://www.anchorterminal.com/compare/groundmail-vs-mailpace.md)\n- [Loops API + MCP vs MailPace](https://www.anchorterminal.com/compare/loops-vs-mailpace.md)\n- [MailerSend vs MailPace](https://www.anchorterminal.com/compare/mailersend-vs-mailpace.md)\n- [Mailgun API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailgun-vs-mailpace.md)\n- [Mailjet API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailjet-vs-mailpace.md)\n- [MailPace vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.md)\n- [MailPace vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/mailpace-vs-mandrill.md)\n- [MailPace vs Postmark API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-postmark.md)\n- [MailPace vs Resend API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-resend.md)\n- [MailPace vs Twilio SendGrid](https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.md)\n- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md)\n- [MailPace vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.md)\n- [MailPace vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Cloudflare Email Service vs MailPace", "url": "" } ], "description": "Cloudflare Email Service scores 65.2 (B) to MailPace's 58.4 (C) for sending email. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cloudflare Email Service B 65.2", "MailPace C 58.4", "scores" ], "h1": "Cloudflare Email Service vs MailPace", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cloudflare-email-service-vs-mailpace", "published": "2026-10-01", "section": "tools", "title": "Cloudflare Email Service vs MailPace for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace" }, "tokens": { "markdown": 5500, "slim": 3180 }, "version": 1 }