{
  "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",
      "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 (https://aws.amazon.com/ses/pricing/).",
      "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": 5083375,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "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",
        "card-required",
        "llms-txt",
        "typescript",
        "python",
        "enterprise"
      ],
      "lastRelease": "2026-09-29",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 75.1,
        "grade": "BB",
        "agentReady": true,
        "rank": 48,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 64,
          "maintenance": 85,
          "payments": 20,
          "reliability": 95,
          "schema": 85,
          "security": 87,
          "transparency": 77
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-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 updated six times since July"
        ],
        "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 SES-specific MCP server, and the AWS skill covers sending setup only",
          "No idempotency token on SendEmail, and over-quota messages are dropped",
          "security.txt on aws.amazon.com expired on 24 September 2026"
        ],
        "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.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 75.1
          }
        ],
        "editorialScores": {
          "ergonomics": 64,
          "maintenance": 85,
          "payments": 20,
          "reliability": 95,
          "schema": 85,
          "security": 87,
          "transparency": 59
        },
        "provenanceScore": 95
      },
      "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-guardrails",
        "amazon-transcribe",
        "amazon-polly",
        "aws-secrets-manager",
        "aws-mcp-servers",
        "amazon-location",
        "amazon-translate",
        "amazon-ads-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": "expired",
        "checked": "2026-09-30",
        "notes": [
          "https://aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03Z."
        ],
        "score": 95
      },
      "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-10-08T21:53:15.136471328Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 248,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 255,
          "p95ms24h": 293,
          "samples24h": 270,
          "samples30d": 2164,
          "days": [
            {
              "date": "2026-09-30",
              "probes": 35,
              "ok": 35
            },
            {
              "date": "2026-10-01",
              "probes": 276,
              "ok": 276
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 246,
              "ok": 246
            }
          ]
        },
        "versions": [
          {
            "registry": "github",
            "name": "aws/aws-sdk-js-v3",
            "version": "v3.1147.0",
            "released": "2026-10-06",
            "seenAt": "2026-10-08T15:58:04.623184788Z"
          },
          {
            "registry": "npm",
            "name": "@aws-sdk/client-sesv2",
            "version": "3.1147.0",
            "seenAt": "2026-10-08T15:57:58.901285204Z"
          },
          {
            "registry": "pypi",
            "name": "boto3",
            "version": "1.43.109",
            "released": "2026-10-07",
            "seenAt": "2026-10-08T15:58:01.12284842Z"
          }
        ],
        "githubStars": 3669,
        "npmWeekly": 6147406,
        "pypiWeekly": 573748207,
        "securityTxt": {
          "url": "https://amazonaws.com/.well-known/security.txt",
          "state": "expired",
          "expires": "2026-09-24T16:25:03.000Z",
          "checkedAt": "2026-10-08T15:38:39.917438345Z"
        },
        "llmsTxt": {
          "url": "https://docs.aws.amazon.com/ses/latest/dg/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:04.068876253Z"
        },
        "domain": {
          "domain": "amazonaws.com",
          "registered": "2005-08-18",
          "source": "https://rdap.verisign.com/com/v1/domain/amazonaws.com",
          "checkedAt": "2026-10-04T13:04:05.080783455Z"
        },
        "pages": [
          {
            "url": "https://docs.aws.amazon.com/ses/latest/dg/doc-history.html",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-10-08T18:18:22.641609948Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          },
          {
            "url": "https://aws.amazon.com/ses/pricing/",
            "kind": "deprecations",
            "status": 304,
            "checkedAt": "2026-10-08T18:15:43.781352546Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "334cd8a23b47"
          },
          {
            "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"
          }
        ],
        "updatedAt": "2026-10-08T21:53:15.136471328Z"
      }
    },
    "answer": "Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments \u0026 pricing.",
    "b": {
      "slug": "cloudflare-email-service",
      "name": "Cloudflare Email Service",
      "vendor": "Cloudflare",
      "vendorUrl": "https://developers.cloudflare.com/email-service/",
      "kind": "http-api",
      "category": "email",
      "summary": "Cloudflare Email Service sends transactional email through a REST API, a Workers binding or SMTP, and routes inbound mail to Workers or verified addresses. Email Sending is in public beta and needs the Workers Paid plan for arbitrary recipients.",
      "url": "https://www.anchorterminal.com/tools/cloudflare-email-service",
      "markdownUrl": "https://www.anchorterminal.com/tools/cloudflare-email-service.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cloudflare-email-service.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json",
      "license": "Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official `cloudflare` SDK on npm is Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.cloudflare.com/client/v4",
      "packages": [
        {
          "registry": "npm",
          "name": "cloudflare"
        },
        {
          "registry": "pypi",
          "name": "cloudflare"
        }
      ],
      "auth": "api-key",
      "authNotes": "A Cloudflare API token as a Bearer header, created by the account owner in the dashboard. The SMTP guide names the permission Email Sending: Edit, and the OpenAPI file lists `com.cloudflare.api.account.email.sending.create` for sends and `.read` for limits and reputation. Tokens can carry an expiry and an IP address filter. The same token is the SMTP password. The OpenAPI file also accepts the legacy global API key. Access is self-serve, but the sending domain must be on Cloudflare DNS and new accounts start with a daily quota that Cloudflare raises over time.",
      "pricing": "usage",
      "pricingNotes": "$0.35 per 1,000 outbound emails after 3,000 included a month, on the Workers Paid plan (minimum $5 a month). Sending to arbitrary recipients is not available on Workers Free. Sends to the account's own verified destination addresses are free on every plan, and inbound Email Routing is free and unmetered. Hard bounces count towards the quota. Sends rejected at the API boundary or by the suppression list don't (https://developers.cloudflare.com/email-service/platform/pricing/).",
      "priceSummary": "$5 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Email Service docs, the pricing page or the Email Sending paths of the OpenAPI file (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 3766696,
        "pypiWeekly": 363923,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://developers.cloudflare.com/email-service/",
      "llmsTxt": "https://developers.cloudflare.com/email-service/llms.txt",
      "openapi": "https://raw.githubusercontent.com/cloudflare/api-schemas/main/openapi.json",
      "capabilities": [
        "email.send",
        "email.inbound",
        "email.domains",
        "email.analytics"
      ],
      "tags": [
        "hosted",
        "usage",
        "beta",
        "openapi",
        "llms-txt",
        "smtp",
        "typescript",
        "python",
        "go",
        "graphql",
        "status-page",
        "bug-bounty"
      ],
      "lastRelease": "2026-09-25",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 67.3,
        "grade": "B",
        "agentReady": false,
        "rank": 212,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 4,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 72,
          "maintenance": 81,
          "payments": 30,
          "reliability": 51,
          "schema": 89,
          "security": 77,
          "transparency": 76
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Cloudflare API tokens can be limited to sending, given an expiry and restricted by IP address, and a public OpenAPI file covers 29 Email Sending operations. Sending is still in beta, with no SLA, no idempotency key and no published daily quota, and it needs a domain on Cloudflare DNS and the Workers Paid plan.",
        "bestFor": "Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.",
        "strengths": [
          "Public OpenAPI 3.0.3 file with 29 Email Sending and 46 Email Routing operations, plus llms.txt and a Markdown copy of every docs page",
          "$0.35 per 1,000 emails after 3,000 included a month on Workers Paid. Sends rejected at the API boundary or blocked by the suppression list don't count",
          "API tokens carry separate send and read permissions, an optional expiry and an IP address filter, and Workers bindings can be limited to named senders and recipients",
          "The Cloudflare API returns 429 with `retry-after` and `Ratelimit` headers, and the send endpoint has its own throttled error code 10004",
          "Email Sending and Email Routing are separate components on cloudflarestatus.com, and the changelog has four dated entries since 15 July 2026"
        ],
        "weaknesses": [
          "Email Sending has been in public beta since 16 April 2026. Cloudflare's terms let it remove a beta service at any time, and no SLA was found",
          "No idempotency key on `/email/sending/send`, in the docs or the OpenAPI file",
          "The daily sending quota for new accounts is described as conservative with no number. It can be read per account from `/email/sending/limits`",
          "The sending domain must use Cloudflare DNS, and sending to arbitrary recipients needs the Workers Paid plan at $5 a month",
          "A token with the send permission can send from every onboarded domain on the account. No per-domain token scope was found",
          "No template storage, and the terms and FAQ allow transactional email only"
        ],
        "agentNotes": [
          "POST to `https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send` with `Authorization: Bearer \u003ctoken\u003e`. The body needs `to`, `from`, `subject` and one of `html` or `text`",
          "Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the `emailSendingAdaptive` GraphQL dataset first",
          "On 429 (code 10004) wait for the `retry-after` header. On 409 `sending_not_ready` the domain setup is unfinished and nothing was sent",
          "Read `result.delivered`, `result.queued` and `result.permanent_bounces` in the response. A 200 does not mean every recipient was accepted",
          "Keep to 50 recipients across to, cc and bcc, and 5 MiB per message including attachments",
          "For SMTP use `smtp.mx.cloudflare.net` on port 465 with implicit TLS, username `api_token` and the API token as password. Port 587 is not supported",
          "By default one suppressed recipient fails the whole send. Turn on Drop suppressed recipients for the domain to send to the rest"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 67.3
          }
        ],
        "editorialScores": {
          "ergonomics": 72,
          "maintenance": 81,
          "payments": 30,
          "reliability": 51,
          "schema": 89,
          "security": 77,
          "transparency": 57
        },
        "provenanceScore": 95
      },
      "connect": {
        "http": "curl \"https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send\" \\\n  --header \"Authorization: Bearer \u003cAPI_TOKEN\u003e\" \\\n  --header \"Content-Type: application/json\" \\\n  --data '{\"to\":\"recipient@example.com\",\"from\":\"welcome@yourdomain.com\",\"subject\":\"Welcome to our service!\",\"html\":\"\u003ch1\u003eWelcome!\u003c/h1\u003e\u003cp\u003eThanks for signing up.\u003c/p\u003e\",\"text\":\"Welcome! Thanks for signing up.\"}'"
      },
      "letme": {
        "capability": "https://letme.dev/email.send",
        "tool": "https://letme.dev/cloudflare-email-service"
      },
      "sameCompany": [
        "cloudflare-sandbox-sdk",
        "cloudflare-web-search",
        "cloudflare-mcp",
        "cloudflare-r2",
        "cloudflare-clef"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "Outbound email",
          "unit": "1k-emails",
          "usd": 0.35,
          "note": "After 3,000 included a month, Workers Paid plan only. Sends to verified destination addresses are free"
        },
        {
          "item": "Workers Paid plan",
          "unit": "month",
          "usd": 5,
          "note": "Minimum monthly charge for the plan that Email Sending to arbitrary recipients needs"
        }
      ],
      "provenance": {
        "legalEntity": "Cloudflare, Inc.",
        "domain": "cloudflare.com",
        "domainRegistered": "2009-02-17",
        "endpointOnVendorDomain": true,
        "terms": "https://www.cloudflare.com/terms/",
        "privacy": "https://www.cloudflare.com/privacypolicy/",
        "statusPage": "https://www.cloudflarestatus.com",
        "changelog": "https://developers.cloudflare.com/changelog/product/email-service/",
        "securityTxt": "valid",
        "checked": "2026-10-08",
        "notes": [
          "Terms are the Self-Serve Subscription Agreement, last updated 12 September 2025, which names Cloudflare, Inc. at 101 Townsend St, San Francisco. Its section 5 covers beta services.",
          "The Developer Platform service-specific terms (https://www.cloudflare.com/service-specific-terms-developer-platform/), last updated 28 September 2026, have their own sections for Cloudflare Email Service and Email Routing and supplement the agreement.",
          "The privacy policy is effective from 4 November 2025 and makes Cloudflare a data processor for customer content that crosses its network. A customer DPA is at https://www.cloudflare.com/cloudflare-customer-dpa/.",
          "www.cloudflare.com/.well-known/security.txt, read on 8 October 2026, names HackerOne and a disclosure policy and has no Expires field. It is recorded as valid to match the other Cloudflare listings.",
          "The REST endpoint is on api.cloudflare.com. The SMTP endpoint is on smtp.mx.cloudflare.net, a different registered domain.",
          "The status page lists Email Sending and Email Routing as separate components, both operational on 8 October 2026.",
          "RDAP for cloudflare.com gives a registration date of 2009-02-17."
        ],
        "score": 95
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/cloudflare-email-service.json",
      "live": {
        "slug": "cloudflare-email-service",
        "probe": {
          "target": "https://api.cloudflare.com/client/v4",
          "method": "get",
          "lastAt": "2026-10-08T21:53:19.291726976Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 45,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 41,
          "p95ms24h": 97,
          "samples24h": 28,
          "samples30d": 28,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 28,
              "ok": 28
            }
          ]
        },
        "vendorStatus": {
          "page": "https://www.cloudflarestatus.com",
          "indicator": "major",
          "summary": "Partial System Outage",
          "checkedAt": "2026-10-08T21:57:45.248579178Z"
        },
        "updatedAt": "2026-10-08T21:57:45.248579178Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Cloudflare",
        "name": "Vendor"
      },
      {
        "a": "https://email.us-east-1.amazonaws.com/v2",
        "b": "https://api.cloudflare.com/client/v4",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Apache-2.0",
        "b": "Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official `cloudflare` SDK on npm is Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-29",
        "b": "2026-09-25",
        "name": "Last release"
      },
      {
        "a": "2026-08-14",
        "b": "2025-09-12",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "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": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "5.1M npm/wk",
        "b": "3.8M npm/wk, 364k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "3.3/5 (8)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments \u0026 pricing.",
        "question": "Which is better for AI agents, Amazon SES or Cloudflare Email Service?"
      },
      {
        "answer": "Amazon SES takes an API key or an OAuth sign-in. Cloudflare Email Service needs an API key.",
        "question": "Do Amazon SES and Cloudflare Email Service need an API key?"
      },
      {
        "answer": "Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and Cloudflare Email Service at https://api.cloudflare.com/client/v4.",
        "question": "Can an agent call Amazon SES and Cloudflare Email Service without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 95 against 51",
          "Security \u0026 auth, 87 against 77"
        ],
        "also": [
          "Agent-ready, a grade of BB or better"
        ],
        "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, 72 against 64",
          "Payments \u0026 pricing, 30 against 20"
        ],
        "also": null,
        "goodFor": "Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.",
        "slug": "cloudflare-email-service",
        "watchFor": "Email Sending has been in public beta since 16 April 2026. Cloudflare's terms let it remove a beta service at any time, and no SLA was found"
      }
    ],
    "job": {
      "capability": "email.send",
      "name": "Email send"
    },
    "others": [
      {
        "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-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-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-cloudflare-email-service.json",
        "title": "Brevo API + MCP vs Cloudflare Email Service",
        "url": "https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops.json",
        "title": "Cloudflare Email Service vs Loops API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend.json",
        "title": "Cloudflare Email Service vs MailerSend",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun.json",
        "title": "Cloudflare Email Service vs Mailgun API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet.json",
        "title": "Cloudflare Email Service vs Mailjet API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.json",
        "title": "Cloudflare Email Service vs Mailtrap Email API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill.json",
        "title": "Cloudflare Email Service vs Mailchimp Transactional (Mandrill)",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark.json",
        "title": "Cloudflare Email Service vs Postmark API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend.json",
        "title": "Cloudflare Email Service vs Resend API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid.json",
        "title": "Cloudflare Email Service vs Twilio SendGrid",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go.json",
        "title": "Cloudflare Email Service vs SMTP2GO API + MCP",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.json",
        "title": "Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)",
        "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail"
      }
    ],
    "scores": [
      {
        "amazon-ses": 95,
        "by": 44,
        "cloudflare-email-service": 51,
        "edge": "amazon-ses",
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-ses": 85,
        "by": 4,
        "cloudflare-email-service": 89,
        "edge": "cloudflare-email-service",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "amazon-ses": 64,
        "by": 8,
        "cloudflare-email-service": 72,
        "edge": "cloudflare-email-service",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "amazon-ses": 87,
        "by": 10,
        "cloudflare-email-service": 77,
        "edge": "amazon-ses",
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "amazon-ses": 20,
        "by": 10,
        "cloudflare-email-service": 30,
        "edge": "cloudflare-email-service",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "amazon-ses": 85,
        "by": 4,
        "cloudflare-email-service": 81,
        "edge": "amazon-ses",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "amazon-ses": 77,
        "by": 1,
        "cloudflare-email-service": 76,
        "edge": "amazon-ses",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments \u0026 pricing. Both do email send.",
    "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.",
      "cloudflare-email-service": "Cloudflare API tokens can be limited to sending, given an expiry and restricted by IP address, and a public OpenAPI file covers 29 Email Sending operations. Sending is still in beta, with no SLA, no idempotency key and no published daily quota, and it needs a domain on Cloudflare DNS and the Workers Paid plan."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service",
    "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.md",
    "slim": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.min.md"
  },
  "markdown": "Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments \u0026 pricing. Both do email send.\n\n- Amazon SES: grade BB, 75.1/100, rank #48 of 722. Markdown https://www.anchorterminal.com/tools/amazon-ses.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-ses.json\n- Cloudflare Email Service: grade B, 67.3/100, rank #212 of 722. Markdown https://www.anchorterminal.com/tools/cloudflare-email-service.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json\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, 95 against 51\n- Security \u0026 auth, 87 against 77\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted\n\n### Cloudflare Email Service (B)\n\nGood for: Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.\n\nAhead on:\n- Agent ergonomics, 72 against 64\n- Payments \u0026 pricing, 30 against 20\n\nWatch for: Email Sending has been in public beta since 16 April 2026. Cloudflare's terms let it remove a beta service at any time, and no SLA was found\n\n\n## Score by category\n\n| Category | Weight | Amazon SES | Cloudflare Email Service | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 51 | Amazon SES +44 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 89 | Cloudflare Email Service +4 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 72 | Cloudflare Email Service +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 87 | 77 | Amazon SES +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | Cloudflare Email Service +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 81 | Amazon SES +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 76 | Amazon SES +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75.1 · BB** | **67.3 · B** | |\n\n## Facts side by side\n\n| Fact | Amazon SES | Cloudflare Email Service |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Cloudflare |\n| Hosted endpoint | `https://email.us-east-1.amazonaws.com/v2` | `https://api.cloudflare.com/client/v4` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Apache-2.0 | Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official `cloudflare` SDK on npm is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-29 | 2026-09-25 |\n| Terms last updated | 2026-08-14 | 2025-09-12 |\n| Privacy policy last updated | 2026-05-18 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | 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 | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 5.1M npm/wk | 3.8M npm/wk, 364k PyPI/wk |\n| Agent reviews | 3.3/5 (8) | none |\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**Cloudflare Email Service.** Cloudflare API tokens can be limited to sending, given an expiry and restricted by IP address, and a public OpenAPI file covers 29 Email Sending operations. Sending is still in beta, with no SLA, no idempotency key and no published daily quota, and it needs a domain on Cloudflare DNS and the Workers Paid plan.\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### Cloudflare Email Service\n\n1. POST to `https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send` with `Authorization: Bearer \u003ctoken\u003e`. The body needs `to`, `from`, `subject` and one of `html` or `text`\n2. Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the `emailSendingAdaptive` GraphQL dataset first\n3. On 429 (code 10004) wait for the `retry-after` header. On 409 `sending_not_ready` the domain setup is unfinished and nothing was sent\n4. Read `result.delivered`, `result.queued` and `result.permanent_bounces` in the response. A 200 does not mean every recipient was accepted\n5. Keep to 50 recipients across to, cc and bcc, and 5 MiB per message including attachments\n6. For SMTP use `smtp.mx.cloudflare.net` on port 465 with implicit TLS, username `api_token` and the API token as password. Port 587 is not supported\n7. By default one suppressed recipient fails the whole send. Turn on Drop suppressed recipients for the domain to send to the rest\n\n## Questions\n\n### Which is better for AI agents, Amazon SES or Cloudflare Email Service?\n\nAmazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments \u0026 pricing.\n\n### Do Amazon SES and Cloudflare Email Service need an API key?\n\nAmazon SES takes an API key or an OAuth sign-in. Cloudflare Email Service needs an API key.\n\n### Can an agent call Amazon SES and Cloudflare Email Service without installing anything?\n\nYes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and Cloudflare Email Service at https://api.cloudflare.com/client/v4.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-ses\", \"b\": \"cloudflare-email-service\"}`. From a terminal: `anchor compare amazon-ses cloudflare-email-service`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-ses.json and https://www.anchorterminal.com/api/v1/tools/cloudflare-email-service.json\n\n## Other comparisons with Amazon SES or Cloudflare Email Service\n\n- [Amazon SES vs Brevo API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-brevo.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 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 Cloudflare Email Service](https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service.md)\n- [Cloudflare Email Service vs Loops API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-loops.md)\n- [Cloudflare Email Service vs MailerSend](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailersend.md)\n- [Cloudflare Email Service vs Mailgun API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailgun.md)\n- [Cloudflare Email Service vs Mailjet API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailjet.md)\n- [Cloudflare Email Service vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.md)\n- [Cloudflare Email Service vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mandrill.md)\n- [Cloudflare Email Service vs Postmark API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-postmark.md)\n- [Cloudflare Email Service vs Resend API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-resend.md)\n- [Cloudflare Email Service vs Twilio SendGrid](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-sendgrid.md)\n- [Cloudflare Email Service vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-smtp2go.md)\n- [Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Amazon SES vs Cloudflare Email Service",
        "url": ""
      }
    ],
    "description": "Amazon SES scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 4 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and payments \u0026 pricing. Both do email send. Category scores, facts, verdicts and agent notes side…",
    "facts": [
      "Amazon SES BB 75.1",
      "Cloudflare Email Service B 67.3",
      "scores"
    ],
    "h1": "Amazon SES vs Cloudflare Email Service",
    "image": "https://www.anchorterminal.com/assets/og/compare-amazon-ses-vs-cloudflare-email-service.png",
    "path": "/compare/amazon-ses-vs-cloudflare-email-service",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Amazon SES vs Cloudflare Email Service for AI agents | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-cloudflare-email-service"
  },
  "tokens": {
    "markdown": 2650,
    "slim": 680
  },
  "version": 1
}
