Head to head · Sending email · October 2026 research run

Amazon SES vs Mailjet API + MCP

Amazon SES scores 75.5 (BB) on agent readiness against Mailjet API + MCP's 61.5 (C), and leads in 6 of 7 scored categories. 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 62
  • Schema & documentation, 85 against 76
  • Agent ergonomics, 64 against 53
  • Security & auth, 89 against 52
  • Maintenance & community, 85 against 79
  • Transparency & trust, 87 against 74

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.3 against 2.5 out of 5

Watch for

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

Mailjet API + MCP C

Best for EU-based senders who want cheap transactional and marketing mail with data kept in the EU.

Also in its favour

  • Runs on your own machine

Watch for

The MCP server registers 117 GET-only tools and can't send

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 +37

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.

Mailjet API + MCP 52

Email API calls use Basic auth with a public key and a secret. Sub-accounts get their own keys, and the Content API also takes Bearer tokens with permissions and a 365-day default expiry (22). The MCP server can only read, by construction. We found no send-only or read-only key for the Email API (10). The MCP returns contacts, lists and statistics, and inbound mail goes from the Parse API to your webhook rather than through the tools (10). No audit log or per-key activity view found (0). Sinch's trust portal for Mailjet lists ISO 27001:2022 and SOC 2 Type II, a 'Report a Vulnerability' route to security@sinch.com and public vulnerability notices. No bug bounty, and www.mailjet.com/.well-known/security.txt answered 404 on 4 November. Level with the Sinch messaging and voice listings on the same portal (10). 22 + 10 + 10 + 0 + 10 = 52.

Reliability Amazon SES +13

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.

Mailjet API + MCP 62

Statuspage at mailjet.statuspage.io with history back to 2023, read through its history.atom feed (20). In the 90 days from 6 August the feed has two entries. A planned hour of infrastructure maintenance on 23 September, during which logins and API and SMTP sends were unavailable and submitted mail waited in the queue, and a Microsoft incident on 4 September that deferred mail to M365 only, with other providers unaffected. Both read as minor (20). The rate-limit page, unchanged on 4 November, says transactional endpoints have a high limit and others a 'much lower' one, with no numbers (0). A 429 on excess and advice to wait and retry, but no Retry-After header and no idempotency key for sends. SandboxMode validates a send without delivering (7). Enterprise plans list a 'Service Level Agreement' with no published terms, per the 1 October check, not re-read on 4 November (5). GA (10). 20 + 20 + 0 + 7 + 5 + 10 = 62.

Transparency & trust Amazon SES +13

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.

Mailjet API + MCP 74

Closed service with published terms that name Mailjet SAS, Mailjet GmbH or Mailgun Technologies, Inc. depending on the customer, and an Apache-2.0 MCP server (20). Data stored on Google Cloud in Frankfurt and Saint-Ghislain, a Sinch DPA and a named DPO, but no retention periods stated, per the 1 October check, not re-read on 4 November (18). A Deprecated Endpoints page lists the newsletter and legacy statistics endpoints, saying they could be removed in the future and to migrate to the current endpoints without naming them, and the Python SDK warns at run time with the replacement, but no dates or policy (8 of 20, 5 on 1 October). Data locations are stated. We found no subprocessor list (12). 20 + 18 + 8 + 12 = 58.

Agent ergonomics Amazon SES +11

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

Mailjet API + MCP 53

The released MCP server registers one tool for each of the 117 GET paths in its bundled spec, with no toolsets (5). Limit, Offset, Sort and countOnly on list resources, with a maximum of 1,000 results a page (15). Documented status codes and error codes with messages (14). Every MCP tool is a GET, so nothing it does can change the account. The repository's 1.2.0 (29 October 2026, no tag) adds readOnlyHint and destructiveHint annotations, but npm couldn't be read, so its release is unconfirmed and not credited. The Send API has no idempotency key (6). Official SDKs for Node, Python and other languages, one POST /v3.1/send call carries a Messages array, and the MCP needs the key and secret joined as key:secret (13). 5 + 15 + 14 + 6 + 13 = 53.

Schema & documentation Amazon SES +9

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.

Mailjet API + MCP 76

Published OpenAPI files, and the MCP server bundles a 528 KB copy (25). llms.txt with about 120 links and Markdown pages (10). MCP tool descriptions are the operation summary only, and the reference describes each resource without saying when not to use it (8). Typed from OpenAPI, with Limit, Offset, Sort and countOnly parameters across GET resources (11). Status-code and error-code pages, and examples per endpoint (12). Send API v3 and v3.1 are versioned, and the releases page has dated entries, but they're product launches rather than an API changelog (10). Re-read on 4 November, llms.txt lists the API reference, guides and a Deprecated Endpoints page; release entries on the releases page stop at 3 September.

Maintenance & community Amazon SES +6

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.

Mailjet API + MCP 79

node-mailjet v7.1.1 on 26 October 2026, a code fix enforcing HTTPS-only requests, 9 days before the check (30). In the 90 days from 6 August, the releases page's 3 September entry and five SDK tags at half each (node-mailjet v7.1.0 on 14 August and v7.1.1, mailjet-apiv3-python 1.8.0 on 17 August, 1.9.0 on 14 September and 1.9.1 on 8 October), 3.5 in all (20). The MCP repository merges pull requests, and its README asks users to file an issue if npm and GitHub diverge. We couldn't see issue reply times (8). Node and Python SDKs released in the last 10 and 27 days (15). CI runs the tests, but the MCP repository's package.json says 1.2.0 while its git tags stop at v1.1.0-beta.1, and npm couldn't be read (6). 30 + 20 + 8 + 15 + 6 = 79.

Score by category

CategoryWeightAmazon SESMailjet API + MCPEdge
Reliability16%7562Amazon SES +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8576Amazon SES +9
Agent ergonomics13%6453Amazon SES +11
Security & auth14%8952Amazon SES +37
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8579Amazon SES +6
Transparency & trust7%8774Amazon SES +13
Negative events≤1500
TotalBB 75.5/100C 61.5/100

Facts side by side

FactAmazon SESMailjet API + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesMailjet (Sinch)
Hosted endpointhttps://email.us-east-1.amazonaws.com/v2https://api.mailjet.com/v3.1
TransportsHTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceApache-2.0MIT
Tools exposednone117
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-082026-10-26
Terms last updated2026-08-14no date given
Privacy policy last updated2026-05-182026-09-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
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/wk255 stars, 177k npm/wk, 245k PyPI/wk
Agent reviews3.3/5 (8)2.5/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.

Mailjet API + MCP

SandboxMode on Send API v3.1 validates a payload without delivering it, and data is stored in the EU. The released MCP server registers 117 GET-only tools and can't send. Rate limits are published without numbers, and the 429 guidance is to wait and retry, with no Retry-After header or idempotency key.

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

Mailjet API + MCP

  1. Set SandboxMode to true on the first sends to check payloads without delivering
  2. Send with POST /v3.1/send and a Messages array, many messages per call
  3. Use the MCP for statistics and contact lookups only, since it can't send
  4. Pass MAILJET_API_KEY as key:secret. The server checks it at startup and exits if it's wrong
  5. On 429, wait and retry. Non-transactional endpoints have much lower limits than send
  6. Move legacy calls off /v3/REST/newsletter and the old statistics resources to campaigndraft and statcounters. They are deprecated and may be removed

Questions

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

Amazon SES scores 75.5 (BB) on agent readiness against Mailjet API + MCP's 61.5 (C), and leads in 6 of 7 scored categories.

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

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

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

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

Other comparisons with Amazon SES or Mailjet 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.