{
  "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": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + MCP leads on payments \u0026 pricing.",
    "b": {
      "slug": "vonage",
      "name": "Vonage Messages API + MCP",
      "vendor": "Vonage (Ericsson)",
      "vendorUrl": "https://www.vonage.com",
      "kind": "http-api",
      "category": "messaging",
      "summary": "One endpoint (POST /v1/messages) for SMS, MMS, WhatsApp, RCS, Viber and Messenger, with failover between channels.",
      "url": "https://www.anchorterminal.com/tools/vonage",
      "markdownUrl": "https://www.anchorterminal.com/tools/vonage.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vonage.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vonage.json",
      "repo": "https://github.com/Vonage-Community/vonage-mcp-server-api-bindings",
      "license": "Apache-2.0",
      "transports": [
        "http",
        "stdio",
        "streamable-http"
      ],
      "remoteUrl": "https://api.nexmo.com/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "@vonage/server-sdk"
        },
        {
          "registry": "pypi",
          "name": "vonage"
        },
        {
          "registry": "npm",
          "name": "@vonage/vonage-mcp-server-api-bindings"
        }
      ],
      "auth": "mixed",
      "authNotes": "Messages API takes a Vonage Application JWT (RS256, signed with the application's private key) or Basic auth with the API key and secret. Basic auth doesn't deliver to application-level webhooks. Inbound webhooks carry an HS256 JWT to verify. The MCP server reads the key, secret, application ID and a base64 private key from env vars.",
      "pricing": "usage",
      "pricingNotes": "Pay as you go per message. Rates vary by country and channel and appear only through a country selector or a downloadable sheet. WhatsApp adds a Vonage platform fee to Meta's template fees. New accounts get €2 of test credit and no card is needed (https://www.vonage.com/communications-apis/messages/pricing/).",
      "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": 15,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 154249,
        "pypiWeekly": 67062,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://developer.vonage.com/en/messages/overview",
      "llmsTxt": "https://developer.vonage.com/llms.txt",
      "openapi": "https://developer.vonage.com/api/v1/developer/api/file/messages?format=json",
      "registryName": "io.github.Vonage/vonage-documentation-mcp",
      "capabilities": [
        "messaging.sms",
        "messaging.mms",
        "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-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 66.8,
        "grade": "B",
        "agentReady": false,
        "rank": 227,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 6,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 50,
          "maintenance": 80,
          "payments": 37,
          "reliability": 77,
          "schema": 90,
          "security": 73,
          "transparency": 49
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.",
        "bestFor": "Agents that need several chat channels behind one call with SMS failover.",
        "strengths": [
          "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS",
          "OpenAPI 3.0.3 spec for the Messages API (version 1.19.1), and SDK releases in Node and Python through September 2026",
          "75 requests a second per API key, with Retry-After and X-RateLimit headers on 429",
          "Application JWTs with ACL claims that limit paths and methods",
          "ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR listed on the security page, and an Audit API for account events"
        ],
        "weaknesses": [
          "No idempotency key, and channel rejections arrive only by status webhook after a 202",
          "The sending MCP lives in the Vonage-Community GitHub organisation, last released on 2026-05-26, with no tool annotations",
          "SMS, WhatsApp and RCS prices sit behind a country selector, and the terms body doesn't render without a browser",
          "No SLA, security.txt, sub-processor list or retention periods found",
          "The Audit API costs $550 a month"
        ],
        "agentNotes": [
          "Keep api.nexmo.com as the host, don't rewrite it to vonage.com",
          "Use the Messages API, not the legacy SMS API",
          "Treat a 202 as accepted only, and wait for the status webhook before assuming delivery",
          "Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks",
          "Verify the webhook JWT and its payload_hash against the raw body"
        ],
        "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": 66.8
          }
        ],
        "editorialScores": {
          "ergonomics": 50,
          "maintenance": 80,
          "payments": 37,
          "reliability": 77,
          "schema": 90,
          "security": 73,
          "transparency": 28
        },
        "provenanceScore": 69
      },
      "connect": {
        "http": "curl https://api.nexmo.com/v1/messages -u \"$VONAGE_API_KEY:$VONAGE_API_SECRET\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"message_type\":\"text\",\"channel\":\"sms\",\"to\":\"447700900000\",\"from\":\"Vonage\",\"text\":\"Hello from Vonage\"}'",
        "claudeCode": "claude mcp add --transport http vonage-docs https://documentation-mcp.vonage.dev/mcp",
        "config": {
          "mcpServers": {
            "vonage": {
              "args": [
                "-y",
                "@vonage/vonage-mcp-server-api-bindings"
              ],
              "command": "npx",
              "env": {
                "VONAGE_API_KEY": "${VONAGE_API_KEY}",
                "VONAGE_API_SECRET": "${VONAGE_API_SECRET}",
                "VONAGE_APPLICATION_ID": "${VONAGE_APPLICATION_ID}",
                "VONAGE_PRIVATE_KEY64": "${VONAGE_PRIVATE_KEY64}",
                "VONAGE_VIRTUAL_NUMBER": "${VONAGE_VIRTUAL_NUMBER}"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/vonage"
      },
      "sameCompany": [
        "vonage-voice"
      ],
      "area": "communication",
      "provenance": {
        "legalEntity": "Vonage Holdings Corp.",
        "domain": "vonage.com",
        "domainRegistered": "2000-12-12",
        "domainNote": "The API endpoints sit on the legacy nexmo.com domain, from Nexmo's acquisition in 2016.",
        "endpointOnVendorDomain": false,
        "terms": "https://www.vonage.com/legal/communications-apis/terms-of-use/",
        "privacy": "https://www.vonage.com/legal/privacy-policy/",
        "statusPage": "https://vonageapi.statuspage.io",
        "changelog": "https://developer.vonage.com/en/changelogs",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "The privacy notice names Vonage Holdings Corp. as controller where one entity applies. The API terms set the contracting entity by customer region in Schedule 1, which we couldn't read because vonage.com returned 403 to automated requests."
        ],
        "score": 69
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage.json",
      "live": {
        "slug": "vonage",
        "probe": {
          "target": "https://api.nexmo.com/v1",
          "method": "get",
          "lastAt": "2026-10-08T21:12:25.592330603Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 44,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 24,
          "p95ms24h": 60,
          "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://vonageapi.statuspage.io",
          "indicator": "minor",
          "summary": "Partially Degraded Service",
          "checkedAt": "2026-10-08T21:06:29.895460909Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "Vonage-Community/vonage-mcp-server-api-bindings",
            "version": "v1.5.0",
            "released": "2026-05-21",
            "seenAt": "2026-10-08T16:34:38.629372145Z"
          },
          {
            "registry": "mcp-registry",
            "name": "io.github.Vonage/vonage-documentation-mcp",
            "version": "1.0.0",
            "seenAt": "2026-10-08T02:42:52.272076636Z"
          },
          {
            "registry": "npm",
            "name": "@vonage/server-sdk",
            "version": "3.30.1",
            "seenAt": "2026-10-08T16:34:34.591582249Z"
          },
          {
            "registry": "npm",
            "name": "@vonage/vonage-mcp-server-api-bindings",
            "version": "1.5.1",
            "seenAt": "2026-10-08T16:34:36.752056116Z"
          },
          {
            "registry": "pypi",
            "name": "vonage",
            "version": "4.9.0",
            "released": "2026-09-16",
            "seenAt": "2026-10-08T16:34:36.643960692Z"
          }
        ],
        "githubStars": 3,
        "npmWeekly": 151884,
        "pypiWeekly": 63193,
        "securityTxt": {
          "url": "https://vonage.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:38.377472768Z"
        },
        "llmsTxt": {
          "url": "https://developer.vonage.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:01:01.755882378Z"
        },
        "domain": {
          "domain": "vonage.com",
          "registered": "2000-12-12",
          "source": "https://rdap.verisign.com/com/v1/domain/vonage.com",
          "checkedAt": "2026-10-04T13:04:15.703583171Z"
        },
        "pages": [
          {
            "url": "https://www.vonage.com/communications-apis/messages/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:31:27.125076816Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "78c0a0681698"
          }
        ],
        "updatedAt": "2026-10-08T21:12:25.592330603Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Vonage (Ericsson)",
        "name": "Vendor"
      },
      {
        "a": "https://sms-voice.us-east-1.amazonaws.com",
        "b": "https://api.nexmo.com/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": "not published",
        "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": "15",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "io.github.Vonage/vonage-documentation-mcp",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-06",
        "b": "2026-09-16",
        "name": "Last release"
      },
      {
        "a": "2026-08-14",
        "b": "couldn't be read",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "couldn't be read",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "407k npm/wk",
        "b": "154k npm/wk, 67k 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 Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + MCP leads on payments \u0026 pricing.",
        "question": "Which is better for AI agents, AWS End User Messaging or Vonage Messages API + MCP?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do AWS End User Messaging and Vonage Messages 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 Vonage Messages API + MCP at https://api.nexmo.com/v1.",
        "question": "Can an agent call AWS End User Messaging and Vonage Messages API + MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 71 against 50",
          "Security \u0026 auth, 88 against 73",
          "Maintenance \u0026 community, 85 against 80",
          "Transparency \u0026 trust, 83 against 49"
        ],
        "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, 37 against 30"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Agents that need several chat channels behind one call with SMS failover.",
        "slug": "vonage",
        "watchFor": "No idempotency key, and channel rejections arrive only by status webhook after a 202"
      }
    ],
    "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-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/bandwidth-vs-vonage.json",
        "title": "Bandwidth Messaging API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bird-vs-vonage.json",
        "title": "Bird API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/bird-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clicksend-vs-vonage.json",
        "title": "ClickSend SMS API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/clicksend-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infobip-vs-vonage.json",
        "title": "Infobip API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/infobip-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plivo-vs-vonage.json",
        "title": "Plivo API vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-vonage.json",
        "title": "Sendblue vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-vonage"
      },
      {
        "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/telnyx-vs-vonage.json",
        "title": "Telnyx API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/telnyx-vs-vonage"
      },
      {
        "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-vonage.json",
        "title": "360dialog WhatsApp API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/360dialog-vs-vonage"
      },
      {
        "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/vonage-vs-whatsapp-cloud-api.json",
        "title": "Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api"
      }
    ],
    "scores": [
      {
        "aws-end-user-messaging": 73,
        "by": 4,
        "edge": "vonage",
        "key": "reliability",
        "name": "Reliability",
        "vonage": 77,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 88,
        "by": 2,
        "edge": "vonage",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "vonage": 90,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 71,
        "by": 21,
        "edge": "aws-end-user-messaging",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "vonage": 50,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 88,
        "by": 15,
        "edge": "aws-end-user-messaging",
        "key": "security",
        "name": "Security \u0026 auth",
        "vonage": 73,
        "weight": 14
      },
      {
        "aws-end-user-messaging": 30,
        "by": 7,
        "edge": "vonage",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "vonage": 37,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 85,
        "by": 5,
        "edge": "aws-end-user-messaging",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "vonage": 80,
        "weight": 7
      },
      {
        "aws-end-user-messaging": 83,
        "by": 34,
        "edge": "aws-end-user-messaging",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "vonage": 49,
        "weight": 7
      }
    ],
    "summary": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + 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.",
      "vonage": "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage",
    "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.md",
    "slim": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.min.md"
  },
  "markdown": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + 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- Vonage Messages API + MCP: grade B, 66.8/100, rank #227 of 722. Markdown https://www.anchorterminal.com/tools/vonage.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage.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- Agent ergonomics, 71 against 50\n- Security \u0026 auth, 88 against 73\n- Maintenance \u0026 community, 85 against 80\n- Transparency \u0026 trust, 83 against 49\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### Vonage Messages API + MCP (B)\n\nGood for: Agents that need several chat channels behind one call with SMS failover.\n\nAhead on:\n- Payments \u0026 pricing, 37 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No idempotency key, and channel rejections arrive only by status webhook after a 202\n\n\n## Score by category\n\n| Category | Weight | AWS End User Messaging | Vonage Messages API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 77 | Vonage Messages API + MCP +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 90 | Vonage Messages API + MCP +2 |\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 | 73 | AWS End User Messaging +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 37 | Vonage Messages API + MCP +7 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 80 | AWS End User Messaging +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 49 | AWS End User Messaging +34 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.3 · BB** | **66.8 · B** | |\n\n## Facts side by side\n\n| Fact | AWS End User Messaging | Vonage Messages API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Vonage (Ericsson) |\n| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://api.nexmo.com/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 | not published |\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 | 15 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |\n| Last release | 2026-10-06 | 2026-09-16 |\n| Terms last updated | 2026-08-14 | couldn't be read |\n| Privacy policy last updated | 2026-05-18 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | 407k npm/wk | 154k npm/wk, 67k 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**Vonage Messages API + MCP.** POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.\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### Vonage Messages API + MCP\n\n1. Keep api.nexmo.com as the host, don't rewrite it to vonage.com\n2. Use the Messages API, not the legacy SMS API\n3. Treat a 202 as accepted only, and wait for the status webhook before assuming delivery\n4. Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks\n5. Verify the webhook JWT and its payload_hash against the raw body\n\n## Questions\n\n### Which is better for AI agents, AWS End User Messaging or Vonage Messages API + MCP?\n\nAWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + MCP leads on payments \u0026 pricing.\n\n### Do AWS End User Messaging and Vonage Messages 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 Vonage Messages 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 Vonage Messages API + MCP at https://api.nexmo.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-end-user-messaging\", \"b\": \"vonage\"}`. From a terminal: `anchor compare aws-end-user-messaging vonage`\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/vonage.json\n\n## Other comparisons with AWS End User Messaging or Vonage Messages 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 Twilio API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-twilio.md)\n- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md)\n- [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md)\n- [ClickSend SMS API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md)\n- [Sendblue vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-vonage.md)\n- [Sinch Messaging APIs + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sinch-vs-vonage.md)\n- [Telnyx API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-vonage.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 Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.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- [Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/vonage-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 Vonage Messages API + MCP",
        "url": ""
      }
    ],
    "description": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + MCP leads on payments \u0026 pricing. Both do messaging sms. Category scores, facts, verdicts and agent notes side by…",
    "facts": [
      "AWS End User Messaging BB 74.3",
      "Vonage Messages API + MCP B 66.8",
      "scores"
    ],
    "h1": "AWS End User Messaging vs Vonage Messages API + MCP",
    "image": "https://www.anchorterminal.com/assets/og/compare-aws-end-user-messaging-vs-vonage.png",
    "path": "/compare/aws-end-user-messaging-vs-vonage",
    "published": "2026-10-01",
    "section": "tools",
    "title": "AWS End User Messaging vs Vonage Messages API + MCP for AI agents",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage"
  },
  "tokens": {
    "markdown": 2600,
    "slim": 780
  },
  "version": 1
}