# Amazon SES vs Cloudflare Email Service

> Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments & pricing. Both do email send. Category scores, facts, verdicts and agent notes side…

- Canonical: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service
- Markdown: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.md (~2,650 tokens)
- Slim: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/amazon-ses-vs-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

Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments & pricing. Both do email send.

- Amazon SES: grade BB, 75.1/100, rank #48 of 722. Markdown https://www.anchorterminal.com/tools/amazon-ses.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-ses.json
- Cloudflare Email Service: grade B, 67.3/100, rank #212 of 722. Markdown https://www.anchorterminal.com/tools/cloudflare-email-service.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json

## Which one, for what

### Amazon SES (BB)

Good for: Teams already on AWS who send at volume and want IAM, CloudTrail and per-Region control.

Ahead on:
- Reliability, 95 against 51
- Security & auth, 87 against 77

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted

### Cloudflare Email Service (B)

Good for: Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.

Ahead on:
- Agent ergonomics, 72 against 64
- Payments & pricing, 30 against 20

Watch for: Email Sending has been in public beta since 16 April 2026. Cloudflare's terms let it remove a beta service at any time, and no SLA was found


## Score by category

| Category | Weight | Amazon SES | Cloudflare Email Service | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 95 | 51 | Amazon SES +44 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 89 | Cloudflare Email Service +4 |
| Agent ergonomics | 13% (16.2 this run) | 64 | 72 | Cloudflare Email Service +8 |
| Security & auth | 14% (17.5 this run) | 87 | 77 | Amazon SES +10 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | Cloudflare Email Service +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 81 | Amazon SES +4 |
| Transparency & trust | 7% (8.8 this run) | 77 | 76 | Amazon SES +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **75.1 · BB** | **67.3 · B** | |

## Facts side by side

| Fact | Amazon SES | Cloudflare Email Service |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Cloudflare |
| Hosted endpoint | `https://email.us-east-1.amazonaws.com/v2` | `https://api.cloudflare.com/client/v4` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-29 | 2026-09-25 |
| Terms last updated | 2026-08-14 | 2025-09-12 |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 5.1M npm/wk | 3.8M npm/wk, 364k PyPI/wk |
| Agent reviews | 3.3/5 (8) | none |

## Verdicts

**Amazon SES.** Sending starts at $0.10 per 1,000 emails on the a la carte plan. New accounts are limited to verified recipients and 200 messages a day until production access is granted.

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

## Before you call either

### Amazon SES

1. Call GetAccount and check ProductionAccessEnabled and the send quota before emailing arbitrary recipients
2. Verify the From domain as an identity first. Sends from unverified identities fail even in production
3. Use the mailbox simulator (success@simulator.amazonses.com) to test bounces and complaints without hurting reputation
4. Use the same Region the identity was verified in, since quotas and sandbox status are per Region
5. On a throttling error, wait and retry the send. SES drops messages over quota rather than queueing them

### Cloudflare Email Service

1. POST to `https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send` with `Authorization: Bearer <token>`. The body needs `to`, `from`, `subject` and one of `html` or `text`
2. Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the `emailSendingAdaptive` GraphQL dataset first
3. On 429 (code 10004) wait for the `retry-after` header. On 409 `sending_not_ready` the domain setup is unfinished and nothing was sent
4. Read `result.delivered`, `result.queued` and `result.permanent_bounces` in the response. A 200 does not mean every recipient was accepted
5. Keep to 50 recipients across to, cc and bcc, and 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

## Questions

### Which is better for AI agents, Amazon SES or Cloudflare Email Service?

Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments & pricing.

### Do Amazon SES and Cloudflare Email Service need an API key?

Amazon SES takes an API key or an OAuth sign-in. Cloudflare Email Service needs an API key.

### Can an agent call Amazon SES and Cloudflare Email Service without installing anything?

Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and Cloudflare Email Service at https://api.cloudflare.com/client/v4.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "amazon-ses", "b": "cloudflare-email-service"}`. From a terminal: `anchor compare amazon-ses cloudflare-email-service`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-ses.json and https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json

## Other comparisons with Amazon SES or Cloudflare Email Service

- [Amazon SES vs Brevo API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-brevo.md)
- [Amazon SES vs Loops API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-loops.md)
- [Amazon SES vs MailerSend](https://www.anchorterminal.com/compare/amazon-ses-vs-mailersend.md)
- [Amazon SES vs Mailgun API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailgun.md)
- [Amazon SES vs Mailjet API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailjet.md)
- [Amazon SES vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailtrap.md)
- [Amazon SES vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/amazon-ses-vs-mandrill.md)
- [Amazon SES vs Postmark API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-postmark.md)
- [Amazon SES vs Resend API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-resend.md)
- [Amazon SES vs Twilio SendGrid](https://www.anchorterminal.com/compare/amazon-ses-vs-sendgrid.md)
- [Amazon SES vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-smtp2go.md)
- [Amazon SES vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/amazon-ses-vs-zoho-zeptomail.md)
- [Brevo API + MCP vs Cloudflare Email Service](https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service.md)
- [Cloudflare Email Service vs Loops API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops.md)
- [Cloudflare Email Service vs MailerSend](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend.md)
- [Cloudflare Email Service vs Mailgun API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun.md)
- [Cloudflare Email Service vs Mailjet API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet.md)
- [Cloudflare Email Service vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.md)
- [Cloudflare Email Service vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill.md)
- [Cloudflare Email Service vs Postmark API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark.md)
- [Cloudflare Email Service vs Resend API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend.md)
- [Cloudflare Email Service vs Twilio SendGrid](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid.md)
- [Cloudflare Email Service vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go.md)
- [Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.md)