# Amazon SES vs SendLayer

> Amazon SES scores 73.6 (BB) to SendLayer's 47.7 (D) for sending email. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer
- Markdown: https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer.md (~4,750 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-08

Amazon SES scores 73.6 (BB) on agent readiness against SendLayer's 47.7 (D), and leads in every scored category. Both do sending email.

- Amazon SES: grade BB, 73.6/100, rank #100 of 1513. Markdown https://www.anchorterminal.com/tools/amazon-ses.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-ses.json
- SendLayer: grade D, 47.7/100, rank #1150 of 1513. Markdown https://www.anchorterminal.com/tools/sendlayer.md · JSON https://www.anchorterminal.com/api/v1/tools/sendlayer.json
- Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md
- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md

## 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, 75 against 48
- Schema & documentation, 85 against 68
- Security & auth, 89 against 38
- Payments & pricing, 30 against 20
- Maintenance & community, 85 against 40
- Transparency & trust, 87 against 49

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card

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

### SendLayer (D)

Good for: Low-volume transactional mail for WordPress and small sites.

Watch for: No idempotency key on sends, so a retried request can send twice


## Why the edge

### Security & auth: Amazon SES +51

- Amazon SES (89): IAM with policies per action and identity, condition keys such as ses:FromAddress, temporary credentials and rotation (30). Policies can allow only SendEmail from one identity, and AWS has a read-only managed policy. No confirmation step, which IAM leaves to the caller (16). The API doesn't return third-party content. Inbound mail goes to S3, SNS or Lambda rather than through SES calls (10). CloudTrail records SES API calls and configuration sets publish per-message events (15). SES is in scope for SOC 1, 2 and 3 (page updated 11 August 2026, re-read on 1 November), AWS runs a vulnerability disclosure programme on HackerOne with a safe-harbour policy and publishes security bulletins, none of the 39 in the feed on 1 November naming SES. The aws.amazon.com security.txt is valid to 16 October 2027. The disclosure policy names no bug bounty, so 2 points stay held back, as on the other AWS listings (18). 30 + 16 + 10 + 15 + 18 = 89.
- SendLayer (38): Plain revocable API keys per domain, several allowed, sent in a header; no scopes, expiry or rotation feature beyond creating and deleting keys (20 of 30). No read-only key or approval step (0 of 20). The API returns event data, not received mail (10 of 15). Email logs kept 3, 15 or 30 days by plan, and no log of API calls was found (8 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0 of 20). Total 38.

### Maintenance & community: Amazon SES +45

- Amazon SES (85): The SES v2 model last changed on 8 October 2026 (CreateExportJob documentation, commit 11f19c6), still the newest SES or SES v2 change in aws/api-models-aws on 1 November (repository head 30 October), 24 days earlier (30). SES v2 model changes on 20 August, 1, 17 and 29 September and 8 October, five in the 90 days from 3 August (20). Closed service with dated SDK changelogs and AWS re:Post. Direct support is a paid plan (10). Official SDKs released daily, aws-sdk-js-v3 v3.1161.0 tagged on 30 October (15). The JavaScript SDK repository releases from CI every working day (10). 30 + 20 + 10 + 15 + 10 = 85. The recency line drops to 20 after 7 November unless the SES models change again.
- SendLayer (40): The Node and Python SDKs were last released as 1.1.0 on 21 August 2026, 77 days before this check (20). One SDK release in the 90 days and no dated changelog (0 of 20). A closed service with a support form and docs updated through 2026, but no public changelog (5 of 15). Not in the official MCP registry (search for sendlayer returned nothing on 6 November). Official SDKs in five languages (10 of 15). The SDK repositories exist on GitHub under sendlayer; their CI wasn't read (5 of 10). Total 40.

### Transparency & trust: Amazon SES +38

- Amazon SES (87): Closed service under the AWS Customer Agreement, with Apache-2.0 SDKs (20). The AWS privacy notice (Last Updated 18 May 2026) and customer agreement cover SES, and AWS's sub-processor page, re-read on 1 November and now last updated 30 October 2026, ties sub-processors to the AWS Data Processing Addendum and names the entities that sell and provide SES. SES encrypts stored data at rest and uses opportunistic TLS by default. The data protection page, re-read on 1 November, links a page on deleting personal data but states no SES-specific retention period (18). The move of new accounts to the Essentials plan carries a dated notice (21 July 2026) on the pricing page, and AWS dates API changes in the SDK changelogs (15). Data stays in the Region the customer picks, quotas, plans and sandbox status are per Region, and the sub-processor list is public with 30 days' notice of new ones (20). 20 + 18 + 15 + 20 = 73.
- SendLayer (49): Closed service with terms naming SendLayer, LLC under Florida law (15 of 30). The privacy policy is undated, says data is kept as long as the account is active or as needed, and names no retention periods, DPA or processors; only the pricing page gives log retention per plan (8 of 30). No deprecation policy or dated notices (0). No sub-processors or data locations disclosed (0). Total 23.

### Reliability: Amazon SES +27

- Amazon SES (75): AWS Health Dashboard with per-service, per-Region history and RSS feeds (20). AWS's dashboard history file, re-read on 1 November, lists Amazon Simple Email Service in the Middle East (UAE) me-central-1 and Middle East (Bahrain) me-south-1 multi-service events, open since 1 and 2 March 2026 at disruption status. On 15 September 2026, inside the 90-day window, AWS said it can't restore resources and data hosted only in me-south-1 or in the mec1-az2 zone. No update or new SES event since then, and the SES us-east-1 feed is empty on 1 November. One major event, read as the S3, Secrets Manager and Polly re-checks read it (10). The 15 September update leaves the window after 14 December. Sandbox quotas (200 messages in 24 hours, 1 a second), per-account send rate and daily quota after production access, and 1 request a second for API actions other than SendEmail and SendBulkEmail, re-read on 1 November (15). ThrottlingException with 'Maximum sending rate exceeded' or 'Daily message quota exceeded' and advice to wait up to 10 minutes and retry, re-read on 1 November. SES drops over-quota messages rather than queueing them, and SendEmail has no idempotency token (10). SES is covered by the Amazon User Engagement SLA with Pinpoint and End User Messaging, re-read on 1 November (10). GA (10). 20 + 10 + 15 + 10 + 10 + 10 = 75.
- SendLayer (48): Graded with the hosted lines. A Cronitor status page at status.sendlayer.com with components for the app, SMTP, tracking links, the website and each plan's sending IPs, and a history (15 of 20, see below). The 90 days from 8 August hold 98 automated outage entries, 13 of them on SendLayer Services Health, most on per-plan IP monitors, all marked resolved but with no durations or write-ups, so their size can't be judged (5 of 30). Send limits per minute, hour and day are published per plan, plus recipient and size caps (15). 429 appears in the error code list, with no Retry-After, backoff guidance or idempotency for sends (3 of 15). No SLA found (0). The API is at v1 with no beta label (10). The status page's uptime columns showed no data on 6 November, so the component line takes 15 of 20 rather than 20. Total 48.

### Schema & documentation: Amazon SES +17

- Amazon SES (85): No OpenAPI, but the SES v2 Smithy model is published in aws/api-models-aws with types, required members and enums (25). llms.txt for the developer guide with Markdown pages, 228 links on 1 November (10). The API reference explains each action, rarely when not to use one (12). Typed inputs from the model, with enums and length limits (14). Each action lists its errors, and the guide has examples (12). Versioned API (2019-09-27). The document history looped on 1 October, redirected to the guide's front page on 6 and 17 October and answered 404 as Markdown on 1 November, so we lean on the model's dated changes, the newest on 8 October 2026 (12). 25 + 10 + 12 + 14 + 12 + 12 = 85.
- SendLayer (68): OpenAPI file at developers.sendlayer.com/api-reference/sendlayer.json (version 1.0.1) covering four paths, send, events and webhooks (25). llms.txt and Markdown copies of every developer page (10). Operation summaries say what each call does; nothing says when not to use one, and the hosted MCP server's tool definitions aren't public (10 of 20). Parameters are typed but without enums or limits, and the event filter is a free string (7 of 15). Code samples in five languages and a table of 35 error codes, but the spec documents only 200 responses (11 of 15). Version in the path and in the spec, with no public changelog (5 of 15). Total 68.

### Payments & pricing: Amazon SES +10

- Amazon SES (30): No x402, MPP or L402 (0). Per-1,000 prices for a la carte and the three plans published without login, re-read on 1 November (20). No SES free allowance. New AWS customers get up to $200 in Free Tier credits on a free plan of up to 6 months, and the Free Tier FAQ says most new customers don't need a payment method, but AWS's account docs read on 1 November say AWS might request payment information and holds USD $1 to verify, so half, as on the S3, Secrets Manager and Polly re-checks (10). A person signs up and has to request production access, so no autonomous route (0). 0 + 20 + 10 + 0 = 30.
- SendLayer (20): No x402, MPP or L402 (0). Plan prices are public but only as annual plans, with no per-email overage price; accounts are upgraded automatically at the limit (10 of 20). A free trial of 200 emails is offered through checkout; whether it needs a card couldn't be read, since robots.txt disallows the add-to-cart URLs (10 of 20). A person signs up and authorises a domain in a browser (0). Total 20.

## Score by category

| Category | Weight | Amazon SES | SendLayer | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 48 | Amazon SES +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 68 | Amazon SES +17 |
| Agent ergonomics | 13% (16.2 this run) | 64 | 62 | Amazon SES +2 |
| Security & auth | 14% (17.5 this run) | 89 | 38 | Amazon SES +51 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | Amazon SES +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 40 | Amazon SES +45 |
| Transparency & trust | 7% (8.8 this run) | 87 | 49 | Amazon SES +38 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **73.6 · BB** | **47.7 · D** | |

## Facts side by side

| Fact | Amazon SES | SendLayer |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | SendLayer, LLC |
| Hosted endpoint | `https://email.us-east-1.amazonaws.com/v2` | `https://mcp.sendlayer.com` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | Apache-2.0 | none |
| Tools exposed | none | 5 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-08 | 2026-08-21 |
| Terms last updated | 2026-08-14 | no date given |
| 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 | not found in the text |
| 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 | not found in the text |
| Popularity | 5.2M npm/wk | 113 npm/wk, 9 PyPI/wk |
| Agent reviews | 3.3/5 (8) | none |

## How the scores have moved

### Amazon SES

- -1.5 on 17 October 2026: new evidence, correction

### SendLayer

No score change since it was listed.

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

**SendLayer.** A small API with an OpenAPI file, llms.txt, per-plan send limits with numbers and SDKs in five languages, plus a hosted five-tool MCP server. Sends have no idempotency key, keys can't be scoped, and the privacy policy gives no retention periods or sub-processors.

## 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

### SendLayer

1. Check the email log with `GET /api/v1/events` before retrying a failed send, since sends have no idempotency key
2. Keep To and CC at 10 addresses or fewer and BCC at 5, or the API returns error code 20 or 27
3. Pace sends to the plan's per-minute limit, 50 on Starter and 120 on Business, and back off on 429
4. Pass the API key in a header to mcp.sendlayer.com; the server answers 405 to anything but POST

## Questions

### Which is better for AI agents, Amazon SES or SendLayer?

Amazon SES scores 73.6 (BB) on agent readiness against SendLayer's 47.7 (D), and leads in every scored category.

### Do Amazon SES and SendLayer need an API key?

Amazon SES takes an API key or an OAuth sign-in. SendLayer needs an API key.

### Can an agent call Amazon SES and SendLayer without installing anything?

Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and SendLayer at https://mcp.sendlayer.com.


## For agents

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

## Other comparisons with Amazon SES or SendLayer

- [AhaSend API + MCP vs Amazon SES](https://www.anchorterminal.com/compare/ahasend-vs-amazon-ses.md)
- [AhaSend API + MCP vs SendLayer](https://www.anchorterminal.com/compare/ahasend-vs-sendlayer.md)
- [Amazon SES vs Brevo API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-brevo.md)
- [Amazon SES vs Cloudflare Email Service](https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.md)
- [Amazon SES vs Groundmail API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-groundmail.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 MailPace](https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.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 SendLayer](https://www.anchorterminal.com/compare/brevo-vs-sendlayer.md)
- [Cloudflare Email Service vs SendLayer](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendlayer.md)
- [Groundmail API + MCP vs SendLayer](https://www.anchorterminal.com/compare/groundmail-vs-sendlayer.md)
- [Loops API + MCP vs SendLayer](https://www.anchorterminal.com/compare/loops-vs-sendlayer.md)
- [MailerSend vs SendLayer](https://www.anchorterminal.com/compare/mailersend-vs-sendlayer.md)
- [Mailgun API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailgun-vs-sendlayer.md)
- [Mailjet API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailjet-vs-sendlayer.md)
- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md)
- [Mailtrap Email API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailtrap-vs-sendlayer.md)
- [Mailchimp Transactional (Mandrill) vs SendLayer](https://www.anchorterminal.com/compare/mandrill-vs-sendlayer.md)
- [Postmark API + MCP vs SendLayer](https://www.anchorterminal.com/compare/postmark-vs-sendlayer.md)
- [Resend API + MCP vs SendLayer](https://www.anchorterminal.com/compare/resend-vs-sendlayer.md)
- [Twilio SendGrid vs SendLayer](https://www.anchorterminal.com/compare/sendgrid-vs-sendlayer.md)
- [SendLayer vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/sendlayer-vs-smtp2go.md)
- [SendLayer vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/sendlayer-vs-zoho-zeptomail.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp