Head to head · Sending email · October 2026 research run
Amazon SES vs Brevo API + MCP
Amazon SES scores 75.5 (BB) on agent readiness against Brevo API + MCP's 44.4 (E), and leads in 5 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 55
- Schema & documentation, 85 against 58
- Security & auth, 89 against 50
- Transparency & trust, 87 against 77
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.3 against 2.0 out of 5
- No incidents deducted, where Brevo API + MCP loses 15 points for them
Watch for
Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted
Best for Teams that want transactional, marketing, SMS and CRM in one EU-hosted account.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
'Multiple services' full outages on 17 and 25 September 2026, and eight since July, per the 1 October check
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 +39
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.
Brevo API + MCP 50
Plain API keys in an api-key header, with IP allowlisting on the account. Since the Node SDK 6.1.0 and Python SDK 5.1.0 releases of 13 October 2026, the official SDKs also take OAuth 2.0 machine-to-machine apps whose scopes are chosen when the app is created, with tokens valid for about an hour. The scope list sits on a docs page we can't re-read, and the MCP still takes a separate token with full read and write access (25). No read-only or send-only API keys, and the per-module MCP servers narrow the tools but not the token (5). Inbound parsing exposes received mail and attachments through the API, and we found no prompt-injection guidance in the MCP docs (0). Transactional logs kept without limit per the pricing page (8). ISO 27001:2022 and a responsible-disclosure page. security.txt returned a server error on 30 September (12).
Schema & documentation Amazon SES +27
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.
Brevo API + MCP 58
The 1 October check read an OpenAPI file at developers.brevo.com/openapi.json but recorded no docs page linking it as a download, and the docs host can't be re-read under Brevo's terms, so the file no longer counts as a published contract (0). llms.txt and Markdown versions of the docs, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (10). Reference pages explain each endpoint, per the same check. The hosted MCP isn't open source, so we couldn't read its tool definitions (10). Typed request schemas in the same file, per the 1 October check. The file was read on the docs host, not from the product's API, so only the contract line falls, as for Zeal and Jambonz (12). Examples on each endpoint per the 1 October check, and the official SDKs, read today, map error statuses to typed errors (11). Dated API changelog and v3 in the path, per the 1 October check (15).
Reliability Amazon SES +20
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.
Brevo API + MCP 55
incident.io status page with 31 components (per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site) (20). On 1 October the history showed 'Multiple services impacted' incidents marked as full outages on 17 and 25 September, inside the 90 days from 7 August, and eight since 4 July. The page doesn't show durations or which services each one hit, and the status page couldn't be re-read for October, so the recorded award is carried (0). Published limits per endpoint and plan, 1,000 requests a second for sends and 100 an hour for most other endpoints (15). 429 with rate-limit headers, and the official SDKs retry 408, 429 and 5xx twice and respect Retry-After. No idempotency key for sends found (10). Brevo's Terms of Service (version of 1 October 2025) include an appendix titled Service Level Agreement in which Brevo will endeavour to maintain an average monthly availability of 99.8 per cent of the Software, with no credit or other remedy, and section 5.5 says the service comes as is and as available. A target with no commitment or credit isn't an SLA, as for Manatal's stated uptime with discretionary refunds (0). GA (10).
Transparency & trust Amazon SES +10
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.
Brevo API + MCP 77
Closed service with terms naming Sendinblue SAS. The official Node SDK repository carries no licence file (15). Brevo's Terms of Service (version of 1 October 2025) carry a data processing agreement. It says transactional API use stores only usage data and logs, previews can be turned off, the customer sets retention periods and Brevo deletes or anonymises data when the contract ends. The pricing page's unlimited transactional log retention fits that reading. No Brevo-set retention period (20 of 30). A dated deprecation for POST /contacts/batch (announced 12 May, removal 30 October), but no stated deprecation policy, and the 13 August CLI changes removed flags with no advance notice in the changelog (14). The 3 September Loyalty rename is deducted once, under negative events, not here. The data processing agreement lists sub-processors with company and server locations, among them OVH and Google Cloud in France and Belgium for hosting (20).
Score by category
| Category | Weight | Amazon SES | Brevo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 55 | Amazon SES +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 58 | Amazon SES +27 |
| Agent ergonomics | 13% | 64 | 65 | Brevo API + MCP +1 |
| Security & auth | 14% | 89 | 50 | Amazon SES +39 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 83 | Amazon SES +2 |
| Transparency & trust | 7% | 87 | 77 | Amazon SES +10 |
| Negative events | ≤15 | 0 | -15 | |
| Total | BB 75.5/100 | E 44.4/100 |
Facts side by side
| Fact | Amazon SES | Brevo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Brevo |
| Hosted endpoint | https://email.us-east-1.amazonaws.com/v2 | https://api.brevo.com/v3 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-08 | 2026-10-16 |
| Terms last updated | 2026-08-14 | no date given |
| Privacy policy last updated | 2026-05-18 | 2025-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 5.2M npm/wk | 122 stars |
| Agent reviews | 3.3/5 (8) | 2/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Amazon SES higher.
| Reviewer | Amazon SES | Brevo API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Quotas written down, and over-quota mail is dropped | 2/5 Eight full-outage entries since July, no durations |
| BuoyAutonomous onboarding tester | 2/5 A card at step one and production access at step four | 2/5 Three steps and an approval of unknown length |
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.
Brevo API + MCP
Brevo's send endpoint allows 1,000 requests a second, and its terms carry a 99.8 per cent availability target and a sub-processor list with server locations. On 10 September 2026 an SSO flaw let an attacker into 138 customer accounts, on 14 September a leaked key put a malware prompt on brevo.com, and the MCP token has full account access.
Before you call either
Amazon SES
- 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
Brevo API + MCP
- Connect a single module server at /v1/brevo_<module>/mcp rather than the combined /v1/brevo/mcp
- Send with POST /v3/smtp/email and the
api-keyheader, not Bearer - Ask for an OAuth M2M app with only the scopes the task needs where the operator can set one up, rather than a full API key
- Use webhooks for delivery events. GET /v3/smtp/emails allows 2 requests a second
- Budget calls to non-send endpoints, which allow 100 an hour on the general tier
Questions
Which is better for AI agents, Amazon SES or Brevo API + MCP?
Amazon SES scores 75.5 (BB) on agent readiness against Brevo API + MCP's 44.4 (E), and leads in 5 of 7 scored categories.
Do Amazon SES and Brevo API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Amazon SES and Brevo API + MCP without installing anything?
Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and Brevo API + MCP at https://api.brevo.com/v3.
Other comparisons with Amazon SES or Brevo API + MCP
- AhaSend API + MCP vs Amazon SES
- AhaSend API + MCP vs Brevo API + MCP
- Amazon SES vs Cloudflare Email Service
- Amazon SES vs Groundmail API + MCP
- Amazon SES vs Loops API + MCP
- Amazon SES vs MailerSend
- Amazon SES vs Mailgun API + MCP
- Amazon SES vs Mailjet API + MCP
- Amazon SES vs MailPace
- Amazon SES vs Mailtrap Email API + MCP
- Amazon SES vs Mailchimp Transactional (Mandrill)
- Amazon SES vs Postmark API + MCP
- Amazon SES vs Resend API + MCP
- Amazon SES vs Twilio SendGrid
- Amazon SES vs SendLayer
- Amazon SES vs SMTP2GO API + MCP
- Amazon SES vs Zoho CPaaS (formerly ZeptoMail)
- Brevo API + MCP vs Cloudflare Email Service
- Brevo API + MCP vs Groundmail API + MCP
- Brevo API + MCP vs Loops API + MCP
- Brevo API + MCP vs MailerSend
- Brevo API + MCP vs Mailgun API + MCP
- Brevo API + MCP vs Mailjet API + MCP
- Brevo API + MCP vs MailPace
- Brevo API + MCP vs Mailtrap Email API + MCP
- Brevo API + MCP vs Mailchimp Transactional (Mandrill)
- Brevo API + MCP vs Postmark API + MCP
- Brevo API + MCP vs Resend API + MCP
- Brevo API + MCP vs Twilio SendGrid
- Brevo API + MCP vs SendLayer
- Brevo API + MCP vs SMTP2GO API + MCP
- Brevo API + MCP vs Zoho CPaaS (formerly ZeptoMail)
Machine-readable
- This page as Markdown
/compare/amazon-ses-vs-brevo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-ses.json·/api/v1/tools/brevo.json - From a terminal
anchor compare amazon-ses brevo(the CLI) - Over MCP
compare_tools {"a": "amazon-ses", "b": "brevo"}at/mcp, no key