# Cloudflare Email Service > 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. - Canonical: https://www.anchorterminal.com/tools/cloudflare-email-service - Markdown: https://www.anchorterminal.com/tools/cloudflare-email-service.md (~9,000 tokens) - Slim: https://www.anchorterminal.com/tools/cloudflare-email-service.min.md (~1,980 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/cloudflare-email-service.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 67.3/100 · rank #212 of 722 · #4 in Email delivery APIs · not agent-ready · confidence medium** More from Cloudflare, listed separately because each is its own product: [Cloudflare Sandbox SDK](https://www.anchorterminal.com/tools/cloudflare-sandbox-sdk.md) (Code execution sandboxes), [Cloudflare Web Search API](https://www.anchorterminal.com/tools/cloudflare-web-search.md) (Web search APIs), [Cloudflare MCP Servers](https://www.anchorterminal.com/tools/cloudflare-mcp.md) (Cloud & infrastructure), [Cloudflare R2](https://www.anchorterminal.com/tools/cloudflare-r2.md) (File storage & sharing), [Clef](https://www.anchorterminal.com/tools/cloudflare-clef.md) (Decision models). ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Cloudflare (https://developers.cloudflare.com/email-service/) | | Kind | HTTP API | | Category | Email delivery APIs (https://www.anchorterminal.com/categories/email) | | Transport | HTTP | | Endpoint | `https://api.cloudflare.com/client/v4` | | Auth | API key · 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 | Pay per use ($5 / mo) · $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/). | | x402 | No · 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). | | 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 | | Packages | npm: `cloudflare`; pypi: `cloudflare` | | Docs | https://developers.cloudflare.com/email-service/ | | llms.txt | https://developers.cloudflare.com/email-service/llms.txt | | Last release | 2026-09-25 | | npm downloads / week | 3,766,696 | | PyPI downloads / week | 363,923 | | Status | Email Sending is in public beta (since 16 April 2026). Email Routing is generally available on Free and Paid plans | | API | REST under `https://api.cloudflare.com/client/v4`. `POST /accounts/{account_id}/email/sending/send` for structured mail and `/send_raw` for a MIME message, plus suppressions, sending subdomains and their DNS records, limits and reputation. 29 sending operations in the OpenAPI 3.0.3 file | | Workers binding | `send_email` binding with a `send()` method that returns one `messageId`. A binding can be limited with `destination_address`, `allowed_destination_addresses` or `allowed_sender_addresses` | | SMTP | `smtp.mx.cloudflare.net` port 465, implicit TLS only, AUTH PLAIN or LOGIN, username `api_token`, password an API token. 50 recipients a session | | Credentials | Cloudflare API token, account-owned or user-owned, with optional expiry and IP address filter. Send and read are separate permissions | | Limits | 50 recipients per email across to, cc and bcc, 5 MiB per message, 32 attachments, 16 KB of custom headers, 998 characters in a subject. Daily quota per account with no published number. Cloudflare API limit of 1,200 requests per five minutes per token | | Free allowance | 3,000 emails a month included on Workers Paid. Sends to verified destination addresses in the account are free on every plan | | Domains | The domain must use Cloudflare DNS. Onboarding adds MX, SPF, DKIM and DMARC records, and up to 30 domains per zone can be configured | | Inbound | Email Routing forwards mail to verified addresses or passes it to a Worker's `email()` handler, which can forward, reply or reject. 200 rules per domain, 25 MiB per inbound message | | Suppressions | Account-wide or per sending domain since 25 September 2026. Hard bounces suppress for seven days or with no expiry, soft bounces for 24 hours. Bulk import of 1,000 entries, 10 requests a minute | | Logs | Activity log in the dashboard for up to 30 days, the same events in the GraphQL Analytics API for 31 days, message previews kept about seven days, and account audit logs for configuration changes kept 18 months | | Events | Delivered, deferred, bounced and rejected events per sending domain go to Cloudflare Queues. No HTTP webhook found | | Templates | None found | | SDKs | Cloudflare's general API SDKs for Node (`cloudflare` 7.3.0 on npm, 3 October 2026), Python (`cloudflare` 5.9.0 on PyPI, 3 October 2026) and Go | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 51 | 10.2 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 89 | 14.5 | | Agent ergonomics | 13% | 16.2 | 72 | 11.7 | | Security & auth | 14% | 17.5 | 77 | 13.5 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 81 | 7.1 | | Transparency & trust (editorial 57, provenance 95) | 7% | 8.8 | 76 | 6.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **67.3 → B** | ### Why each score - Reliability 51: Graded on the hosted Email Sending REST API with the hosted lines. cloudflarestatus.com is a Statuspage with Email Sending and Email Routing as separate components (20). The incidents feed held 50 incidents from 19 September to 8 October 2026, none naming either email component. The API component had a minor incident of 18 minutes on 7 October and delayed permission changes on 30 September. The history page loads by script, so the rest of the 90 days went unread (10 of 30). 1,200 API requests per five minutes per token and 200 a second per IP, 50 recipients and 5 MiB per message. The daily sending quota and the send rate limit 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 marked Beta in the docs, although the OpenAPI operation is tagged generally-available. We scored from the docs (0). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 89: Cloudflare's public OpenAPI 3.0.3 file 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 14 REST error codes 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). - Agent ergonomics 72: A send returns a small object grouping recipients into delivered, queued and bounced. 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). - Security & auth 77: 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 names HackerOne and a disclosure policy with no Expires field. The compliance page lists no certifications without a dashboard login, so none were confirmed (16 of 20). - Payments & pricing 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). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 81: Read for a closed service. The newest Email Service changelog entry is 25 September 2026, per-domain suppressions (30). Four entries in the last 90 days, on 15 July, 17 July, 4 September and 25 September (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 on npm (7.3.0) and PyPI (5.9.0) were both published on 3 October 2026. The Go SDK wasn't checked (15). The OpenAPI file carries the sending paths. Nothing else to measure for a hosted endpoint (6 of 10). - Transparency & trust 76: Closed service under the Self-Serve Subscription Agreement and service-specific terms with an Email Service section updated on 28 September 2026. The SDKs are Apache-2.0 (18 of 30). The privacy policy of 4 November 2025 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). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/cloudflare-email-service.md (JSON https://www.anchorterminal.com/fixes/cloudflare-email-service.json) ### What we couldn't check - unchecked: status history before 19 September 2026. The history page loads by script and the incidents feed holds only the latest 50 incidents - unchecked: Cloudflare's certifications. The compliance page lists none without a dashboard login - unchecked: whether Cloudflare signup or the Workers Free plan asks for a card. The signup flow wasn't run - unchecked: the Go SDK's current version and whether the SDKs' generated methods cover every sending operation - The daily sending quota for a new account and the send rate limit have no published number - Docs and OpenAPI disagree on status. The docs mark Email Sending as Beta, and the OpenAPI send operation is tagged generally-available - The token permissions reference page has no Email Sending entry. The permission names come from the SMTP guide and the OpenAPI file - Whether the legacy `/email/sending/suppression` paths in the OpenAPI file, alongside the newer `/suppressions` ones, are due for removal - Whether Cloudflare's MCP servers, listed separately as cloudflare-mcp, expose Email Sending. Not checked for this listing - The lead was right about the interfaces and the beta status. Email Routing is part of the same product, so the listing also covers inbound mail ### Sources - docs home with the Beta mark: (seen 2026-10-08) - llms.txt: (seen 2026-10-08) - REST API guide and error codes: (seen 2026-10-08) - SMTP guide: (seen 2026-10-08) - Workers binding and error codes: (seen 2026-10-08) - send bindings: (seen 2026-10-08) - getting started: (seen 2026-10-08) - limits: (seen 2026-10-08) - pricing: (seen 2026-10-08) - Workers pricing: (seen 2026-10-08) - FAQ: (seen 2026-10-08) - email lifecycle: (seen 2026-10-08) - suppression lists: (seen 2026-10-08) - email logs: (seen 2026-10-08) - metrics and analytics: (seen 2026-10-08) - audit logs: (seen 2026-10-08) - audit log retention: (seen 2026-10-08) - event subscriptions: (seen 2026-10-08) - Email Sending API reference: (seen 2026-10-08) - send operation reference: (seen 2026-10-08) - OpenAPI file: (seen 2026-10-08) - Cloudflare API rate limits and headers: (seen 2026-10-08) - token expiry and IP filtering: (seen 2026-10-08) - token permissions reference: (seen 2026-10-08) - Email Service changelog: (seen 2026-10-08) - Email Service changelog RSS: (seen 2026-10-08) - status components: (seen 2026-10-08) - status incidents feed: (seen 2026-10-08) - status history page: (seen 2026-10-08) - Self-Serve Subscription Agreement: (seen 2026-10-08) - Developer Platform service-specific terms: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - customer DPA: (seen 2026-10-08) - sub-processors: (seen 2026-10-08) - compliance resources: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - npm registry record for cloudflare: (seen 2026-10-08) - PyPI record for cloudflare: (seen 2026-10-08) - RDAP for cloudflare.com: (seen 2026-10-08) ## Who's behind it (provenance 95/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Cloudflare, Inc. | 20/20 | | Domain age | cloudflare.com, registered 2009-02-17 (17 years) | 15/15 | | Endpoint on the vendor's domain | api.cloudflare.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 2 clauses that cost points | 6/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | www.cloudflarestatus.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | 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, read on 8 October 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 8 October 2026. RDAP for cloudflare.com gives a registration date of 2009-02-17. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.cloudflare.com/terms/), read 2026-10-08, dated 2025-09-12, states 7 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "(e) introduce software or automated agents or scripts into the Services so as to produce multiple accounts, generate automated searches, requests or queries, or to strip or mine data from the Services;" - To know. Says the terms or the service can change without notice (costs points). "We also reserve the right to modify or discontinue the Service at any time (including, without limitation, by limiting or discontinuing certain features of the Service) without notice to you." - To know. Says access can be ended without notice or for any reason. "We may at our sole discretion terminate your user account or Suspend or terminate your use or access to the Service at any time, with or without notice for any reason or no reason at all." - To know. Requires arbitration or waives class actions. "THIS AGREEMENT CONTAINS PROVISIONS REQUIRING THAT YOU AGREE TO THE USE OF ARBITRATION TO RESOLVE ANY DISPUTES ARISING UNDER THIS AGREEMENT RATHER THAN A JURY TRIAL OR ANY OTHER COURT PROCEEDINGS, AND TO WAIVE YOUR PARTICIPATION IN CLASS ACTION OF ANY KIND AGAINST CLOUDFLARE." - Gives the date it was last updated. Last updated 2025-09-12. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Says it gives notice of a change. - Also in the text (2026-10-08). A customer who lets a third party into the account with an API token or OAuth does so at its own risk, and that party may change or delete account data. "You acknowledge that by permitting a third party to access your Cloudflare account, the third party may obtain, modify, or delete your account data and settings." - Also in the text (2026-10-08). Fees are non-refundable, and a customer who cancels is billed in full for the subscription term in which it cancels. "YOU WILL BE BILLED IN FULL FOR THE SUBSCRIPTION TERM IN WHICH YOU CANCEL AND NO REFUNDS WILL BE PROVIDED FOR THE UNUSED PORTION OF SUCH SUBSCRIPTION TERM." - Also in the text (2026-10-08). Cloudflare accepts no liability for harm arising from free or trial versions of the Services. "We will have no liability for any harm or damage arising out of or in connection with any Free Services." **Privacy policy** (https://www.cloudflare.com/privacypolicy/), read 2026-10-08, gives no date, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Making Personal Information (such as online identifiers or browsing activity) available to these companies may be considered a “sale” or “sharing” of your Personal Information under the CCPA." - Not found in the text. Gives the date it was last updated. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacyquestions@cloudflare.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. ## Live (updated 2026-10-08 22:39 UTC) - Right now: up, HTTP 404, 21 ms, checked 2026-10-08 22:39 UTC (get on `https://api.cloudflare.com/client/v4`) - Uptime 24h 100.0% (36 probes) · 30 days 100.0% (36 probes) · p50 39 ms · p95 97 ms - Vendor status page: major, Partial System Outage - Always current: https://www.anchorterminal.com/api/v1/live/cloudflare-email-service.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Outbound email | $0.35 | per 1,000 emails | After 3,000 included a month, Workers Paid plan only. Sends to verified destination addresses are free | | Workers Paid plan | $5 | per month (plan) | Minimum monthly charge for the plan that Email Sending to arbitrary recipients needs | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 the changelog has four dated entries since 15 July 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 ## Before you call it (notes for agents) 1. POST to `https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send` with `Authorization: Bearer `. 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 5 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 ## Connect First request: ```bash curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send" \ --header "Authorization: Bearer " \ --header "Content-Type: application/json" \ --data '{"to":"recipient@example.com","from":"welcome@yourdomain.com","subject":"Welcome to our service!","html":"

Welcome!

Thanks for signing up.

","text":"Welcome! Thanks for signing up."}' ``` Through letme (picks today, calling later): https://letme.dev/cloudflare-email-service. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Amazon SES | BB | 75.1 | 48 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/amazon-ses.md | | Resend API + MCP | BB | 75.1 | 50 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/resend.md | | AgentMail API + MCP | BB | 74.9 | 55 | email.send, email.inbound, email.domains, email.analytics | yes | https://www.anchorterminal.com/tools/agentmail.md | | MailerSend | B | 69.5 | 156 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailersend.md | | Mailtrap Email API + MCP | B | 66.8 | 228 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailtrap.md | | Postmark API + MCP | B | 66.5 | 235 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/postmark.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Email Sending entered public beta on 16 April 2026 and is still marked Beta on the docs home page, while Email Routing carries no beta mark (source: ) - Three ways to send. A REST call to `/accounts/{account_id}/email/sending/send`, the `send_email` Workers binding, and SMTP on `smtp.mx.cloudflare.net` port 465, added in beta on 8 June 2026 (source: ) - The public OpenAPI 3.0.3 file has 29 operations under `/email/sending` and 46 under `/email/routing`. The rendered API reference lists 14 of the sending ones (source: ) - New accounts start with a daily quota the docs call conservative, with no number, and can send only to verified destination addresses until a sending domain is onboarded (source: ) - The service-specific terms limit the Email Service to transactional email, say Cloudflare may scan message content for malware, phishing and spam, and say it is not durable storage (source: ) - Delivery events for a sending domain can be published to Cloudflare Queues since 15 July 2026. No HTTP webhook was found (source: ) - The npm and PyPI download counts are for Cloudflare's general API SDKs, which cover every Cloudflare product, not Email Service alone ## Compare - [Amazon SES vs Cloudflare Email Service](https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.md): BB 75.1 vs B 67.3 - [Brevo API + MCP vs Cloudflare Email Service](https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service.md): E 44.8 vs B 67.3 - [Cloudflare Email Service vs Loops API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops.md): B 67.3 vs B 62.7 - [Cloudflare Email Service vs MailerSend](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend.md): B 67.3 vs B 69.5 - [Cloudflare Email Service vs Mailgun API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun.md): B 67.3 vs B 66.2 - [Cloudflare Email Service vs Mailjet API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet.md): B 67.3 vs C 59.4 - [Cloudflare Email Service vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.md): B 67.3 vs B 66.8 - [Cloudflare Email Service vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill.md): B 67.3 vs C 58.1 - [Cloudflare Email Service vs Postmark API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark.md): B 67.3 vs B 66.5 - [Cloudflare Email Service vs Resend API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend.md): B 67.3 vs BB 75.1 - [Cloudflare Email Service vs Twilio SendGrid](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid.md): B 67.3 vs B 63.6 - [Cloudflare Email Service vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go.md): B 67.3 vs D 53.1 - [Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.md): B 67.3 vs C 61.8 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on cloudflare.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "cloudflare-email-service", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Cloudflare Email Service on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Cloudflare Email Service on Anchor Terminal](https://www.anchorterminal.com/badges/cloudflare-email-service.svg)](https://www.anchorterminal.com/tools/cloudflare-email-service) ``` Plain link: ```html Cloudflare Email Service on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Cloudflare Email Service is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/cloudflare-email-service-dark.png - Light: https://www.anchorterminal.com/assets/share/cloudflare-email-service-light.png