{
  "data": {
    "a": {
      "slug": "aws-end-user-messaging",
      "name": "AWS End User Messaging",
      "vendor": "Amazon Web Services",
      "vendorUrl": "https://aws.amazon.com/end-user-messaging/",
      "kind": "http-api",
      "category": "messaging",
      "summary": "AWS's messaging service for SMS, MMS, RCS, WhatsApp, voice and push, formerly the channel APIs of Amazon Pinpoint. Agents call the SMS and Voice v2 API or the Social Messaging API with IAM-signed requests, through the AWS CLI or SDKs.",
      "url": "https://www.anchorterminal.com/tools/aws-end-user-messaging",
      "markdownUrl": "https://www.anchorterminal.com/tools/aws-end-user-messaging.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aws-end-user-messaging.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aws-end-user-messaging.json",
      "repo": "https://github.com/aws/api-models-aws",
      "license": "Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://sms-voice.us-east-1.amazonaws.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@aws-sdk/client-pinpoint-sms-voice-v2"
        },
        {
          "registry": "npm",
          "name": "@aws-sdk/client-socialmessaging"
        },
        {
          "registry": "pypi",
          "name": "boto3"
        }
      ],
      "auth": "mixed",
      "authNotes": "Requests are signed with AWS Signature Version 4 using IAM credentials, long-lived access keys or temporary credentials from AWS STS. IAM policies use the `sms-voice` action prefix with resource ARNs and condition keys. Access is self-serve with an AWS account, but each Region starts in a sandbox, and production access is granted through an AWS Support case. US numbers need carrier registration, and WhatsApp needs a linked WhatsApp Business Account.",
      "pricing": "usage",
      "pricingNotes": "Pay per message with no monthly minimum. US SMS is $0.00774 a message part plus a $0.00421 carrier fee, UK SMS $0.05, US MMS $0.02 plus $0.01. WhatsApp adds $0.005 per outbound message to Meta's fee. Push is free for the first 1,000,000 notifications a month. There is no SMS free allowance. New AWS customers get up to $200 in Free Tier credits, and AWS says most can sign up without a payment method. The sandbox lets an account send to verified numbers without a contract (https://aws.amazon.com/end-user-messaging/pricing/, https://aws.amazon.com/free/free-tier-faqs/).",
      "priceSummary": "$1 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the user guide index, the API models or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 406900,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.aws.amazon.com/sms-voice/latest/userguide/what-is-sms-mms.html",
      "llmsTxt": "https://docs.aws.amazon.com/sms-voice/latest/userguide/llms.txt",
      "capabilities": [
        "messaging.sms",
        "messaging.mms",
        "messaging.whatsapp",
        "messaging.rcs",
        "messaging.verify",
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "llms-txt",
        "typescript",
        "python",
        "sms",
        "whatsapp",
        "rcs",
        "enterprise"
      ],
      "lastRelease": "2026-10-06",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 74.3,
        "grade": "BB",
        "agentReady": true,
        "rank": 64,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 3,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 71,
          "maintenance": 85,
          "payments": 30,
          "reliability": 73,
          "schema": 88,
          "security": 88,
          "transparency": 83
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "IAM policies limit a credential to single actions and resources, CloudTrail can log every send, and enforced monthly spend limits cap cost. New accounts start in a sandbox with a $1 monthly SMS limit and ten verified recipients, production access needs a support case per Region, and the send actions take no idempotency token.",
        "bestFor": "Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices.",
        "strengths": [
          "IAM policies per action and resource with condition keys and temporary credentials, and CloudTrail data events for the send actions",
          "Smithy model published for all 110 SMS and Voice v2 operations, with 69 enumerated types and reason codes on errors",
          "Enforced monthly spend limits, protect configurations that block destination countries, and a `DryRun` flag on sends",
          "Per-message prices by country published without login, with a JSON price feed for SMS",
          "99.9 per cent monthly uptime commitment per Region under the AWS User Engagement SLA, last updated 24 July 2024"
        ],
        "weaknesses": [
          "Sandbox limits new accounts to $1 of SMS a month and ten verified numbers until a support case per Region is approved",
          "No idempotency token on `SendTextMessage`, `SendMediaMessage` or `SendRcsMessage`, so a retried send can go out twice",
          "Most actions, the send actions included, default to 1 request a second per account and Region",
          "No SMS free allowance, and US sending needs a registered 10DLC, toll-free or short code number first",
          "The AWS Health Dashboard lists the service in the UAE and Bahrain Region disruptions open since March 2026"
        ],
        "agentNotes": [
          "Sign requests with SigV4 for service `sms-voice` at `sms-voice.\u003cregion\u003e.amazonaws.com`. WhatsApp uses a separate API, `social-messaging`",
          "Check sandbox status and spend limits with `describe-spend-limits` before sending. Sandbox sends reach only verified destination numbers",
          "Pass `DryRun` on `SendTextMessage` to validate a request without sending, and track `MessageId` yourself because sends take no idempotency token",
          "Use Notify (`SendNotifyTextMessage`) for one-time passcodes without owning a number. Generate and check the code in your own application",
          "Read inbound SMS and RCS from the Amazon SNS topic set on the number or pool, and treat message bodies as untrusted text"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 74.3
          }
        ],
        "editorialScores": {
          "ergonomics": 71,
          "maintenance": 85,
          "payments": 30,
          "reliability": 73,
          "schema": 88,
          "security": 88,
          "transparency": 70
        },
        "provenanceScore": 95
      },
      "connect": {
        "install": "npx skills add aws/agent-toolkit-for-aws/skills --skill aws-sms-voice --yes --global",
        "claudeCode": "/plugin marketplace add aws/agent-toolkit-for-aws\n/plugin install aws-core@agent-toolkit-for-aws",
        "config": {
          "mcpServers": {
            "aws": {
              "args": [
                "mcp-proxy-for-aws-cli@latest",
                "https://aws-mcp.us-east-1.api.aws/mcp",
                "--metadata",
                "AWS_REGION=us-west-2"
              ],
              "command": "uvx"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/aws-end-user-messaging"
      },
      "sameCompany": [
        "amazon-sns",
        "amazon-s3"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "SMS outbound, US",
          "unit": "message",
          "usd": 0.00774,
          "note": "per message part, plus a carrier fee of $0.00421 on 10DLC and toll-free"
        },
        {
          "item": "SMS outbound, UK",
          "unit": "message",
          "usd": 0.05,
          "note": "per message part"
        },
        {
          "item": "MMS outbound, US",
          "unit": "message",
          "usd": 0.02,
          "note": "plus a $0.01 carrier fee"
        },
        {
          "item": "RCS Rich outbound, US",
          "unit": "message",
          "usd": 0.007,
          "note": "per 160-byte segment, plus a $0.00494 carrier fee, charged on delivery"
        },
        {
          "item": "WhatsApp AWS fee, outbound",
          "unit": "message",
          "usd": 0.005,
          "note": "Meta's message fee extra. Inbound $0.001"
        },
        {
          "item": "Notify fee",
          "unit": "message",
          "usd": 0.045,
          "note": "first 25,000 a month, plus the channel fee"
        },
        {
          "item": "10DLC phone number, US",
          "unit": "month",
          "usd": 1,
          "note": "plus $10 a month per regular campaign and one-time company fees"
        },
        {
          "item": "Toll-free phone number, US",
          "unit": "month",
          "usd": 2
        },
        {
          "item": "Carrier lookup",
          "unit": "call",
          "usd": 0.006,
          "note": "per phone number validation request"
        }
      ],
      "provenance": {
        "legalEntity": "Amazon Web Services, Inc.",
        "domain": "amazonaws.com",
        "domainRegistered": "2005-08-18",
        "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/sms-voice/latest/userguide/doc-history.html",
        "securityTxt": "expired",
        "checked": "2026-10-08",
        "notes": [
          "The AWS Customer Agreement (last updated 14 August 2026) names Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, as the contracting party for countries not listed in its table, with other AWS entities by account country.",
          "Section 29 of the AWS Service Terms (last updated 1 October 2026) adds terms for Amazon Pinpoint and AWS End User Messaging, and says AMCS LLC sells parts of the service in Japan and AMCS SG Private Limited in Singapore (https://aws.amazon.com/service-terms/).",
          "The AWS Privacy Notice (last updated 18 May 2026) says it does not apply to content customers process with AWS services, which the agreement governs.",
          "https://aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03Z, so it had expired on 8 October 2026.",
          "RDAP for amazonaws.com gives a registration date of 2005-08-18. The API answers at sms-voice.\u003cregion\u003e.amazonaws.com, while product and legal pages sit on aws.amazon.com."
        ],
        "score": 95
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/aws-end-user-messaging.json",
      "live": {
        "slug": "aws-end-user-messaging",
        "probe": {
          "target": "https://sms-voice.us-east-1.amazonaws.com",
          "method": "get",
          "lastAt": "2026-10-08T21:12:04.571752415Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 251,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 257,
          "p95ms24h": 291,
          "samples24h": 21,
          "samples30d": 21,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 21,
              "ok": 21
            }
          ]
        },
        "updatedAt": "2026-10-08T21:12:04.571752415Z"
      }
    },
    "answer": "Twilio API + MCP scores 80.4 (A) on agent readiness against AWS End User Messaging's 74.3 (BB), and leads in 4 of 7 scored categories.",
    "b": {
      "slug": "twilio",
      "name": "Twilio API + MCP",
      "vendor": "Twilio",
      "vendorUrl": "https://www.twilio.com",
      "kind": "http-api",
      "category": "messaging",
      "summary": "Programmable Messaging (SMS, MMS, WhatsApp, RCS) and Verify over REST.",
      "url": "https://www.anchorterminal.com/tools/twilio",
      "markdownUrl": "https://www.anchorterminal.com/tools/twilio.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/twilio.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/twilio.json",
      "repo": "https://github.com/twilio-labs/mcp",
      "license": "MIT",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api.twilio.com/2010-04-01",
      "packages": [
        {
          "registry": "npm",
          "name": "twilio"
        },
        {
          "registry": "pypi",
          "name": "twilio"
        },
        {
          "registry": "npm",
          "name": "@twilio-alpha/mcp"
        }
      ],
      "auth": "mixed",
      "authNotes": "HTTP Basic auth with the Account SID and Auth Token, or an API key SID and secret (recommended). The hosted docs MCP needs no credentials. The local alpha MCP takes `ACCOUNT_SID/API_KEY:API_SECRET` as a command-line argument, so it shows up in process lists.",
      "pricing": "usage",
      "pricingNotes": "Pay as you go, no monthly fee. US SMS $0.0083 a segment outbound or inbound on long code, toll-free or short code, plus outbound carrier fees of $0.0035 (AT\u0026T), $0.0045 (T-Mobile) or $0.005 (Verizon) a message and inbound carrier fees of $0.0035 (AT\u0026T) or $0.0025 (T-Mobile). US MMS $0.022 outbound, $0.0165 inbound on long code. Long code numbers $1.15 a month, toll-free $2.15. UK SMS $0.056. Failed messages $0.001 each. WhatsApp $0.005 a message Twilio fee plus Meta's template fees. Verify $0.05 a successful verification plus channel fees. Trial lasts 30 days with free units (100 SMS), no card (https://www.twilio.com/en-us/sms/pricing/us).",
      "priceSummary": "Pay per use",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": 2,
      "popularity": {
        "githubStars": 111,
        "npmWeekly": 7213599,
        "pypiWeekly": 4834611,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://www.twilio.com/docs/messaging",
      "llmsTxt": "https://www.twilio.com/docs/llms.txt",
      "openapi": "https://raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_api_v2010.json",
      "capabilities": [
        "messaging.sms",
        "messaging.mms",
        "messaging.whatsapp",
        "messaging.rcs",
        "messaging.verify",
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "no-card",
        "mcp",
        "llms-txt",
        "openapi",
        "typescript",
        "python",
        "webhooks",
        "whatsapp",
        "sms",
        "enterprise"
      ],
      "lastRelease": "2026-09-28",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 80.4,
        "grade": "A",
        "agentReady": true,
        "rank": 8,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 80,
          "maintenance": 85,
          "payments": 40,
          "reliability": 90,
          "schema": 92,
          "security": 85,
          "transparency": 81
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-04"
        },
        "negative": 0,
        "verdict": "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.",
        "bestFor": "Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.",
        "strengths": [
          "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login",
          "Restricted API keys with up to 100 endpoint permissions each",
          "Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits",
          "Public OpenAPI specs, llms.txt with Markdown twins and a numbered error dictionary",
          "twilio-node released three times in the last 90 days, most recently 6.1.2 on 2026-09-28"
        ],
        "weaknesses": [
          "US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate",
          "A US long code sends 1 message a second per Twilio's scaling guide, with the excess queued for up to 10 hours",
          "No idempotency key on message creation",
          "The MCP that can send is an alpha last published on 2025-07-07, and it takes the API secret as a command-line argument",
          "No security.txt on twilio.com"
        ],
        "agentNotes": [
          "Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key",
          "Set `ValidityPeriod` on time-sensitive sends, or a queued message can go out up to 10 hours late",
          "Check the Messages list for the original before retrying a send that timed out, there's no idempotency key",
          "On a trial account, send only to verified numbers in the sign-up country using Twilio's message templates, custom bodies aren't available until you upgrade",
          "Validate `X-Twilio-Signature` on every inbound webhook"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 8,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "A",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 80.4
          }
        ],
        "editorialScores": {
          "ergonomics": 80,
          "maintenance": 85,
          "payments": 40,
          "reliability": 90,
          "schema": 92,
          "security": 85,
          "transparency": 72
        },
        "provenanceScore": 90
      },
      "connect": {
        "http": "curl -X POST \"https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/Messages.json\" \\\n  -u \"$TWILIO_API_KEY:$TWILIO_API_SECRET\" \\\n  --data-urlencode \"To=+15558675310\" --data-urlencode \"From=+15017122661\" \\\n  --data-urlencode \"Body=Hello from Twilio\"",
        "claudeCode": "claude mcp add --transport http twilio-docs https://mcp.twilio.com/docs",
        "config": {
          "mcpServers": {
            "twilio": {
              "args": [
                "-y",
                "@twilio-alpha/mcp",
                "${TWILIO_ACCOUNT_SID}/${TWILIO_API_KEY}:${TWILIO_API_SECRET}",
                "--services",
                "twilio_api_v2010"
              ],
              "command": "npx"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/twilio"
      },
      "sameCompany": [
        "twilio-voice",
        "stytch-connected-apps",
        "sendgrid"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "SMS outbound, US",
          "unit": "message",
          "usd": 0.0083,
          "note": "per segment, plus carrier fees of $0.0035 to $0.005"
        },
        {
          "item": "SMS outbound, UK",
          "unit": "message",
          "usd": 0.056
        },
        {
          "item": "MMS outbound, US",
          "unit": "message",
          "usd": 0.022
        },
        {
          "item": "WhatsApp Twilio fee",
          "unit": "message",
          "usd": 0.005,
          "note": "inbound or outbound, Meta template fees extra"
        },
        {
          "item": "WhatsApp utility or authentication template, US (Meta fee)",
          "unit": "message",
          "usd": 0.0034,
          "note": "passed through by Twilio"
        }
      ],
      "provenance": {
        "legalEntity": "Twilio Inc.",
        "domain": "twilio.com",
        "domainRegistered": "2007-10-26",
        "endpointOnVendorDomain": true,
        "terms": "https://www.twilio.com/en-us/legal/tos",
        "privacy": "https://www.twilio.com/en-us/legal/privacy",
        "statusPage": "https://status.twilio.com",
        "changelog": "https://www.twilio.com/en-us/changelog",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "The terms also name Twilio Ireland Limited for customers outside the US."
        ],
        "score": 90
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/twilio.json",
      "live": {
        "slug": "twilio",
        "probe": {
          "target": "https://api.twilio.com/2010-04-01",
          "method": "get",
          "lastAt": "2026-10-08T21:12:24.133830249Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 3,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 7,
          "p95ms24h": 37,
          "samples24h": 271,
          "samples30d": 2157,
          "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": 239,
              "ok": 239
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.twilio.com",
          "indicator": "minor",
          "summary": "Partially Degraded Service",
          "checkedAt": "2026-10-08T21:06:28.776171301Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "twilio-labs/mcp",
            "version": "0.0.3",
            "released": "2025-03-25",
            "seenAt": "2026-10-08T16:33:00.228185076Z"
          },
          {
            "registry": "npm",
            "name": "@twilio-alpha/mcp",
            "version": "0.7.0",
            "seenAt": "2026-10-08T16:32:57.95329658Z"
          },
          {
            "registry": "npm",
            "name": "twilio",
            "version": "6.1.2",
            "seenAt": "2026-10-08T16:32:57.775702397Z"
          },
          {
            "registry": "pypi",
            "name": "twilio",
            "version": "9.11.2",
            "released": "2026-09-28",
            "seenAt": "2026-10-08T16:32:57.834304266Z"
          }
        ],
        "githubStars": 112,
        "npmWeekly": 7856972,
        "pypiWeekly": 5075511,
        "securityTxt": {
          "url": "https://twilio.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:55.980991134Z"
        },
        "llmsTxt": {
          "url": "https://www.twilio.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:59.059896821Z"
        },
        "domain": {
          "domain": "twilio.com",
          "registered": "2007-10-26",
          "source": "https://rdap.verisign.com/com/v1/domain/twilio.com",
          "checkedAt": "2026-10-04T13:05:12.523190086Z"
        },
        "pages": [
          {
            "url": "https://www.twilio.com/en-us/sms/pricing/us",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:31:14.129427371Z",
            "changedAt": "2026-10-06T16:17:22.587177289Z",
            "fingerprint": "0d4f7123336a"
          }
        ],
        "updatedAt": "2026-10-08T21:12:24.133830249Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Twilio",
        "name": "Vendor"
      },
      {
        "a": "https://sms-voice.us-east-1.amazonaws.com",
        "b": "https://api.twilio.com/2010-04-01",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$0.0077 per message",
        "b": "$0.0083 per message",
        "name": "Price for messaging sms"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0",
        "b": "MIT",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "2",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-06",
        "b": "2026-09-28",
        "name": "Last release"
      },
      {
        "a": "2026-08-14",
        "b": "2026-07-16",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2026-04-09",
        "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": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "407k npm/wk",
        "b": "111 stars, 7.2M npm/wk, 4.8M PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.5/5 (8)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Twilio API + MCP scores 80.4 (A) on agent readiness against AWS End User Messaging's 74.3 (BB), and leads in 4 of 7 scored categories.",
        "question": "Which is better for AI agents, AWS End User Messaging or Twilio API + MCP?"
      },
      {
        "answer": "They cost about the same, $0.0077 per message for AWS End User Messaging and $0.0083 per message for Twilio API + MCP. These are the vendors' published prices for the job.",
        "question": "Which is cheaper for messaging sms, AWS End User Messaging or Twilio API + MCP?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do AWS End User Messaging and Twilio API + MCP need an API key?"
      },
      {
        "answer": "Yes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Twilio API + MCP at https://api.twilio.com/2010-04-01.",
        "question": "Can an agent call AWS End User Messaging and Twilio API + MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": null,
        "goodFor": "Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices.",
        "slug": "aws-end-user-messaging",
        "watchFor": "Sandbox limits new accounts to $1 of SMS a month and ten verified numbers until a support case per Region is approved"
      },
      {
        "aheadOn": [
          "Reliability, 90 against 73",
          "Agent ergonomics, 80 against 71",
          "Payments \u0026 pricing, 40 against 30"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.",
        "slug": "twilio",
        "watchFor": "US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate"
      }
    ],
    "job": {
      "capability": "messaging.sms",
      "name": "Messaging sms"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bandwidth.json",
        "title": "AWS End User Messaging vs Bandwidth Messaging API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bandwidth"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bird.json",
        "title": "AWS End User Messaging vs Bird API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bird"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-clicksend.json",
        "title": "AWS End User Messaging vs ClickSend SMS API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-clicksend"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-infobip.json",
        "title": "AWS End User Messaging vs Infobip API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-infobip"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.json",
        "title": "AWS End User Messaging vs Plivo API",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.json",
        "title": "AWS End User Messaging vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.json",
        "title": "AWS End User Messaging vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telnyx.json",
        "title": "AWS End User Messaging vs Telnyx API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telnyx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.json",
        "title": "AWS End User Messaging vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-twilio.json",
        "title": "Bandwidth Messaging API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bird-vs-twilio.json",
        "title": "Bird API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/bird-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clicksend-vs-twilio.json",
        "title": "ClickSend SMS API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/clicksend-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infobip-vs-twilio.json",
        "title": "Infobip API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/infobip-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plivo-vs-twilio.json",
        "title": "Plivo API vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-twilio.json",
        "title": "Sendblue vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sinch-vs-twilio.json",
        "title": "Sinch Messaging APIs + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/sinch-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/telnyx-vs-twilio.json",
        "title": "Telnyx API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/telnyx-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/twilio-vs-vonage.json",
        "title": "Twilio API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/twilio-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.json",
        "title": "360dialog WhatsApp API + MCP vs AWS End User Messaging",
        "url": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging"
      },
      {
        "json": "https://www.anchorterminal.com/compare/360dialog-vs-twilio.json",
        "title": "360dialog WhatsApp API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/360dialog-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.json",
        "title": "AWS End User Messaging vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.json",
        "title": "Twilio API + MCP vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api"
      }
    ],
    "scores": [
      {
        "aws-end-user-messaging": 73,
        "by": 17,
        "edge": "twilio",
        "key": "reliability",
        "name": "Reliability",
        "twilio": 90,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 88,
        "by": 4,
        "edge": "twilio",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "twilio": 92,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 71,
        "by": 9,
        "edge": "twilio",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "twilio": 80,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 88,
        "by": 3,
        "edge": "aws-end-user-messaging",
        "key": "security",
        "name": "Security \u0026 auth",
        "twilio": 85,
        "weight": 14
      },
      {
        "aws-end-user-messaging": 30,
        "by": 10,
        "edge": "twilio",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "twilio": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 85,
        "by": 0,
        "edge": "",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "twilio": 85,
        "weight": 7
      },
      {
        "aws-end-user-messaging": 83,
        "by": 2,
        "edge": "aws-end-user-messaging",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "twilio": 81,
        "weight": 7
      }
    ],
    "summary": "Twilio API + MCP scores 80.4 (A) on agent readiness against AWS End User Messaging's 74.3 (BB), and leads in 4 of 7 scored categories. Both do messaging sms.",
    "verdicts": {
      "aws-end-user-messaging": "IAM policies limit a credential to single actions and resources, CloudTrail can log every send, and enforced monthly spend limits cap cost. New accounts start in a sandbox with a $1 monthly SMS limit and ten verified recipients, production access needs a support case per Region, and the send actions take no idempotency token.",
      "twilio": "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio",
    "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.md",
    "slim": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.min.md"
  },
  "markdown": "Twilio API + MCP scores 80.4 (A) on agent readiness against AWS End User Messaging's 74.3 (BB), and leads in 4 of 7 scored categories. Both do messaging sms.\n\n- AWS End User Messaging: grade BB, 74.3/100, rank #64 of 722. Markdown https://www.anchorterminal.com/tools/aws-end-user-messaging.md · JSON https://www.anchorterminal.com/api/v1/tools/aws-end-user-messaging.json\n- Twilio API + MCP: grade A, 80.4/100, rank #8 of 722. Markdown https://www.anchorterminal.com/tools/twilio.md · JSON https://www.anchorterminal.com/api/v1/tools/twilio.json\n\n## Which one, for what\n\n### AWS End User Messaging (BB)\n\nGood for: Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices.\n\nWatch for: Sandbox limits new accounts to $1 of SMS a month and ten verified numbers until a support case per Region is approved\n\n### Twilio API + MCP (A)\n\nGood for: Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.\n\nAhead on:\n- Reliability, 90 against 73\n- Agent ergonomics, 80 against 71\n- Payments \u0026 pricing, 40 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate\n\n\n## Score by category\n\n| Category | Weight | AWS End User Messaging | Twilio API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 90 | Twilio API + MCP +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 92 | Twilio API + MCP +4 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 80 | Twilio API + MCP +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 88 | 85 | AWS End User Messaging +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Twilio API + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 85 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 81 | AWS End User Messaging +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.3 · BB** | **80.4 · A** | |\n\n## Facts side by side\n\n| Fact | AWS End User Messaging | Twilio API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Twilio |\n| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://api.twilio.com/2010-04-01` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for messaging sms | $0.0077 per message | $0.0083 per message |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0 | MIT |\n| Tools exposed | none | 2 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-09-28 |\n| Terms last updated | 2026-08-14 | 2026-07-16 |\n| Privacy policy last updated | 2026-05-18 | 2026-04-09 |\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 | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 407k npm/wk | 111 stars, 7.2M npm/wk, 4.8M PyPI/wk |\n| Agent reviews | none | 3.5/5 (8) |\n\n## Verdicts\n\n**AWS End User Messaging.** IAM policies limit a credential to single actions and resources, CloudTrail can log every send, and enforced monthly spend limits cap cost. New accounts start in a sandbox with a $1 monthly SMS limit and ten verified recipients, production access needs a support case per Region, and the send actions take no idempotency token.\n\n**Twilio API + MCP.** Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.\n\n## Before you call either\n\n### AWS End User Messaging\n\n1. Sign requests with SigV4 for service `sms-voice` at `sms-voice.\u003cregion\u003e.amazonaws.com`. WhatsApp uses a separate API, `social-messaging`\n2. Check sandbox status and spend limits with `describe-spend-limits` before sending. Sandbox sends reach only verified destination numbers\n3. Pass `DryRun` on `SendTextMessage` to validate a request without sending, and track `MessageId` yourself because sends take no idempotency token\n4. Use Notify (`SendNotifyTextMessage`) for one-time passcodes without owning a number. Generate and check the code in your own application\n5. Read inbound SMS and RCS from the Amazon SNS topic set on the number or pool, and treat message bodies as untrusted text\n\n### Twilio API + MCP\n\n1. Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key\n2. Set `ValidityPeriod` on time-sensitive sends, or a queued message can go out up to 10 hours late\n3. Check the Messages list for the original before retrying a send that timed out, there's no idempotency key\n4. On a trial account, send only to verified numbers in the sign-up country using Twilio's message templates, custom bodies aren't available until you upgrade\n5. Validate `X-Twilio-Signature` on every inbound webhook\n\n## Questions\n\n### Which is better for AI agents, AWS End User Messaging or Twilio API + MCP?\n\nTwilio API + MCP scores 80.4 (A) on agent readiness against AWS End User Messaging's 74.3 (BB), and leads in 4 of 7 scored categories.\n\n### Which is cheaper for messaging sms, AWS End User Messaging or Twilio API + MCP?\n\nThey cost about the same, $0.0077 per message for AWS End User Messaging and $0.0083 per message for Twilio API + MCP. These are the vendors' published prices for the job.\n\n### Do AWS End User Messaging and Twilio API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call AWS End User Messaging and Twilio API + MCP without installing anything?\n\nYes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Twilio API + MCP at https://api.twilio.com/2010-04-01.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-end-user-messaging\", \"b\": \"twilio\"}`. From a terminal: `anchor compare aws-end-user-messaging twilio`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aws-end-user-messaging.json and https://www.anchorterminal.com/api/v1/tools/twilio.json\n\n## Other comparisons with AWS End User Messaging or Twilio API + MCP\n\n- [AWS End User Messaging vs Bandwidth Messaging API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bandwidth.md)\n- [AWS End User Messaging vs Bird API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bird.md)\n- [AWS End User Messaging vs ClickSend SMS API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-clicksend.md)\n- [AWS End User Messaging vs Infobip API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-infobip.md)\n- [AWS End User Messaging vs Plivo API](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.md)\n- [AWS End User Messaging vs Sendblue](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.md)\n- [AWS End User Messaging vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.md)\n- [AWS End User Messaging vs Telnyx API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telnyx.md)\n- [AWS End User Messaging vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.md)\n- [Bandwidth Messaging API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-twilio.md)\n- [Bird API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bird-vs-twilio.md)\n- [ClickSend SMS API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-twilio.md)\n- [Infobip API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/infobip-vs-twilio.md)\n- [Plivo API vs Twilio API + MCP](https://www.anchorterminal.com/compare/plivo-vs-twilio.md)\n- [Sendblue vs Twilio API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-twilio.md)\n- [Sinch Messaging APIs + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/sinch-vs-twilio.md)\n- [Telnyx API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-twilio.md)\n- [Twilio API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/twilio-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs AWS End User Messaging](https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.md)\n- [360dialog WhatsApp API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-twilio.md)\n- [AWS End User Messaging vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.md)\n- [Twilio API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.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": "AWS End User Messaging vs Twilio API + MCP",
        "url": ""
      }
    ],
    "description": "Twilio API + MCP scores 80.4 (A) on agent readiness against AWS End User Messaging's 74.3 (BB), and leads in 4 of 7 scored categories. Both do messaging sms. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "AWS End User Messaging BB 74.3",
      "Twilio API + MCP A 80.4",
      "scores"
    ],
    "h1": "AWS End User Messaging vs Twilio API + MCP",
    "image": "https://www.anchorterminal.com/assets/og/compare-aws-end-user-messaging-vs-twilio.png",
    "path": "/compare/aws-end-user-messaging-vs-twilio",
    "published": "2026-10-01",
    "section": "tools",
    "title": "AWS End User Messaging vs Twilio API + MCP for AI agents",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio"
  },
  "tokens": {
    "markdown": 2550,
    "slim": 630
  },
  "version": 1
}