{ "data": { "a": { "slug": "amazon-ses", "name": "Amazon SES", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/ses/", "kind": "http-api", "category": "email", "summary": "AWS's email service for sending and receiving at scale, over the SES v2 API or SMTP, with templates, configuration sets, receipt rules and deliverability tooling.", "url": "https://www.anchorterminal.com/tools/amazon-ses", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-ses.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-ses.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-ses.json", "dns": "amazon-ses.grade.anchorterminal.com", "repo": "https://github.com/aws/aws-sdk-js-v3", "license": "Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://email.us-east-1.amazonaws.com/v2", "packages": [ { "registry": "npm", "name": "@aws-sdk/client-sesv2" }, { "registry": "pypi", "name": "boto3" } ], "auth": "mixed", "authNotes": "API calls are signed with AWS Signature Version 4 using IAM credentials. SMTP uses separate SMTP credentials derived from an IAM user. The AWS MCP Server can reach SES with IAM SigV4 or OAuth sign-in.", "pricing": "usage", "pricingNotes": "A la carte $0.10 per 1,000 emails sent or received, plus $0.12 a GB of attachments and $0.09 per 1,000 inbound chunks. Pricing plans since 2026 are Essentials $0.16 per 1,000 with no monthly fee, Pro $105 a month plus $0.22 per 1,000, Enterprise $500 a month plus $0.23 per 1,000, all falling with volume. Accounts with no SES use since 2025-06-01 start on Essentials from 2026-07-21. Standard dedicated IPs $24.95 a month each. New AWS customers get up to $200 in Free Tier credits on a free plan of up to 6 months. AWS says most new customers can sign up without a payment method, and that it might request one and hold USD $1 to verify (https://aws.amazon.com/ses/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$105 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 or stablecoin payment path in docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 5214584, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.aws.amazon.com/ses/latest/dg/Welcome.html", "llmsTxt": "https://docs.aws.amazon.com/ses/latest/dg/llms.txt", "capabilities": [ "email.send", "email.inbound", "email.templates", "email.domains", "email.analytics" ], "tags": [ "hosted", "llms-txt", "typescript", "python", "enterprise", "free-tier", "no-card" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 73.6, "grade": "BB", "agentReady": true, "rank": 100, "ranked": true, "rankOf": 1513, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 85, "payments": 30, "reliability": 75, "schema": 85, "security": 89, "transparency": 87 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "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.", "bestFor": "Teams already on AWS who send at volume and want IAM, CloudTrail and per-Region control.", "strengths": [ "$0.10 per 1,000 emails a la carte, falling to $0.11 per 1,000 above 100 million on Essentials", "IAM policies can limit a credential to SendEmail from one identity, and CloudTrail logs every call", "Covered by an AWS SLA and in scope for SOC 1, 2 and 3", "Inbound mail through receipt rules to S3, SNS or Lambda", "Smithy model for SES v2 published and changed five times in the 90 days to 1 November 2026, most recently on 8 October" ], "weaknesses": [ "Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted", "SigV4 signing makes a plain curl or quick agent call awkward", "No idempotency token on SendEmail, and over-quota messages are dropped", "Listed in AWS's open me-central-1 and me-south-1 disruptions, where AWS said on 15 September 2026 that some data can't be restored", "API actions other than the send calls are throttled at 1 request a second, with no increase available" ], "agentNotes": [ "Call GetAccount and check ProductionAccessEnabled and the send quota before emailing arbitrary recipients", "Verify the From domain as an identity first. Sends from unverified identities fail even in production", "Use the mailbox simulator (success@simulator.amazonses.com) to test bounces and complaints without hurting reputation", "Use the same Region the identity was verified in, since quotas and sandbox status are per Region", "On a throttling error, wait and retry the send. SES drops messages over quota rather than queueing them" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 73.6 } ], "editorialScores": { "ergonomics": 64, "maintenance": 85, "payments": 30, "reliability": 75, "schema": 85, "security": 89, "transparency": 73 }, "provenanceScore": 100, "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-10-17", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://email.us-east-1.amazonaws.com/v2/email/outbound-emails \\\n --aws-sigv4 \"aws:amz:us-east-1:ses\" --user \"$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY\" \\\n -H \"Content-Type: application/json\" -d '{\"FromEmailAddress\":\"you@example.com\",\"Destination\":{\"ToAddresses\":[\"them@example.com\"]},\"Content\":{\"Simple\":{\"Subject\":{\"Data\":\"Hello\"},\"Body\":{\"Text\":{\"Data\":\"Hello from SES\"}}}}}'" }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/amazon-ses" }, "sameCompany": [ "amazon-bedrock", "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "amazon-nova-sonic", "agentcore-memory", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "communication", "unitPrices": [ { "item": "Outbound, a la carte", "unit": "1k-emails", "usd": 0.1, "note": "plus $0.12 a GB of attachments" }, { "item": "Inbound, a la carte", "unit": "1k-emails", "usd": 0.1, "note": "plus $0.09 per 1,000 incoming chunks" }, { "item": "Essentials plan", "unit": "1k-emails", "usd": 0.16, "note": "0 to 10M, no monthly fee, default for new accounts from 2026-07-21" }, { "item": "Pro plan", "unit": "month", "usd": 105, "note": "plus $0.22 per 1,000 emails, 1 managed dedicated IP included" }, { "item": "Pro plan emails", "unit": "1k-emails", "usd": 0.22, "note": "0 to 10M" }, { "item": "Enterprise plan", "unit": "month", "usd": 500, "note": "plus $0.23 per 1,000 emails" }, { "item": "Dedicated IP, standard", "unit": "month", "usd": 24.95, "note": "per IP" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazonaws.com", "domainRegistered": "2005-08-18", "domainNote": "The API runs on Amazon's amazonaws.com service domain, while the product and legal pages sit on aws.amazon.com (amazon.com registered 1994-11-01).", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/agreement/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/ses/latest/dg/doc-history.html", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "https://aws.amazon.com/.well-known/security.txt carries Expires 2027-10-16T16:25:03.000Z on 1 November 2026. It points to the AWS VDP on HackerOne and the policy at vdp.aws.security.", "The changelog address (doc-history.html) redirected to the developer guide's front page on 6 and 17 October, and its Markdown twin answered 404 on 1 November; the SES v2 model in aws/api-models-aws carries the dated API changes." ], "score": 100 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "paid-only", "freeTier": true, "minutes": 20, "credential": "cloud-iam", "hosting": [ "US", "CA", "EU", "UK", "APAC" ], "euResidency": "yes", "trainsOnData": "no", "zeroRetention": "unknown", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "CSA STAR", "HIPAA (BAA available)", "FedRAMP", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-ses.json", "live": { "slug": "amazon-ses", "probe": { "target": "https://email.us-east-1.amazonaws.com/v2", "method": "get", "lastAt": "2026-11-08T19:18:33.410698367Z", "lastOk": true, "lastStatus": 404, "lastMs": 325, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 261, "p95ms24h": 353, "samples24h": 243, "samples30d": 7890, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "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": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 196, "ok": 196 } ], "since": "2026-10-08T00:00:00Z" }, "versions": [ { "registry": "github", "name": "aws/aws-sdk-js-v3", "version": "v3.1164.0", "released": "2026-11-06", "seenAt": "2026-11-08T00:34:38.109655795Z" }, { "registry": "npm", "name": "@aws-sdk/client-sesv2", "version": "3.1164.0", "seenAt": "2026-11-08T00:34:37.76134273Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.126", "released": "2026-11-06", "seenAt": "2026-11-08T00:34:37.978956349Z" } ], "githubStars": 3679, "npmWeekly": 8887761, "pypiWeekly": 631287754, "securityTxt": { "url": "https://amazonaws.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-16T16:25:03.000Z", "checkedAt": "2026-11-08T16:02:59.489638332Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/ses/latest/dg/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-08T15:35:01.536992065Z" }, "domain": { "domain": "amazonaws.com", "registered": "2005-08-18", "source": "https://rdap.verisign.com/com/v1/domain/amazonaws.com", "checkedAt": "2026-11-08T15:03:16.29084936Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/ses/latest/dg/doc-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-11-08T14:56:23.870738835Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://aws.amazon.com/ses/pricing/", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-08T14:51:24.348272833Z", "changedAt": "2026-11-06T13:23:04.635465647Z", "fingerprint": "45f32c7fe39d" }, { "url": "https://aws.amazon.com/agreement/", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:15:29.873815962Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cc03daebf120" } ], "github": { "repo": "aws/aws-sdk-js-v3", "checkedAt": "2026-11-02T08:33:16.329318522Z", "stars": 3679, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T17:07:41Z", "openIssues": 105, "openPRs": 57, "issuesOpened90d": 23, "issuesClosed90d": 21, "prsMerged90d": 73, "ci": { "branch": "main", "runs": 50, "success": 44, "failure": 6, "other": 0, "latest": "failure", "latestAt": "2026-10-30T18:54:44Z" }, "advisories": [ { "ghsa": "GHSA-6475-r3vj-m8vf", "severity": "low", "published": "2026-01-08T19:59:56Z" } ], "replies": { "sampled": 25, "unanswered": 10, "medianDays": 3.1 } }, "updatedAt": "2026-11-08T19:18:33.410698367Z" }, "streak": { "days": 31, "from": "2026-10-08", "sinceWatching": true, "best": 31 } }, "answer": "Amazon SES scores 73.6 (BB) on agent readiness against SendLayer's 47.7 (D), and leads in every scored category.", "b": { "slug": "sendlayer", "name": "SendLayer", "vendor": "SendLayer, LLC", "vendorUrl": "https://sendlayer.com", "kind": "http-api", "category": "email", "summary": "SendLayer is a transactional email service from SendLayer, LLC, with an SMTP relay, a REST API for sending and email events, webhooks, SDKs in five languages and a hosted MCP server. It is aimed largely at WordPress and small-business sites.", "url": "https://www.anchorterminal.com/tools/sendlayer", "markdownUrl": "https://www.anchorterminal.com/tools/sendlayer.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sendlayer.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sendlayer.json", "dns": "sendlayer.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.sendlayer.com", "packages": [ { "registry": "npm", "name": "sendlayer" }, { "registry": "pypi", "name": "sendlayer" } ], "auth": "api-key", "authNotes": "Bearer API key in the `Authorization` header, created per sending domain in the dashboard (one is made when a domain is authorised). Keys can be labelled and deleted; no scopes or read-only keys were found. The hosted MCP server takes the same key in an `x-sendlayer-api-key` or `Authorization` header.", "pricing": "paid", "pricingNotes": "Plans billed annually. Starter $5 a month for 1,000 emails, Business $15 for 5,000, Growth $25 for 10,000, Scale 20,000+ by quote. A free trial sends up to 200 emails. Accounts that reach their limit are upgraded automatically. 14-day money-back guarantee.", "priceSummary": "$5 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, llms.txt, the OpenAPI file or the pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 5, "popularity": { "githubStars": null, "npmWeekly": 113, "pypiWeekly": 9, "asOf": "2026-11-06" }, "docsUrl": "https://developers.sendlayer.com/", "llmsTxt": "https://developers.sendlayer.com/llms.txt", "openapi": "https://developers.sendlayer.com/api-reference/sendlayer.json", "capabilities": [ "email.send", "email.analytics", "email.domains" ], "tags": [ "hosted", "closed-source", "smtp", "webhooks", "openapi", "llms-txt", "mcp", "remote-mcp", "status-page", "typescript", "python", "php", "ruby", "go" ], "lastRelease": "2026-08-21", "graded": true, "anchor": { "graded": true, "score": 47.7, "grade": "D", "agentReady": false, "rank": 1150, "ranked": true, "rankOf": 1513, "categoryRank": 19, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 40, "payments": 20, "reliability": 48, "schema": 68, "security": 38, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Low-volume transactional mail for WordPress and small sites.", "strengths": [ "Send limits per minute, hour and day are published for each plan", "OpenAPI file, llms.txt and Markdown copies of every developer page", "Official SDKs for Node, Python, PHP, Ruby and Go", "Hosted MCP server at mcp.sendlayer.com with five tools for sending, events and webhooks", "Numbered error codes with messages for each missing or invalid field" ], "weaknesses": [ "No idempotency key on sends, so a retried request can send twice", "API keys can't be scoped or made read-only", "Status history shows 98 automated outage entries in 90 days with no durations or write-ups", "Privacy policy has no date, retention periods, DPA or sub-processor list", "No public changelog, SLA, security.txt or disclosure policy found" ], "agentNotes": [ "Check the email log with `GET /api/v1/events` before retrying a failed send, since sends have no idempotency key", "Keep To and CC at 10 addresses or fewer and BCC at 5, or the API returns error code 20 or 27", "Pace sends to the plan's per-minute limit, 50 on Starter and 120 on Business, and back off on 429", "Pass the API key in a header to mcp.sendlayer.com; the server answers 405 to anything but POST" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.7 } ], "editorialScores": { "ergonomics": 62, "maintenance": 40, "payments": 20, "reliability": 48, "schema": 68, "security": 38, "transparency": 23 }, "provenanceScore": 75, "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": { "install": "npm install sendlayer", "http": "curl https://console.sendlayer.com/api/v1/email -X POST -H \"Authorization: Bearer $SENDLAYER_API_KEY\" -H \"Content-Type: application/json\" -d '{\"From\":{\"name\":\"You\",\"email\":\"you@yourdomain.com\"},\"To\":[{\"name\":\"Person\",\"email\":\"person@example.com\"}],\"Subject\":\"Hello\",\"ContentType\":\"Text\",\"PlainContent\":\"Hello\"}'", "claudeCode": "claude mcp add --scope user --transport http sendlayer-mcp https://mcp.sendlayer.com --header \"Authorization: Bearer YOUR_SENDLAYER_API_KEY\"", "config": { "mcpServers": { "sendlayer": { "headers": { "x-sendlayer-api-key": "YOUR_SENDLAYER_API_KEY" }, "url": "https://mcp.sendlayer.com" } } } }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/sendlayer" }, "area": "communication", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 5, "note": "1,000 emails a month, billed annually" }, { "item": "Business", "unit": "month", "usd": 15, "note": "5,000 emails a month, billed annually" }, { "item": "Growth", "unit": "month", "usd": 25, "note": "10,000 emails a month, billed annually" } ], "provenance": { "legalEntity": "SendLayer, LLC", "domain": "sendlayer.com", "domainRegistered": "2015-07-22", "endpointOnVendorDomain": true, "terms": "https://sendlayer.com/terms-of-service/", "privacy": "https://sendlayer.com/privacy-policy/", "statusPage": "https://status.sendlayer.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms name SendLayer, LLC under Florida law with courts in West Palm Beach. Neither the terms nor the privacy policy carries a date.", "The terms contain no clause on automated access to the website.", "sendlayer.com/robots.txt disallows only WordPress internals, cart and search paths. developers.sendlayer.com allows all but /_next/ and /cdn-cgi/.", "RDAP gives sendlayer.com a registration date of 22 July 2015; the about page says the team started SendLayer in 2022, and the footer copyright runs from 2021.", "/.well-known/security.txt returns 404." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sendlayer.json", "live": { "slug": "sendlayer", "probe": { "target": "https://mcp.sendlayer.com", "method": "get", "lastAt": "2026-11-08T19:19:08.767297119Z", "lastOk": true, "lastStatus": 405, "lastMs": 369, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 328, "p95ms24h": 399, "samples24h": 243, "samples30d": 452, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 196, "ok": 196 } ], "since": "2026-11-06T00:00:00Z" }, "vendorStatus": { "page": "https://status.sendlayer.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T17:50:21.745719934Z" }, "versions": [ { "registry": "npm", "name": "sendlayer", "version": "1.1.0", "seenAt": "2026-11-08T01:36:32.03645962Z" }, { "registry": "pypi", "name": "sendlayer", "version": "1.1.0", "released": "2026-08-21", "seenAt": "2026-11-08T01:36:32.802648319Z" } ], "npmWeekly": 100, "pypiWeekly": 7, "securityTxt": { "url": "https://sendlayer.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-08T16:02:18.713913522Z" }, "llmsTxt": { "url": "https://developers.sendlayer.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-08T15:37:25.017245468Z" }, "domain": { "domain": "sendlayer.com", "registered": "2015-07-22", "source": "https://rdap.verisign.com/com/v1/domain/sendlayer.com", "checkedAt": "2026-11-08T15:05:26.641092909Z" }, "pages": [ { "url": "https://sendlayer.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-08T15:11:18.97007943Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1f5bea738989" }, { "url": "https://sendlayer.com/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-11-08T15:11:21.626011912Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1fbf9877b12a" } ], "mcpTools": { "url": "https://mcp.sendlayer.com", "checkedAt": "2026-11-08T02:01:33.931549444Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:47:41.040426143Z" }, "updatedAt": "2026-11-08T19:19:08.767297119Z" }, "streak": { "days": 2, "from": "2026-11-06", "sinceWatching": true, "best": 2 } }, "edges": [ { "by": 51, "category": "security", "leads": "amazon-ses", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 89, "b": 38 } }, { "by": 45, "category": "maintenance", "leads": "amazon-ses", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 85, "b": 40 } }, { "by": 38, "category": "transparency", "leads": "amazon-ses", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 87, "b": 49 } }, { "by": 27, "category": "reliability", "leads": "amazon-ses", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 75, "b": 48 } }, { "by": 17, "category": "schema", "leads": "amazon-ses", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 85, "b": 68 } }, { "by": 10, "category": "payments", "leads": "amazon-ses", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 30, "b": 20 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "SendLayer, LLC", "name": "Vendor" }, { "a": "https://email.us-east-1.amazonaws.com/v2", "b": "https://mcp.sendlayer.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "none", "name": "Licence" }, { "a": "none", "b": "5", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-08", "b": "2026-08-21", "name": "Last release" }, { "a": "2026-08-14", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "5.2M npm/wk", "b": "113 npm/wk, 9 PyPI/wk", "name": "Popularity" }, { "a": "3.3/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon SES scores 73.6 (BB) on agent readiness against SendLayer's 47.7 (D), and leads in every scored category.", "question": "Which is better for AI agents, Amazon SES or SendLayer?" }, { "answer": "Amazon SES takes an API key or an OAuth sign-in. SendLayer needs an API key.", "question": "Do Amazon SES and SendLayer need an API key?" }, { "answer": "Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and SendLayer at https://mcp.sendlayer.com.", "question": "Can an agent call Amazon SES and SendLayer without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 48", "Schema \u0026 documentation, 85 against 68", "Security \u0026 auth, 89 against 38", "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 85 against 40", "Transparency \u0026 trust, 87 against 49" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "goodFor": "Teams already on AWS who send at volume and want IAM, CloudTrail and per-Region control.", "slug": "amazon-ses", "watchFor": "Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted" }, { "aheadOn": null, "also": null, "goodFor": "Low-volume transactional mail for WordPress and small sites.", "slug": "sendlayer", "watchFor": "No idempotency key on sends, so a retried request can send twice" } ], "history": { "amazon-ses": [ { "causes": [ "evidence", "correction" ], "date": "2026-10-17", "delta": -1.5, "from": 75.1, "fromGrade": "BB", "to": 73.6, "toGrade": "BB" } ], "sendlayer": null }, "job": { "capability": "email.send", "name": "Sending email" }, "others": [ { "json": "https://www.anchorterminal.com/compare/ahasend-vs-amazon-ses.json", "title": "AhaSend API + MCP vs Amazon SES", "url": "https://www.anchorterminal.com/compare/ahasend-vs-amazon-ses" }, { "json": "https://www.anchorterminal.com/compare/ahasend-vs-sendlayer.json", "title": "AhaSend API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/ahasend-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-brevo.json", "title": "Amazon SES vs Brevo API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-brevo" }, { "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-groundmail.json", "title": "Amazon SES vs Groundmail API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-groundmail" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-loops.json", "title": "Amazon SES vs Loops API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-loops" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailersend.json", "title": "Amazon SES vs MailerSend", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailersend" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailgun.json", "title": "Amazon SES vs Mailgun API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailgun" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailjet.json", "title": "Amazon SES vs Mailjet API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailjet" }, { "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/amazon-ses-vs-mailtrap.json", "title": "Amazon SES vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mandrill.json", "title": "Amazon SES vs Mailchimp Transactional (Mandrill)", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mandrill" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-postmark.json", "title": "Amazon SES vs Postmark API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-postmark" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-resend.json", "title": "Amazon SES vs Resend API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-resend" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendgrid.json", "title": "Amazon SES vs Twilio SendGrid", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendgrid" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-smtp2go.json", "title": "Amazon SES vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-zoho-zeptomail.json", "title": "Amazon SES vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-zoho-zeptomail" }, { "json": "https://www.anchorterminal.com/compare/brevo-vs-sendlayer.json", "title": "Brevo API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/brevo-vs-sendlayer" }, { "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/groundmail-vs-sendlayer.json", "title": "Groundmail API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/groundmail-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/loops-vs-sendlayer.json", "title": "Loops API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/loops-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailersend-vs-sendlayer.json", "title": "MailerSend vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailersend-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailgun-vs-sendlayer.json", "title": "Mailgun API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailgun-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailjet-vs-sendlayer.json", "title": "Mailjet API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailjet-vs-sendlayer" }, { "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/mailtrap-vs-sendlayer.json", "title": "Mailtrap Email API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mandrill-vs-sendlayer.json", "title": "Mailchimp Transactional (Mandrill) vs SendLayer", "url": "https://www.anchorterminal.com/compare/mandrill-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/postmark-vs-sendlayer.json", "title": "Postmark API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/postmark-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/resend-vs-sendlayer.json", "title": "Resend API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/resend-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/sendgrid-vs-sendlayer.json", "title": "Twilio SendGrid vs SendLayer", "url": "https://www.anchorterminal.com/compare/sendgrid-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/sendlayer-vs-smtp2go.json", "title": "SendLayer vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/sendlayer-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/sendlayer-vs-zoho-zeptomail.json", "title": "SendLayer vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/sendlayer-vs-zoho-zeptomail" } ], "panel": null, "scores": [ { "amazon-ses": 75, "by": 27, "edge": "amazon-ses", "key": "reliability", "name": "Reliability", "sendlayer": 48, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-ses": 85, "by": 17, "edge": "amazon-ses", "key": "schema", "name": "Schema \u0026 documentation", "sendlayer": 68, "weight": 13 }, { "amazon-ses": 64, "by": 2, "edge": "amazon-ses", "key": "ergonomics", "name": "Agent ergonomics", "sendlayer": 62, "weight": 13 }, { "amazon-ses": 89, "by": 51, "edge": "amazon-ses", "key": "security", "name": "Security \u0026 auth", "sendlayer": 38, "weight": 14 }, { "amazon-ses": 30, "by": 10, "edge": "amazon-ses", "key": "payments", "name": "Payments \u0026 pricing", "sendlayer": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-ses": 85, "by": 45, "edge": "amazon-ses", "key": "maintenance", "name": "Maintenance \u0026 community", "sendlayer": 40, "weight": 7 }, { "amazon-ses": 87, "by": 38, "edge": "amazon-ses", "key": "transparency", "name": "Transparency \u0026 trust", "sendlayer": 49, "weight": 7 } ], "summary": "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.", "tasks": null, "tutorials": [], "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer", "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer.min.md" }, "markdown": "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.\n\n- 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\n- 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\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### Amazon SES (BB)\n\nGood for: Teams already on AWS who send at volume and want IAM, CloudTrail and per-Region control.\n\nAhead on:\n- Reliability, 75 against 48\n- Schema \u0026 documentation, 85 against 68\n- Security \u0026 auth, 89 against 38\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 85 against 40\n- Transparency \u0026 trust, 87 against 49\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted\n\n### SendLayer (D)\n\nGood for: Low-volume transactional mail for WordPress and small sites.\n\nWatch for: No idempotency key on sends, so a retried request can send twice\n\n\n## Why the edge\n\n### Security \u0026 auth: Amazon SES +51\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: Amazon SES +45\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: Amazon SES +38\n\n- 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.\n- 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.\n\n### Reliability: Amazon SES +27\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: Amazon SES +17\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Amazon SES +10\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Amazon SES | SendLayer | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 48 | Amazon SES +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 68 | Amazon SES +17 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 62 | Amazon SES +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 89 | 38 | Amazon SES +51 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Amazon SES +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 40 | Amazon SES +45 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 87 | 49 | Amazon SES +38 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **73.6 · BB** | **47.7 · D** | |\n\n## Facts side by side\n\n| Fact | Amazon SES | SendLayer |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | SendLayer, LLC |\n| Hosted endpoint | `https://email.us-east-1.amazonaws.com/v2` | `https://mcp.sendlayer.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Apache-2.0 | none |\n| Tools exposed | none | 5 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-08 | 2026-08-21 |\n| Terms last updated | 2026-08-14 | no date given |\n| Privacy policy last updated | 2026-05-18 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 5.2M npm/wk | 113 npm/wk, 9 PyPI/wk |\n| Agent reviews | 3.3/5 (8) | none |\n\n## How the scores have moved\n\n### Amazon SES\n\n- -1.5 on 17 October 2026: new evidence, correction\n\n### SendLayer\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Amazon SES\n\n1. Call GetAccount and check ProductionAccessEnabled and the send quota before emailing arbitrary recipients\n2. Verify the From domain as an identity first. Sends from unverified identities fail even in production\n3. Use the mailbox simulator (success@simulator.amazonses.com) to test bounces and complaints without hurting reputation\n4. Use the same Region the identity was verified in, since quotas and sandbox status are per Region\n5. On a throttling error, wait and retry the send. SES drops messages over quota rather than queueing them\n\n### SendLayer\n\n1. Check the email log with `GET /api/v1/events` before retrying a failed send, since sends have no idempotency key\n2. Keep To and CC at 10 addresses or fewer and BCC at 5, or the API returns error code 20 or 27\n3. Pace sends to the plan's per-minute limit, 50 on Starter and 120 on Business, and back off on 429\n4. Pass the API key in a header to mcp.sendlayer.com; the server answers 405 to anything but POST\n\n## Questions\n\n### Which is better for AI agents, Amazon SES or SendLayer?\n\nAmazon SES scores 73.6 (BB) on agent readiness against SendLayer's 47.7 (D), and leads in every scored category.\n\n### Do Amazon SES and SendLayer need an API key?\n\nAmazon SES takes an API key or an OAuth sign-in. SendLayer needs an API key.\n\n### Can an agent call Amazon SES and SendLayer without installing anything?\n\nYes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and SendLayer at https://mcp.sendlayer.com.\n\n\n## For agents\n\n- 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\n- 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`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-ses.json and https://www.anchorterminal.com/api/v1/tools/sendlayer.json\n\n## Other comparisons with Amazon SES or SendLayer\n\n- [AhaSend API + MCP vs Amazon SES](https://www.anchorterminal.com/compare/ahasend-vs-amazon-ses.md)\n- [AhaSend API + MCP vs SendLayer](https://www.anchorterminal.com/compare/ahasend-vs-sendlayer.md)\n- [Amazon SES vs Brevo API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-brevo.md)\n- [Amazon SES vs Cloudflare Email Service](https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.md)\n- [Amazon SES vs Groundmail API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-groundmail.md)\n- [Amazon SES vs Loops API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-loops.md)\n- [Amazon SES vs MailerSend](https://www.anchorterminal.com/compare/amazon-ses-vs-mailersend.md)\n- [Amazon SES vs Mailgun API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailgun.md)\n- [Amazon SES vs Mailjet API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailjet.md)\n- [Amazon SES vs MailPace](https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.md)\n- [Amazon SES vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailtrap.md)\n- [Amazon SES vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/amazon-ses-vs-mandrill.md)\n- [Amazon SES vs Postmark API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-postmark.md)\n- [Amazon SES vs Resend API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-resend.md)\n- [Amazon SES vs Twilio SendGrid](https://www.anchorterminal.com/compare/amazon-ses-vs-sendgrid.md)\n- [Amazon SES vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-smtp2go.md)\n- [Amazon SES vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/amazon-ses-vs-zoho-zeptomail.md)\n- [Brevo API + MCP vs SendLayer](https://www.anchorterminal.com/compare/brevo-vs-sendlayer.md)\n- [Cloudflare Email Service vs SendLayer](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendlayer.md)\n- [Groundmail API + MCP vs SendLayer](https://www.anchorterminal.com/compare/groundmail-vs-sendlayer.md)\n- [Loops API + MCP vs SendLayer](https://www.anchorterminal.com/compare/loops-vs-sendlayer.md)\n- [MailerSend vs SendLayer](https://www.anchorterminal.com/compare/mailersend-vs-sendlayer.md)\n- [Mailgun API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailgun-vs-sendlayer.md)\n- [Mailjet API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailjet-vs-sendlayer.md)\n- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md)\n- [Mailtrap Email API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailtrap-vs-sendlayer.md)\n- [Mailchimp Transactional (Mandrill) vs SendLayer](https://www.anchorterminal.com/compare/mandrill-vs-sendlayer.md)\n- [Postmark API + MCP vs SendLayer](https://www.anchorterminal.com/compare/postmark-vs-sendlayer.md)\n- [Resend API + MCP vs SendLayer](https://www.anchorterminal.com/compare/resend-vs-sendlayer.md)\n- [Twilio SendGrid vs SendLayer](https://www.anchorterminal.com/compare/sendgrid-vs-sendlayer.md)\n- [SendLayer vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/sendlayer-vs-smtp2go.md)\n- [SendLayer vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/sendlayer-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-08", "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": "Amazon SES vs SendLayer", "url": "" } ], "description": "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.", "facts": [ "Amazon SES BB 73.6", "SendLayer D 47.7", "scores" ], "h1": "Amazon SES vs SendLayer", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-ses-vs-sendlayer", "published": "2026-10-01", "section": "tools", "title": "Amazon SES vs SendLayer for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-08", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer" }, "tokens": { "markdown": 4750, "slim": 980 }, "version": 1 }