{
  "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:53:16.166855379Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 253,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 257,
          "p95ms24h": 291,
          "samples24h": 28,
          "samples30d": 28,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 28,
              "ok": 28
            }
          ]
        },
        "updatedAt": "2026-10-08T21:53:16.166855379Z"
      }
    },
    "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sinch Messaging APIs + MCP's 63.2 (B), and leads in 5 of 7 scored categories. Sinch Messaging APIs + MCP leads on payments \u0026 pricing.",
    "b": {
      "slug": "sinch",
      "name": "Sinch Messaging APIs + MCP",
      "vendor": "Sinch",
      "vendorUrl": "https://sinch.com",
      "kind": "http-api",
      "category": "messaging",
      "summary": "The SMS REST API and the Conversation API, which sends SMS, RCS, WhatsApp, Viber and Messenger through one message format, plus the Verification API.",
      "url": "https://www.anchorterminal.com/tools/sinch",
      "markdownUrl": "https://www.anchorterminal.com/tools/sinch.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sinch.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sinch.json",
      "repo": "https://github.com/sinch/sinch-mcp-server",
      "license": "Apache-2.0",
      "transports": [
        "http",
        "stdio",
        "streamable-http"
      ],
      "remoteUrl": "https://us.sms.api.sinch.com/xms/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "@sinch/sdk-core"
        },
        {
          "registry": "pypi",
          "name": "sinch"
        },
        {
          "registry": "npm",
          "name": "@sinch/mcp"
        }
      ],
      "auth": "mixed",
      "authNotes": "The SMS API takes a service-plan Bearer token. Conversation, Numbers and Templates use OAuth 2.0 client credentials from a project access key (Basic auth also accepted). Verification and Voice use an application key and secret. The MCP server's HTTP mode does no inbound auth in single-tenant mode.",
      "pricing": "usage",
      "pricingNotes": "Pay as you go. US SMS $0.0078 a message on 10DLC or toll-free and $0.009 on short code, same rate inbound, plus carrier fees. Other countries and WhatsApp are priced through a country selector. Trial accounts get 2 units of local currency (for example $2) and a test number, no card (https://sinch.com/pricing/sms/).",
      "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": 54,
      "popularity": {
        "githubStars": 1,
        "npmWeekly": 15648,
        "pypiWeekly": 11166,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://developers.sinch.com/docs/conversation",
      "llmsTxt": "https://developers.sinch.com/llms.txt",
      "openapi": "https://developers.sinch.com/_bundle/docs/conversation/api-reference/conversation.yaml",
      "capabilities": [
        "messaging.sms",
        "messaging.whatsapp",
        "messaging.rcs",
        "messaging.verify",
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "no-card",
        "mcp",
        "openapi",
        "llms-txt",
        "typescript",
        "python",
        "webhooks",
        "whatsapp",
        "sms",
        "enterprise"
      ],
      "lastRelease": "2026-09-23",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 63.2,
        "grade": "B",
        "agentReady": false,
        "rank": 315,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 8,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 50,
          "maintenance": 83,
          "payments": 40,
          "reliability": 73,
          "schema": 81,
          "security": 50,
          "transparency": 72
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format. The MCP server is a developer preview whose npm release dates from 2026-04-14.",
        "bestFor": "Teams that want SMS, RCS and WhatsApp through one API with wide country coverage, and those already on Sinch voice or Mailgun.",
        "strengths": [
          "The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format",
          "Published limits of 800 requests a second per project and a 500,000-message queue per app",
          "HMAC-signed callbacks with a nonce and timestamp",
          "Trial with 2 units of local currency and a test number, no card",
          "SDK releases in Java and Python in September 2026"
        ],
        "weaknesses": [
          "The MCP server is a developer preview whose npm release dates from 2026-04-14",
          "54 MCP tools with no readOnlyHint or destructiveHint annotations",
          "Separate credential schemes for the SMS, Conversation and Verification APIs, none with scopes",
          "No SLA, and no Retry-After on 429",
          "No security.txt or bug bounty found"
        ],
        "agentNotes": [
          "Load the MCP with `--tags` for the channels you need, or all 54 tools land in context",
          "Keep a single-tenant HTTP MCP bound to localhost, it does no inbound authentication",
          "Expect sends to drain at 20 messages a second per app unless Sinch raises it",
          "Verify `x-sinch-webhook-signature` against the raw body before parsing the JSON",
          "Use the regional base URL (us, eu or br) that matches the project"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 63.2
          }
        ],
        "editorialScores": {
          "ergonomics": 50,
          "maintenance": 83,
          "payments": 40,
          "reliability": 73,
          "schema": 81,
          "security": 50,
          "transparency": 55
        },
        "provenanceScore": 88
      },
      "connect": {
        "http": "curl -X POST \"https://us.sms.api.sinch.com/xms/v1/$SINCH_SERVICE_PLAN_ID/batches\" \\\n  -H \"Authorization: Bearer $SINCH_API_TOKEN\" -H \"Content-Type: application/json\" \\\n  -d '{\"from\":\"+12025550123\",\"to\":[\"+15551234567\"],\"body\":\"Hello from Sinch\"}'",
        "config": {
          "mcpServers": {
            "sinch": {
              "args": [
                "-y",
                "@sinch/mcp"
              ],
              "command": "npx",
              "env": {
                "CONVERSATION_APP_ID": "${SINCH_CONVERSATION_APP_ID}",
                "CONVERSATION_REGION": "us",
                "KEY_ID": "${SINCH_KEY_ID}",
                "KEY_SECRET": "${SINCH_KEY_SECRET}",
                "PROJECT_ID": "${SINCH_PROJECT_ID}"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/sinch"
      },
      "sameCompany": [
        "sinch-voice"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "SMS outbound, US 10DLC or toll-free",
          "unit": "message",
          "usd": 0.0078,
          "note": "plus carrier fees"
        },
        {
          "item": "SMS outbound, US short code",
          "unit": "message",
          "usd": 0.009,
          "note": "plus carrier fees"
        }
      ],
      "provenance": {
        "legalEntity": "Sinch AB (publ)",
        "domain": "sinch.com",
        "domainRegistered": "1997-12-03",
        "endpointOnVendorDomain": true,
        "terms": "https://sinch.com/legal/terms-and-conditions/other-sinch-terms-conditions/general-terms-and-conditions/",
        "privacy": "https://sinch.com/legal/privacy-notice/",
        "statusPage": "https://status.sinch.com",
        "changelog": "https://developers.sinch.com/docs/conversation/release-notes",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "The general terms name the contracting Sinch entity only in the order form or master agreement. Sinch AB (publ) is the listed parent."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/sinch.json",
      "live": {
        "slug": "sinch",
        "probe": {
          "target": "https://us.sms.api.sinch.com/xms/v1",
          "method": "get",
          "lastAt": "2026-10-08T21:53:34.116901803Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 255,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 253,
          "p95ms24h": 288,
          "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
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.sinch.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-08T21:58:14.476541272Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "sinch/sinch-mcp-server",
            "version": "v0.0.1-alpha6",
            "released": "2026-04-14",
            "seenAt": "2026-10-08T16:29:35.10106415Z"
          },
          {
            "registry": "npm",
            "name": "@sinch/mcp",
            "version": "0.0.1-alpha.6",
            "seenAt": "2026-10-08T16:29:33.234375695Z"
          },
          {
            "registry": "npm",
            "name": "@sinch/sdk-core",
            "version": "1.6.0",
            "seenAt": "2026-10-08T16:29:32.892734455Z"
          },
          {
            "registry": "pypi",
            "name": "sinch",
            "version": "2.2.0",
            "released": "2026-09-21",
            "seenAt": "2026-10-08T16:29:33.12178482Z"
          }
        ],
        "githubStars": 1,
        "npmWeekly": 18516,
        "pypiWeekly": 13854,
        "securityTxt": {
          "url": "https://sinch.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:47.862783137Z"
        },
        "llmsTxt": {
          "url": "https://developers.sinch.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:54.449236167Z"
        },
        "domain": {
          "domain": "sinch.com",
          "registered": "1997-12-03",
          "source": "https://rdap.verisign.com/com/v1/domain/sinch.com",
          "checkedAt": "2026-10-04T13:05:54.744606475Z"
        },
        "pages": [
          {
            "url": "https://developers.sinch.com/docs/conversation/release-notes",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:17:59.292836807Z",
            "changedAt": "2026-10-05T15:55:19.291475702Z",
            "fingerprint": "d94b5f1113a7"
          },
          {
            "url": "https://sinch.com/pricing/sms/",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-10-08T18:24:25.916636512Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "4d9f998b696c"
          }
        ],
        "updatedAt": "2026-10-08T21:58:14.476541272Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Sinch",
        "name": "Vendor"
      },
      {
        "a": "https://sms-voice.us-east-1.amazonaws.com",
        "b": "https://us.sms.api.sinch.com/xms/v1",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, stdio, Streamable HTTP",
        "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.0078 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": "Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "54",
        "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-23",
        "name": "Last release"
      },
      {
        "a": "2026-08-14",
        "b": "2026-06-01",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2025-12-12",
        "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": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "407k npm/wk",
        "b": "1 stars, 16k npm/wk, 11k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sinch Messaging APIs + MCP's 63.2 (B), and leads in 5 of 7 scored categories. Sinch Messaging APIs + MCP leads on payments \u0026 pricing.",
        "question": "Which is better for AI agents, AWS End User Messaging or Sinch Messaging APIs + MCP?"
      },
      {
        "answer": "They cost about the same, $0.0077 per message for AWS End User Messaging and $0.0078 per message for Sinch Messaging APIs + MCP. These are the vendors' published prices for the job.",
        "question": "Which is cheaper for messaging sms, AWS End User Messaging or Sinch Messaging APIs + MCP?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do AWS End User Messaging and Sinch Messaging APIs + 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 Sinch Messaging APIs + MCP at https://us.sms.api.sinch.com/xms/v1.",
        "question": "Can an agent call AWS End User Messaging and Sinch Messaging APIs + MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 88 against 81",
          "Agent ergonomics, 71 against 50",
          "Security \u0026 auth, 88 against 50",
          "Transparency \u0026 trust, 83 against 72"
        ],
        "also": [
          "Agent-ready, a grade of BB or better"
        ],
        "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": [
          "Payments \u0026 pricing, 40 against 30"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Teams that want SMS, RCS and WhatsApp through one API with wide country coverage, and those already on Sinch voice or Mailgun.",
        "slug": "sinch",
        "watchFor": "The MCP server is a developer preview whose npm release dates from 2026-04-14"
      }
    ],
    "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-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-twilio.json",
        "title": "AWS End User Messaging vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio"
      },
      {
        "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-sinch.json",
        "title": "Bandwidth Messaging API + MCP vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bird-vs-sinch.json",
        "title": "Bird API + MCP vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/bird-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clicksend-vs-sinch.json",
        "title": "ClickSend SMS API + MCP vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/clicksend-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infobip-vs-sinch.json",
        "title": "Infobip API + MCP vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/infobip-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plivo-vs-sinch.json",
        "title": "Plivo API vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-sinch.json",
        "title": "Sendblue vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sinch-vs-telnyx.json",
        "title": "Sinch Messaging APIs + MCP vs Telnyx API + MCP",
        "url": "https://www.anchorterminal.com/compare/sinch-vs-telnyx"
      },
      {
        "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/sinch-vs-vonage.json",
        "title": "Sinch Messaging APIs + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/sinch-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-sinch.json",
        "title": "360dialog WhatsApp API + MCP vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/360dialog-vs-sinch"
      },
      {
        "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/sinch-vs-whatsapp-cloud-api.json",
        "title": "Sinch Messaging APIs + MCP vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api"
      }
    ],
    "scores": [
      {
        "aws-end-user-messaging": 73,
        "by": 0,
        "edge": "",
        "key": "reliability",
        "name": "Reliability",
        "sinch": 73,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 88,
        "by": 7,
        "edge": "aws-end-user-messaging",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "sinch": 81,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 71,
        "by": 21,
        "edge": "aws-end-user-messaging",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "sinch": 50,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 88,
        "by": 38,
        "edge": "aws-end-user-messaging",
        "key": "security",
        "name": "Security \u0026 auth",
        "sinch": 50,
        "weight": 14
      },
      {
        "aws-end-user-messaging": 30,
        "by": 10,
        "edge": "sinch",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "sinch": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 85,
        "by": 2,
        "edge": "aws-end-user-messaging",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "sinch": 83,
        "weight": 7
      },
      {
        "aws-end-user-messaging": 83,
        "by": 11,
        "edge": "aws-end-user-messaging",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "sinch": 72,
        "weight": 7
      }
    ],
    "summary": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sinch Messaging APIs + MCP's 63.2 (B), and leads in 5 of 7 scored categories. Sinch Messaging APIs + MCP leads on payments \u0026 pricing. 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.",
      "sinch": "The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format. The MCP server is a developer preview whose npm release dates from 2026-04-14."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch",
    "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.md",
    "slim": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.min.md"
  },
  "markdown": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sinch Messaging APIs + MCP's 63.2 (B), and leads in 5 of 7 scored categories. Sinch Messaging APIs + MCP leads on payments \u0026 pricing. 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- Sinch Messaging APIs + MCP: grade B, 63.2/100, rank #315 of 722. Markdown https://www.anchorterminal.com/tools/sinch.md · JSON https://www.anchorterminal.com/api/v1/tools/sinch.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\nAhead on:\n- Schema \u0026 documentation, 88 against 81\n- Agent ergonomics, 71 against 50\n- Security \u0026 auth, 88 against 50\n- Transparency \u0026 trust, 83 against 72\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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### Sinch Messaging APIs + MCP (B)\n\nGood for: Teams that want SMS, RCS and WhatsApp through one API with wide country coverage, and those already on Sinch voice or Mailgun.\n\nAhead on:\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: The MCP server is a developer preview whose npm release dates from 2026-04-14\n\n\n## Score by category\n\n| Category | Weight | AWS End User Messaging | Sinch Messaging APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 73 | even |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 81 | AWS End User Messaging +7 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 50 | AWS End User Messaging +21 |\n| Security \u0026 auth | 14% (17.5 this run) | 88 | 50 | AWS End User Messaging +38 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Sinch Messaging APIs + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 83 | AWS End User Messaging +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 72 | AWS End User Messaging +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.3 · BB** | **63.2 · B** | |\n\n## Facts side by side\n\n| Fact | AWS End User Messaging | Sinch Messaging APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Sinch |\n| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://us.sms.api.sinch.com/xms/v1` |\n| Transports | HTTP | HTTP, stdio, Streamable HTTP |\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.0078 per message |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0 | Apache-2.0 |\n| Tools exposed | none | 54 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-09-23 |\n| Terms last updated | 2026-08-14 | 2026-06-01 |\n| Privacy policy last updated | 2026-05-18 | 2025-12-12 |\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 | not found in the text |\n| Popularity | 407k npm/wk | 1 stars, 16k npm/wk, 11k PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\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**Sinch Messaging APIs + MCP.** The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format. The MCP server is a developer preview whose npm release dates from 2026-04-14.\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### Sinch Messaging APIs + MCP\n\n1. Load the MCP with `--tags` for the channels you need, or all 54 tools land in context\n2. Keep a single-tenant HTTP MCP bound to localhost, it does no inbound authentication\n3. Expect sends to drain at 20 messages a second per app unless Sinch raises it\n4. Verify `x-sinch-webhook-signature` against the raw body before parsing the JSON\n5. Use the regional base URL (us, eu or br) that matches the project\n\n## Questions\n\n### Which is better for AI agents, AWS End User Messaging or Sinch Messaging APIs + MCP?\n\nAWS End User Messaging scores 74.3 (BB) on agent readiness against Sinch Messaging APIs + MCP's 63.2 (B), and leads in 5 of 7 scored categories. Sinch Messaging APIs + MCP leads on payments \u0026 pricing.\n\n### Which is cheaper for messaging sms, AWS End User Messaging or Sinch Messaging APIs + MCP?\n\nThey cost about the same, $0.0077 per message for AWS End User Messaging and $0.0078 per message for Sinch Messaging APIs + MCP. These are the vendors' published prices for the job.\n\n### Do AWS End User Messaging and Sinch Messaging APIs + 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 Sinch Messaging APIs + MCP without installing anything?\n\nYes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Sinch Messaging APIs + MCP at https://us.sms.api.sinch.com/xms/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-end-user-messaging\", \"b\": \"sinch\"}`. From a terminal: `anchor compare aws-end-user-messaging sinch`\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/sinch.json\n\n## Other comparisons with AWS End User Messaging or Sinch Messaging APIs + 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 Telnyx API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telnyx.md)\n- [AWS End User Messaging vs Twilio API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.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 Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-sinch.md)\n- [Bird API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bird-vs-sinch.md)\n- [ClickSend SMS API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/clicksend-vs-sinch.md)\n- [Infobip API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/infobip-vs-sinch.md)\n- [Plivo API vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/plivo-vs-sinch.md)\n- [Sendblue vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/sendblue-vs-sinch.md)\n- [Sinch Messaging APIs + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/sinch-vs-telnyx.md)\n- [Sinch Messaging APIs + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/sinch-vs-twilio.md)\n- [Sinch Messaging APIs + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sinch-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 Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/360dialog-vs-sinch.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- [Sinch Messaging APIs + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sinch-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 Sinch Messaging APIs + MCP",
        "url": ""
      }
    ],
    "description": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sinch Messaging APIs + MCP's 63.2 (B), and leads in 5 of 7 scored categories. Sinch Messaging APIs + MCP leads on payments \u0026 pricing. Both do messaging sms. Category scores, facts, verdicts and agent notes side…",
    "facts": [
      "AWS End User Messaging BB 74.3",
      "Sinch Messaging APIs + MCP B 63.2",
      "scores"
    ],
    "h1": "AWS End User Messaging vs Sinch Messaging APIs + MCP",
    "image": "https://www.anchorterminal.com/assets/og/compare-aws-end-user-messaging-vs-sinch.png",
    "path": "/compare/aws-end-user-messaging-vs-sinch",
    "published": "2026-10-01",
    "section": "tools",
    "title": "AWS End User Messaging vs Sinch Messaging APIs + MCP for AI agents",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sinch"
  },
  "tokens": {
    "markdown": 2650,
    "slim": 680
  },
  "version": 1
}