Head to head · Sending email · October 2026 research run

Amazon SES vs Postmark API + MCP

Amazon SES scores 75.5 (BB) on agent readiness against Postmark API + MCP's 67.4 (B), and leads in 5 of 7 scored categories. Postmark API + MCP leads on agent ergonomics and payments & pricing. Both do sending email.

Best email delivery APIs for AI agents · All 174 email comparisons

Which one, for what

Amazon SES BB

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

Ahead on

  • Reliability, 75 against 60
  • Security & auth, 89 against 63
  • Maintenance & community, 85 against 80
  • Transparency & trust, 87 against 78

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Postmark API + MCP loses 3 points for them

Watch for

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

Postmark API + MCP B

Best for Transactional mail where deliverability and a small, well-annotated MCP matter more than a free tier.

Ahead on

  • Agent ergonomics, 79 against 64
  • Payments & pricing, 60 against 45

Also in its favour

  • Runs on your own machine

Watch for

No OpenAPI spec and no published request-rate limit

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Amazon SES +26

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.

Postmark API + MCP 63

Server tokens limited to one server and a separate account token for account-level calls, plus IP allowlisting for API sending since 27 August and 2FA on every plan since 23 September. No per-scope tokens (22). A server token can't reach other servers, the MCP annotations let clients confirm writes, and WEBHOOK_URL_ALLOWLIST limits where createWebhook can point (12). The MCP README names the prompt-injection risk and the controls (dedicated token, client approval, the allowlist). Bounce dumps carry text from remote servers (12). Message activity kept 45 days, and the MCP writes one JSON log line per call with addresses masked (12). The security page, re-read on 1 November, names a SOC 1 data centre, payments through Stripe and regular audits by security firms, but no SOC 2 or ISO 27001 of Postmark's own, no disclosure policy, and /.well-known/security.txt answered 404. That's below mailersend and contactsplus (8 each, a disclosure policy with discretionary bounties) (5). 22 + 12 + 12 + 12 + 5 = 63.

Reliability Amazon SES +15

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.

Postmark API + MCP 60

Status page at status.postmarkapp.com (Sorry) with monthly history (20). On 1 November its robots.txt answered 406 with an empty body, which this run treats as blocked, so the history wasn't re-read. Per the 1 October read, the incidents inside the 90-day window that starts on 3 August were sending delays on 15 August, open-webhook delays on 19 August, 70 minutes of web-app errors on 17 September and sending delays of 20 minutes on 22 September and 18 minutes on 28 September with mail queued and not lost, plus planned maintenance on 7 August, all minor. The window from 2 October to 1 November is unread and isn't credited, so the line stays at the 1 October award, as mailtrap's was held when its status host refused us (20). Batch limits are published (500 messages, 50 MB a call) but no request-rate limit, re-read on 1 November (5). A 429 is documented with advice to reduce the rate, with no Retry-After and no idempotency key for sends (5). No SLA on the pricing page, re-read on 1 November (0). GA (10). 20 + 20 + 5 + 5 + 0 + 10 = 60.

Agent ergonomics Postmark API + MCP +15

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

Postmark API + MCP 79

24 tools and no toolsets, counted in the source on 1 November (15). count and offset with the 10,000 cap stated in the descriptions, filters on searches, and a truncation notice when listTemplates hits 100 (17). Over 40 documented error codes, and startup errors name the missing variable and link to the fix (18). Every tool carries readOnlyHint, destructiveHint and idempotentHint, with 12 read-only and the deletes flagged destructive. No idempotency key for sends (15). DEFAULT_SENDER_EMAIL and DEFAULT_MESSAGE_STREAM cut required fields, and there are official Node and Python SDKs (14). 15 + 17 + 18 + 15 + 14 = 79.

Payments & pricing Postmark API + MCP +15

Amazon SES 45

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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Postmark API + MCP 60

No x402, MPP or L402 (0). Prices and per-1,000 overage ($1.80, $1.30, $1.20) published without login, re-read on 1 November (20). Developer plan of 100 emails a month with no card (20). Browser signup and a manual account review before sending outside your own domains (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Amazon SES +9

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.

Postmark API + MCP 78

Closed service with published terms and an MIT MCP server (20). Message content and metadata deleted after 45 days, retention adjustable up to 365 days on Pro and Platform, suppressions kept indefinitely, and a DPA with standard contractual clauses, re-read on 1 November (26). No deprecation policy or dated deprecation notices found (5). Two named hosting companies, Deft near Chicago and AWS, US hosting only, with change notifications per the 1 October check (18). 20 + 26 + 5 + 18 = 69.

Maintenance & community Amazon SES +5

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.

Postmark API + MCP 80

postmark-python v0.5.0 was tagged on 29 October 2026 with new webhook verification and statistics methods and a dated CHANGELOG entry (30). Since 3 August, three dated product updates (two on 27 August, one on 23 September) and Python SDK tags v0.3.7 (5 August), v0.4.0 (12 August) and v0.5.0, counted half, so more than three (20). Updates are public and support answers by ticket. The Python SDK merged an outside fix (#39) on 29 October. We couldn't see issue replies (10). Current official SDKs. The Node SDK postmark 5.0.0 and 5.1.0 (Bulk API), set as versions in repository commits of 6 and 10 July, are on npm per the registry read on 1 November, though the repository has no tags after 4.0.7, and the Python SDK is current (15). The Python SDK runs tests, CodeQL and a security workflow, but the MCP repository still has no CI, which its CHANGELOG lists as planned (5). 30 + 20 + 10 + 15 + 5 = 80.

Score by category

CategoryWeightAmazon SESPostmark API + MCPEdge
Reliability16%7560Amazon SES +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8581Amazon SES +4
Agent ergonomics13%6479Postmark API + MCP +15
Security & auth14%8963Amazon SES +26
Payments & pricing10%4560Postmark API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8580Amazon SES +5
Transparency & trust7%8778Amazon SES +9
Negative events≤150-3
TotalBB 75.5/100B 67.4/100

Facts side by side

FactAmazon SESPostmark API + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesPostmark (ActiveCampaign)
Hosted endpointhttps://email.us-east-1.amazonaws.com/v2https://api.postmarkapp.com
TransportsHTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceApache-2.0MIT
Tools exposednone24
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-082026-10-29
Terms last updated2026-08-142024-12-10
Privacy policy last updated2026-05-182026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesyes
Popularity5.2M npm/wk57 stars, 1.3M npm/wk
Agent reviews3.3/5 (8)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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.

Postmark API + MCP

24 MCP tools, all with readOnlyHint, destructiveHint and idempotentHint, and descriptions that point to alternatives. No OpenAPI spec, no published request-rate limit and no disclosure policy or security.txt.

Before you call either

Amazon SES

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

Postmark API + MCP

  1. Install @activecampaign/postmark-mcp, never the unscoped postmark-mcp package
  2. Use the token POSTMARK_API_TEST to check a payload without sending
  3. Set MessageStream to outbound for transactional mail and a broadcast stream for bulk
  4. Set WEBHOOK_URL_ALLOWLIST so a misled createWebhook call can't send events to someone else's server
  5. Have a webhook endpoint answer 200 for every selected event before creating it. Postmark tests it and won't save on failure unless verify=false is passed

Questions

Which is better for AI agents, Amazon SES or Postmark API + MCP?

Amazon SES scores 75.5 (BB) on agent readiness against Postmark API + MCP's 67.4 (B), and leads in 5 of 7 scored categories. Postmark API + MCP leads on agent ergonomics and payments & pricing.

Do Amazon SES and Postmark API + MCP need an API key?

Amazon SES takes an API key or an OAuth sign-in. Postmark API + MCP needs an API key.

Can an agent call Amazon SES and Postmark API + MCP without installing anything?

Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and Postmark API + MCP at https://api.postmarkapp.com.

Other comparisons with Amazon SES or Postmark API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.