{ "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": 1510, "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-07T19:21:51.791604115Z", "lastOk": true, "lastStatus": 404, "lastMs": 281, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 272, "p95ms24h": 363, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "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": 197, "ok": 197 } ] }, "versions": [ { "registry": "github", "name": "aws/aws-sdk-js-v3", "version": "v3.1164.0", "released": "2026-11-06", "seenAt": "2026-11-06T23:05:43.497627611Z" }, { "registry": "npm", "name": "@aws-sdk/client-sesv2", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:43.155327297Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.126", "released": "2026-11-06", "seenAt": "2026-11-06T23:05:43.36943754Z" } ], "githubStars": 3679, "npmWeekly": 8772507, "pypiWeekly": 637851852, "securityTxt": { "url": "https://amazonaws.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-16T16:25:03.000Z", "checkedAt": "2026-11-07T16:01:20.771828423Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/ses/latest/dg/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:29.83319967Z" }, "domain": { "domain": "amazonaws.com", "registered": "2005-08-18", "source": "https://rdap.verisign.com/com/v1/domain/amazonaws.com", "checkedAt": "2026-11-01T14:19:22.344066529Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/ses/latest/dg/doc-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:05:26.27242891Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://aws.amazon.com/ses/pricing/", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:00:14.597722294Z", "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-07T19:21:51.791604115Z" } }, "answer": "Amazon SES scores 73.6 (BB) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on agent ergonomics.", "b": { "slug": "mailpace", "name": "MailPace", "vendor": "OhMySMTP Ltd", "vendorUrl": "https://mailpace.com", "kind": "http-api", "category": "email", "summary": "MailPace is a UK transactional email service, formerly OhMySMTP, hosted in the EU. It sends mail through an HTTPS API or SMTP, turns inbound mail into webhooks and has a Domains and Email Status API.", "url": "https://www.anchorterminal.com/tools/mailpace", "markdownUrl": "https://www.anchorterminal.com/tools/mailpace.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mailpace.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mailpace.json", "dns": "mailpace.grade.anchorterminal.com", "repo": "https://github.com/mailpace/mailpace-mcp", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@mailpace/mailpace.js" } ], "auth": "api-key", "authNotes": "Each domain has its own server token, sent in the `MailPace-Server-Token` header, which can send from that domain and read its email status. An organisation token in `MailPace-Organization-Token` manages domains and domain tokens through the Domains API, including revoking them. Both are made in the dashboard after a browser signup.", "pricing": "paid", "pricingNotes": "$10 a month includes 10,000 emails sent or received, then $1 per 1,000, per the Paddle prices the pricing page loads and the comparison pages ($100 for 100,000, $1,000 for 1 million). A free plan of up to 100 emails a month is given on request by email. Paddle is the merchant of record; card, PayPal, Apple Pay or Google Pay.", "priceSummary": "$10 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs repository, the pricing page or the MCP server source (checked 2026-11-06). Payment is by Paddle subscription; the FAQ says crypto isn't accepted.", "endpoints": [] }, "toolCount": 12, "popularity": { "githubStars": 1, "npmWeekly": 207, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.mailpace.com/", "capabilities": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "tags": [ "hosted", "closed-source", "smtp", "webhooks", "idempotency", "status-page", "sla", "eu", "mcp", "typescript", "ruby", "go", "php" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 58.4, "grade": "C", "agentReady": false, "rank": 754, "ranked": true, "rankOf": 1510, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 65, "payments": 25, "reliability": 70, "schema": 54, "security": 50, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.", "bestFor": "Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.", "strengths": [ "Sends accept an `Idempotency-Key` header kept for 24 hours, so a retry after a timeout doesn't send twice", "Per-domain server tokens limit a leaked key to one domain, and organisation tokens can create and revoke them by API", "Webhooks are signed with Ed25519 and inbound mail is retried five times before it fails", "Status page on Upptime with GitHub issues as incident reports, and a 99% monthly availability promise with credits in the terms", "Sub-processors and their locations are listed, and mail is kept 30 days plus 7 in backups per the DPA" ], "weaknesses": [ "No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages", "Rate limits aren't published; the docs say they vary by organisation age, plan and history", "No free plan without emailing support, and the paid plan starts at $10 a month", "MCP server 2.0.0 exists only in the repository; npm and the MCP registry had nothing for it on 6 November 2026", "No security.txt, disclosure policy or certification found" ], "agentNotes": [ "Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token", "Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403", "On 429 `You are sending emails too quickly` back off; no Retry-After is documented", "Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms", "Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.4 } ], "editorialScores": { "ergonomics": 71, "maintenance": 65, "payments": 25, "reliability": 70, "schema": 54, "security": 50, "transparency": 69 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://app.mailpace.com/api/v1/send -X POST -H \"Accept: application/json\" -H \"Content-Type: application/json\" -H \"MailPace-Server-Token: $MAILPACE_TOKEN\" -H \"Idempotency-Key: $(uuidgen)\" -d '{\"from\":\"you@yourdomain.com\",\"to\":\"person@example.com\",\"subject\":\"Hello\",\"textbody\":\"Hello\"}'" }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/mailpace" }, "area": "communication", "unitPrices": [ { "item": "Scaling plan", "unit": "month", "usd": 10, "note": "includes 10,000 emails sent or received" }, { "item": "Emails beyond 10,000", "unit": "1k-emails", "usd": 1 } ], "provenance": { "legalEntity": "OhMySMTP Ltd", "domain": "mailpace.com", "domainRegistered": "2022-01-10", "endpointOnVendorDomain": true, "terms": "https://mailpace.com/terms", "privacy": "https://mailpace.com/privacy", "statusPage": "https://status.mailpace.com", "changelog": "https://mailpace.com/category/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms and privacy policy name OhMySMTP Ltd, incorporated in England and Wales, company number 13200428. Companies House lists two active directors.", "Terms last updated 9 January 2026, privacy policy 30 August 2026, DPA updated in October 2026 per the landing repository.", "mailpace.com/robots.txt allows all paths. The terms contain no clause on automated access to the website beyond the usual licence limits.", "RDAP gives mailpace.com a registration date of 10 January 2022; the service ran as OhMySMTP before that.", "/.well-known/security.txt returns 404 on mailpace.com and app.mailpace.com." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mailpace.json", "live": { "slug": "mailpace", "vendorStatus": { "page": "https://status.mailpace.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:01.553362214Z" }, "versions": [ { "registry": "npm", "name": "@mailpace/mailpace.js", "version": "0.1.3", "seenAt": "2026-11-06T23:42:02.752996422Z" } ], "githubStars": 1, "npmWeekly": 207, "securityTxt": { "url": "https://mailpace.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:07.630537329Z" }, "pages": [ { "url": "https://mailpace.com/category/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:13:40.841899008Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "38f92a159d1b" }, { "url": "https://mailpace.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:45.28058492Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e6b0fea49c1d" }, { "url": "https://mailpace.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:45.480605157Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "24f1eed01dad" } ], "updatedAt": "2026-11-07T16:01:07.630537329Z" } }, "edges": [ { "by": 39, "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": "Per-domain server tokens that can only send from and read status for their domain, and an organisation token that creates, renames and revokes domain tokens through the Domains API. Tokens travel in headers only. The authentication page still tells users to contact support to regenerate a leaked token (25 of 30). No read-only token. A domain token can't touch other domains, and the unpublished MCP server has an optional recipient allowlist. No approval step on the hosted API (8 of 20). Inbound mail reaches the customer's webhook as untrusted content, and Email Status returns bounce text. The MCP README warns about prompt injection and suggests the allowlist (9 of 15). The dashboard keeps sent mail for 30 days; no log of API calls was found (6 of 15). No security.txt (404 on mailpace.com and app.mailpace.com), no disclosure policy, bug bounty, SOC 2 or ISO 27001. WebAuthn-only two-factor sign-in and Ed25519-signed webhooks are documented (2 of 20). Total 50." }, "scores": { "a": 89, "b": 50 } }, { "by": 31, "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": "No OpenAPI or other machine-readable contract for the HTTPS API. The MCP server's 12 tools have typed zod inputs and output schemas, but that server isn't published yet, so partial credit (8 of 25). llms.txt answers 404 on mailpace.com and docs.mailpace.com, and no Markdown copies are served (0). The reference states what each endpoint does, and the introduction says when not to use it (transactional only, no batch, no static IPs) (12 of 20). Field tables give type, examples and required or optional, with enums for status, sort and direction and the 50-recipient cap in text (9 of 15). Examples in curl and six languages and a full table of error responses with messages, though several listed messages have a broken quote (`{\"error:\"...`) and the send reference says 30 MB where the home page says 25 MB (12 of 15). Version in the path with a promise that an old version runs until a published end-of-life date, and dated changelog posts (13 of 15). Total 54." }, "scores": { "a": 85, "b": 54 } }, { "by": 20, "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": "Email Status API documented on 22 October 2026, and the MCP server rewritten as 2.0.0 on 4 November 2026, two days before this check (30). In the 90 days from 8 August, the Q3 changelog post of 31 August, the Email Status docs of 22 October, a mailpace-rails push on 17 October and the MCP rewrite, but only one changelog post (15 of 20). A closed service with email support. Three pull requests to the MCP repository from 2025 have no reply (8 of 15). Not in the official MCP registry (search for mailpace returned nothing on 6 November). The Node library was last pushed in October 2024 and Go in January 2024, while mailpace-rails is current (7 of 15). The MCP server gained CI with tests on 4 November; the older SDKs weren't checked for CI (5 of 10). Total 65." }, "scores": { "a": 85, "b": 65 } }, { "by": 12, "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 hosted service under terms that name OhMySMTP Ltd with its company number. The MCP server, SDKs, landing site and status page are MIT (18 of 30). The privacy policy (30 August 2026), the pricing page and the DPA agree on retention, 30 days in the dashboard and 7 more in backups, 37 days at most (25 of 30). The API reference promises an old version runs until a published end-of-life date, and the terms list dated changes. The terms also say changes apply immediately (8 of 20). Sub-processors listed with purpose and location, Freethought hosting in the EU, Hetzner backups in Germany, AppSignal in Amsterdam, Paddle in the UK and Tutanota in Germany (18 of 20). Total 69." }, "scores": { "a": 87, "b": 75 } }, { "by": 7, "category": "ergonomics", "leads": "mailpace", "name": "Agent ergonomics", "reasons": { "a": "No SES-specific MCP. The AWS MCP Server with an amazon-ses skill covers sending setup only. API responses are compact and list actions take PageSize and NextToken (15). Paginated lists and filters on suppression and contact lists (15). SendEmail declares eight typed errors, among them MessageRejected, MailFromDomainNotVerifiedException, SendingPausedException and TooManyRequestsException (16). No idempotency token on SendEmail, so a retried send can go out twice. SDK retries cover throttling (8). SDKs in every major language, but every call needs SigV4 and a send needs a nested Content structure (10).", "b": "Responses are small, the send returns an id and status and Email Status returns one email (18 of 25). Only the domains list takes `limit`, `offset`, `sort` and `direction`; there is no endpoint to list or search sent mail (8 of 20). Errors are JSON with a human message and an HTTP status for each case in the documented table, with no stable error codes (14 of 20). `Idempotency-Key` on sends, kept 24 hours per token, and failed validations are not stored so they can be retried. The MCP server marks send as not idempotent and revoke as destructive (18 of 20). A send needs from, to, a subject and a body; official libraries for Node, Rails, Go and PHP transports and an SMTP route (13 of 15). Total 71." }, "scores": { "a": 64, "b": 71 } }, { "by": 5, "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 public Upptime status page at status.mailpace.com, driven by the mailpace/status repository, with monitors for the application, SMTP, docs, blog and landing page and GitHub issues as incident reports (20). The 90 days from 8 August hold two incidents, an application outage on 22 September 2026 that the operator put down to an upstream provider returning 5xx (issue open for two minutes), and SMTP down on 2 November 2026 for about 35 minutes, which leaves SMTP at 99.65% for the week. Minor incidents only (20). No rate limit numbers are published; the docs say limits vary by organisation age, plan and history (0). A documented 429 with its message, no Retry-After or backoff guidance, and an `Idempotency-Key` on sends with written retry rules (10 of 15). The terms guarantee 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes (10). The API is at v1 with no beta label (10). Total 70." }, "scores": { "a": 75, "b": 70 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "OhMySMTP Ltd", "name": "Vendor" }, { "a": "https://email.us-east-1.amazonaws.com/v2", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "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": "12", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-08", "b": "2026-10-22", "name": "Last release" }, { "a": "2026-08-14", "b": "2026-01-09", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-08-30", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "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": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "5.2M npm/wk", "b": "1 stars, 207 npm/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 MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on agent ergonomics.", "question": "Which is better for AI agents, Amazon SES or MailPace?" }, { "answer": "Amazon SES takes an API key or an OAuth sign-in. MailPace needs an API key.", "question": "Do Amazon SES and MailPace need an API key?" }, { "answer": "Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2. No hosted endpoint is listed for MailPace.", "question": "Can an agent call Amazon SES and MailPace without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 70", "Schema \u0026 documentation, 85 against 54", "Security \u0026 auth, 89 against 50", "Payments \u0026 pricing, 30 against 25", "Maintenance \u0026 community, 85 against 65", "Transparency \u0026 trust, 87 against 75" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "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": [ "Agent ergonomics, 71 against 64" ], "also": null, "goodFor": "Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.", "slug": "mailpace", "watchFor": "No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages" } ], "history": { "amazon-ses": [ { "causes": [ "evidence", "correction" ], "date": "2026-10-17", "delta": -1.5, "from": 75.1, "fromGrade": "BB", "to": 73.6, "toGrade": "BB" } ], "mailpace": 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-mailpace.json", "title": "AhaSend API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/ahasend-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-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-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-sendlayer.json", "title": "Amazon SES vs SendLayer", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer" }, { "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-mailpace.json", "title": "Brevo API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/brevo-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.json", "title": "Cloudflare Email Service vs MailPace", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/groundmail-vs-mailpace.json", "title": "Groundmail API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/groundmail-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/loops-vs-mailpace.json", "title": "Loops API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/loops-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailersend-vs-mailpace.json", "title": "MailerSend vs MailPace", "url": "https://www.anchorterminal.com/compare/mailersend-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailgun-vs-mailpace.json", "title": "Mailgun API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/mailgun-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailjet-vs-mailpace.json", "title": "Mailjet API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/mailjet-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.json", "title": "MailPace vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-mandrill.json", "title": "MailPace vs Mailchimp Transactional (Mandrill)", "url": "https://www.anchorterminal.com/compare/mailpace-vs-mandrill" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-postmark.json", "title": "MailPace vs Postmark API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-postmark" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-resend.json", "title": "MailPace vs Resend API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-resend" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.json", "title": "MailPace vs Twilio SendGrid", "url": "https://www.anchorterminal.com/compare/mailpace-vs-sendgrid" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.json", "title": "MailPace vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailpace-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.json", "title": "MailPace vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.json", "title": "MailPace vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail" } ], "panel": null, "scores": [ { "amazon-ses": 75, "by": 5, "edge": "amazon-ses", "key": "reliability", "mailpace": 70, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-ses": 85, "by": 31, "edge": "amazon-ses", "key": "schema", "mailpace": 54, "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-ses": 64, "by": 7, "edge": "mailpace", "key": "ergonomics", "mailpace": 71, "name": "Agent ergonomics", "weight": 13 }, { "amazon-ses": 89, "by": 39, "edge": "amazon-ses", "key": "security", "mailpace": 50, "name": "Security \u0026 auth", "weight": 14 }, { "amazon-ses": 30, "by": 5, "edge": "amazon-ses", "key": "payments", "mailpace": 25, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-ses": 85, "by": 20, "edge": "amazon-ses", "key": "maintenance", "mailpace": 65, "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-ses": 87, "by": 12, "edge": "amazon-ses", "key": "transparency", "mailpace": 75, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Amazon SES scores 73.6 (BB) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on agent ergonomics. 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.", "mailpace": "A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace", "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.min.md" }, "markdown": "Amazon SES scores 73.6 (BB) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on agent ergonomics. Both do sending email.\n\n- Amazon SES: grade BB, 73.6/100, rank #100 of 1510. Markdown https://www.anchorterminal.com/tools/amazon-ses.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-ses.json\n- MailPace: grade C, 58.4/100, rank #754 of 1510. Markdown https://www.anchorterminal.com/tools/mailpace.md · JSON https://www.anchorterminal.com/api/v1/tools/mailpace.json\n- Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md\n- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md\n\n## Which one, for what\n\n### 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 70\n- Schema \u0026 documentation, 85 against 54\n- Security \u0026 auth, 89 against 50\n- Payments \u0026 pricing, 30 against 25\n- Maintenance \u0026 community, 85 against 65\n- Transparency \u0026 trust, 87 against 75\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\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### MailPace (C)\n\nGood for: Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.\n\nAhead on:\n- Agent ergonomics, 71 against 64\n\nWatch for: No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages\n\n\n## Why the edge\n\n### Security \u0026 auth: Amazon SES +39\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- MailPace (50): Per-domain server tokens that can only send from and read status for their domain, and an organisation token that creates, renames and revokes domain tokens through the Domains API. Tokens travel in headers only. The authentication page still tells users to contact support to regenerate a leaked token (25 of 30). No read-only token. A domain token can't touch other domains, and the unpublished MCP server has an optional recipient allowlist. No approval step on the hosted API (8 of 20). Inbound mail reaches the customer's webhook as untrusted content, and Email Status returns bounce text. The MCP README warns about prompt injection and suggests the allowlist (9 of 15). The dashboard keeps sent mail for 30 days; no log of API calls was found (6 of 15). No security.txt (404 on mailpace.com and app.mailpace.com), no disclosure policy, bug bounty, SOC 2 or ISO 27001. WebAuthn-only two-factor sign-in and Ed25519-signed webhooks are documented (2 of 20). Total 50.\n\n### Schema \u0026 documentation: Amazon SES +31\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- MailPace (54): No OpenAPI or other machine-readable contract for the HTTPS API. The MCP server's 12 tools have typed zod inputs and output schemas, but that server isn't published yet, so partial credit (8 of 25). llms.txt answers 404 on mailpace.com and docs.mailpace.com, and no Markdown copies are served (0). The reference states what each endpoint does, and the introduction says when not to use it (transactional only, no batch, no static IPs) (12 of 20). Field tables give type, examples and required or optional, with enums for status, sort and direction and the 50-recipient cap in text (9 of 15). Examples in curl and six languages and a full table of error responses with messages, though several listed messages have a broken quote (`{\"error:\"...`) and the send reference says 30 MB where the home page says 25 MB (12 of 15). Version in the path with a promise that an old version runs until a published end-of-life date, and dated changelog posts (13 of 15). Total 54.\n\n### Maintenance \u0026 community: Amazon SES +20\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- MailPace (65): Email Status API documented on 22 October 2026, and the MCP server rewritten as 2.0.0 on 4 November 2026, two days before this check (30). In the 90 days from 8 August, the Q3 changelog post of 31 August, the Email Status docs of 22 October, a mailpace-rails push on 17 October and the MCP rewrite, but only one changelog post (15 of 20). A closed service with email support. Three pull requests to the MCP repository from 2025 have no reply (8 of 15). Not in the official MCP registry (search for mailpace returned nothing on 6 November). The Node library was last pushed in October 2024 and Go in January 2024, while mailpace-rails is current (7 of 15). The MCP server gained CI with tests on 4 November; the older SDKs weren't checked for CI (5 of 10). Total 65.\n\n### Transparency \u0026 trust: Amazon SES +12\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- MailPace (75): Closed hosted service under terms that name OhMySMTP Ltd with its company number. The MCP server, SDKs, landing site and status page are MIT (18 of 30). The privacy policy (30 August 2026), the pricing page and the DPA agree on retention, 30 days in the dashboard and 7 more in backups, 37 days at most (25 of 30). The API reference promises an old version runs until a published end-of-life date, and the terms list dated changes. The terms also say changes apply immediately (8 of 20). Sub-processors listed with purpose and location, Freethought hosting in the EU, Hetzner backups in Germany, AppSignal in Amsterdam, Paddle in the UK and Tutanota in Germany (18 of 20). Total 69.\n\n### Agent ergonomics: MailPace +7\n\n- Amazon SES (64): No SES-specific MCP. The AWS MCP Server with an amazon-ses skill covers sending setup only. API responses are compact and list actions take PageSize and NextToken (15). Paginated lists and filters on suppression and contact lists (15). SendEmail declares eight typed errors, among them MessageRejected, MailFromDomainNotVerifiedException, SendingPausedException and TooManyRequestsException (16). No idempotency token on SendEmail, so a retried send can go out twice. SDK retries cover throttling (8). SDKs in every major language, but every call needs SigV4 and a send needs a nested Content structure (10).\n- MailPace (71): Responses are small, the send returns an id and status and Email Status returns one email (18 of 25). Only the domains list takes `limit`, `offset`, `sort` and `direction`; there is no endpoint to list or search sent mail (8 of 20). Errors are JSON with a human message and an HTTP status for each case in the documented table, with no stable error codes (14 of 20). `Idempotency-Key` on sends, kept 24 hours per token, and failed validations are not stored so they can be retried. The MCP server marks send as not idempotent and revoke as destructive (18 of 20). A send needs from, to, a subject and a body; official libraries for Node, Rails, Go and PHP transports and an SMTP route (13 of 15). Total 71.\n\n### Reliability: Amazon SES +5\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- MailPace (70): Graded with the hosted lines. A public Upptime status page at status.mailpace.com, driven by the mailpace/status repository, with monitors for the application, SMTP, docs, blog and landing page and GitHub issues as incident reports (20). The 90 days from 8 August hold two incidents, an application outage on 22 September 2026 that the operator put down to an upstream provider returning 5xx (issue open for two minutes), and SMTP down on 2 November 2026 for about 35 minutes, which leaves SMTP at 99.65% for the week. Minor incidents only (20). No rate limit numbers are published; the docs say limits vary by organisation age, plan and history (0). A documented 429 with its message, no Retry-After or backoff guidance, and an `Idempotency-Key` on sends with written retry rules (10 of 15). The terms guarantee 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes (10). The API is at v1 with no beta label (10). Total 70.\n\n## Score by category\n\n| Category | Weight | Amazon SES | MailPace | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 70 | Amazon SES +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 54 | Amazon SES +31 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 71 | MailPace +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 89 | 50 | Amazon SES +39 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | Amazon SES +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 65 | Amazon SES +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 87 | 75 | Amazon SES +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **73.6 · BB** | **58.4 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon SES | MailPace |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | OhMySMTP Ltd |\n| Hosted endpoint | `https://email.us-east-1.amazonaws.com/v2` | no (local only) |\n| Transports | HTTP | 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 | 12 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-08 | 2026-10-22 |\n| Terms last updated | 2026-08-14 | 2026-01-09 |\n| Privacy policy last updated | 2026-05-18 | 2026-08-30 |\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 | yes |\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 | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 5.2M npm/wk | 1 stars, 207 npm/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### MailPace\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**MailPace.** A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.\n\n## Before you call either\n\n### 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### MailPace\n\n1. Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token\n2. Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403\n3. On 429 `You are sending emails too quickly` back off; no Retry-After is documented\n4. Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms\n5. Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned\n\n## Questions\n\n### Which is better for AI agents, Amazon SES or MailPace?\n\nAmazon SES scores 73.6 (BB) on agent readiness against MailPace's 58.4 (C), and leads in 6 of 7 scored categories. MailPace leads on agent ergonomics.\n\n### Do Amazon SES and MailPace need an API key?\n\nAmazon SES takes an API key or an OAuth sign-in. MailPace needs an API key.\n\n### Can an agent call Amazon SES and MailPace without installing anything?\n\nAmazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2. No hosted endpoint is listed for MailPace.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-ses\", \"b\": \"mailpace\"}`. From a terminal: `anchor compare amazon-ses mailpace`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-ses.json and https://www.anchorterminal.com/api/v1/tools/mailpace.json\n\n## Other comparisons with Amazon SES or MailPace\n\n- [AhaSend API + MCP vs Amazon SES](https://www.anchorterminal.com/compare/ahasend-vs-amazon-ses.md)\n- [AhaSend API + MCP vs MailPace](https://www.anchorterminal.com/compare/ahasend-vs-mailpace.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 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 SendLayer](https://www.anchorterminal.com/compare/amazon-ses-vs-sendlayer.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 MailPace](https://www.anchorterminal.com/compare/brevo-vs-mailpace.md)\n- [Cloudflare Email Service vs MailPace](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.md)\n- [Groundmail API + MCP vs MailPace](https://www.anchorterminal.com/compare/groundmail-vs-mailpace.md)\n- [Loops API + MCP vs MailPace](https://www.anchorterminal.com/compare/loops-vs-mailpace.md)\n- [MailerSend vs MailPace](https://www.anchorterminal.com/compare/mailersend-vs-mailpace.md)\n- [Mailgun API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailgun-vs-mailpace.md)\n- [Mailjet API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailjet-vs-mailpace.md)\n- [MailPace vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.md)\n- [MailPace vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/mailpace-vs-mandrill.md)\n- [MailPace vs Postmark API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-postmark.md)\n- [MailPace vs Resend API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-resend.md)\n- [MailPace vs Twilio SendGrid](https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.md)\n- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md)\n- [MailPace vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.md)\n- [MailPace vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon SES vs MailPace", "url": "" } ], "description": "Amazon SES scores 73.6 (BB) to MailPace's 58.4 (C) for sending email. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon SES BB 73.6", "MailPace C 58.4", "scores" ], "h1": "Amazon SES vs MailPace", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-ses-vs-mailpace", "published": "2026-10-01", "section": "tools", "title": "Amazon SES vs MailPace for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace" }, "tokens": { "markdown": 5300, "slim": 3280 }, "version": 1 }