{
  "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 Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on reliability and payments \u0026 pricing.",
    "b": {
      "slug": "plivo",
      "name": "Plivo API",
      "vendor": "Plivo",
      "vendorUrl": "https://www.plivo.com",
      "kind": "http-api",
      "category": "messaging",
      "summary": "CPaaS REST API for SMS, MMS, RCS and WhatsApp in 190+ countries, alongside voice.",
      "url": "https://www.anchorterminal.com/tools/plivo",
      "markdownUrl": "https://www.anchorterminal.com/tools/plivo.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/plivo.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/plivo.json",
      "repo": "https://github.com/plivo/plivo-node",
      "license": "MIT",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.plivo.com/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "plivo"
        },
        {
          "registry": "pypi",
          "name": "plivo"
        }
      ],
      "auth": "api-key",
      "authNotes": "HTTP Basic auth with Auth ID and Auth Token. The Auth ID also appears in every request path. Subaccounts get their own credentials.",
      "pricing": "usage",
      "pricingNotes": "Pay as you go with free trial credits and no card to sign up. US long code SMS $0.0077 outbound and inbound, toll-free $0.0079, MMS $0.018, plus carrier surcharges ($0.0035 to $0.005 a message). Long code numbers $0.50 a month. WhatsApp US marketing $0.0275 and utility $0.00374 a message. UK SMS from $0.0372 (https://www.plivo.com/sms/pricing/us/).",
      "priceSummary": "Pay per use",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402 or stablecoin payment path in docs, pricing or agent discovery files (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 102,
        "npmWeekly": 50920,
        "pypiWeekly": 69307,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://www.plivo.com/docs/",
      "llmsTxt": "https://www.plivo.com/docs/llms.txt",
      "capabilities": [
        "messaging.sms",
        "messaging.mms",
        "messaging.rcs",
        "messaging.whatsapp",
        "messaging.voice",
        "messaging.verify",
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "no-card",
        "llms-txt",
        "typescript",
        "python",
        "webhooks",
        "sms",
        "whatsapp"
      ],
      "lastRelease": "2026-09-25",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 60.3,
        "grade": "C",
        "agentReady": false,
        "rank": 406,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 10,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 57,
          "maintenance": 78,
          "payments": 40,
          "reliability": 78,
          "schema": 59,
          "security": 45,
          "transparency": 70
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.",
        "bestFor": "Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.",
        "strengths": [
          "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier",
          "Free trial credits with no card",
          "Published API limit of 300 requests per 5 seconds",
          "plivo-python released on 2026-07-28 and 2026-09-25",
          "Signed webhooks, and SOC 2, PCI DSS Level 1 and HIPAA per Plivo's security page"
        ],
        "weaknesses": [
          "No OpenAPI spec",
          "One Auth ID and token per account or subaccount, with no scopes or read-only keys",
          "The official MCP has one tool and only searches docs",
          "Inbound US SMS is billed at $0.0077 too, plus a T-Mobile inbound surcharge of $0.0025",
          "No availability SLA, the service levels document covers support response times only"
        ],
        "agentNotes": [
          "Put the Auth ID in both the path and the Basic auth header, every request needs both",
          "Stay under 300 API requests per 5 seconds, a 429 carries no Retry-After",
          "Give each agent its own subaccount to isolate credentials and spend",
          "Use the docs MCP to find endpoints, then call the REST API directly to send"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 60.3
          }
        ],
        "editorialScores": {
          "ergonomics": 57,
          "maintenance": 78,
          "payments": 40,
          "reliability": 78,
          "schema": 59,
          "security": 45,
          "transparency": 50
        },
        "provenanceScore": 89
      },
      "connect": {
        "http": "curl -X POST \"https://api.plivo.com/v1/Account/$PLIVO_AUTH_ID/Message/\" -u \"$PLIVO_AUTH_ID:$PLIVO_AUTH_TOKEN\" \\\n  -H \"Content-Type: application/json\" -d '{\"src\":\"+14155550100\",\"dst\":\"+14155550101\",\"text\":\"Hello from Plivo\"}'"
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/plivo"
      },
      "sameCompany": [
        "plivo-voice"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "SMS outbound, US long code",
          "unit": "message",
          "usd": 0.0077,
          "note": "US, carrier surcharge extra"
        },
        {
          "item": "SMS outbound, UK",
          "unit": "message",
          "usd": 0.0372,
          "note": "UK, starting rate, varies by network"
        },
        {
          "item": "MMS outbound, US long code",
          "unit": "message",
          "usd": 0.018,
          "note": "US, carrier surcharge extra"
        },
        {
          "item": "WhatsApp marketing, US",
          "unit": "message",
          "usd": 0.0275
        },
        {
          "item": "WhatsApp utility or authentication, US",
          "unit": "message",
          "usd": 0.00374
        }
      ],
      "provenance": {
        "legalEntity": "Plivo Inc.",
        "domain": "plivo.com",
        "domainRegistered": "2011-04-17",
        "endpointOnVendorDomain": true,
        "terms": "https://www.plivo.com/legal/tos/",
        "privacy": "https://www.plivo.com/legal/privacy/",
        "statusPage": "https://status.plivo.com",
        "changelog": "https://www.plivo.com/changelog/",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "Legal entity taken from the site footer."
        ],
        "score": 89
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/plivo.json",
      "live": {
        "slug": "plivo",
        "probe": {
          "target": "https://api.plivo.com/v1",
          "method": "get",
          "lastAt": "2026-10-08T21:12:18.832993105Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 327,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 331,
          "p95ms24h": 403,
          "samples24h": 271,
          "samples30d": 2157,
          "days": [
            {
              "date": "2026-09-30",
              "probes": 35,
              "ok": 35
            },
            {
              "date": "2026-10-01",
              "probes": 276,
              "ok": 276
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 239,
              "ok": 239
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.plivo.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-08T21:06:22.651564352Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "plivo/plivo-node",
            "version": "v4.79.0",
            "released": "2026-07-28",
            "seenAt": "2026-10-08T16:25:45.057976425Z"
          },
          {
            "registry": "npm",
            "name": "plivo",
            "version": "4.79.0",
            "seenAt": "2026-10-08T16:25:44.885061881Z"
          },
          {
            "registry": "pypi",
            "name": "plivo",
            "version": "4.63.0",
            "released": "2026-09-25",
            "seenAt": "2026-10-08T16:25:44.931424459Z"
          }
        ],
        "githubStars": 102,
        "npmWeekly": 53685,
        "pypiWeekly": 77271,
        "securityTxt": {
          "url": "https://plivo.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:53.379676193Z"
        },
        "llmsTxt": {
          "url": "https://www.plivo.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:48.345646617Z"
        },
        "domain": {
          "domain": "plivo.com",
          "registered": "2011-04-17",
          "source": "https://rdap.verisign.com/com/v1/domain/plivo.com",
          "checkedAt": "2026-10-04T13:07:46.742269573Z"
        },
        "pages": [
          {
            "url": "https://www.plivo.com/sms/pricing/us/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:29:46.683488468Z",
            "changedAt": "2026-10-08T18:29:46.683488468Z",
            "fingerprint": "465b0a3363d5"
          }
        ],
        "updatedAt": "2026-10-08T21:12:18.832993105Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Plivo",
        "name": "Vendor"
      },
      {
        "a": "https://sms-voice.us-east-1.amazonaws.com",
        "b": "https://api.plivo.com/v1",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$0.0077 per message",
        "b": "$0.0077 per message",
        "name": "Price for messaging sms"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0",
        "b": "MIT",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-06",
        "b": "2026-09-25",
        "name": "Last release"
      },
      {
        "a": "2026-08-14",
        "b": "2026-04-29",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2026-05-27",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "407k npm/wk",
        "b": "102 stars, 51k npm/wk, 69k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on reliability and payments \u0026 pricing.",
        "question": "Which is better for AI agents, AWS End User Messaging or Plivo API?"
      },
      {
        "answer": "They cost about the same, $0.0077 per message for AWS End User Messaging and $0.0077 per message for Plivo API. These are the vendors' published prices for the job.",
        "question": "Which is cheaper for messaging sms, AWS End User Messaging or Plivo API?"
      },
      {
        "answer": "AWS End User Messaging takes an API key or an OAuth sign-in. Plivo API needs an API key.",
        "question": "Do AWS End User Messaging and Plivo API need an API key?"
      },
      {
        "answer": "Yes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Plivo API at https://api.plivo.com/v1.",
        "question": "Can an agent call AWS End User Messaging and Plivo API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 88 against 59",
          "Agent ergonomics, 71 against 57",
          "Security \u0026 auth, 88 against 45",
          "Maintenance \u0026 community, 85 against 78",
          "Transparency \u0026 trust, 83 against 70"
        ],
        "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": [
          "Reliability, 78 against 73",
          "Payments \u0026 pricing, 40 against 30"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.",
        "slug": "plivo",
        "watchFor": "No OpenAPI spec"
      }
    ],
    "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-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/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-plivo.json",
        "title": "Bandwidth Messaging API + MCP vs Plivo API",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-plivo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bird-vs-plivo.json",
        "title": "Bird API + MCP vs Plivo API",
        "url": "https://www.anchorterminal.com/compare/bird-vs-plivo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clicksend-vs-plivo.json",
        "title": "ClickSend SMS API + MCP vs Plivo API",
        "url": "https://www.anchorterminal.com/compare/clicksend-vs-plivo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infobip-vs-plivo.json",
        "title": "Infobip API + MCP vs Plivo API",
        "url": "https://www.anchorterminal.com/compare/infobip-vs-plivo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plivo-vs-sendblue.json",
        "title": "Plivo API vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-sendblue"
      },
      {
        "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/plivo-vs-telnyx.json",
        "title": "Plivo API vs Telnyx API + MCP",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-telnyx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plivo-vs-twilio.json",
        "title": "Plivo API vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/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-plivo.json",
        "title": "360dialog WhatsApp API + MCP vs Plivo API",
        "url": "https://www.anchorterminal.com/compare/360dialog-vs-plivo"
      },
      {
        "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/plivo-vs-whatsapp-cloud-api.json",
        "title": "Plivo API vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api"
      }
    ],
    "scores": [
      {
        "aws-end-user-messaging": 73,
        "by": 5,
        "edge": "plivo",
        "key": "reliability",
        "name": "Reliability",
        "plivo": 78,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 88,
        "by": 29,
        "edge": "aws-end-user-messaging",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "plivo": 59,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 71,
        "by": 14,
        "edge": "aws-end-user-messaging",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "plivo": 57,
        "weight": 13
      },
      {
        "aws-end-user-messaging": 88,
        "by": 43,
        "edge": "aws-end-user-messaging",
        "key": "security",
        "name": "Security \u0026 auth",
        "plivo": 45,
        "weight": 14
      },
      {
        "aws-end-user-messaging": 30,
        "by": 10,
        "edge": "plivo",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "plivo": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "aws-end-user-messaging": 85,
        "by": 7,
        "edge": "aws-end-user-messaging",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "plivo": 78,
        "weight": 7
      },
      {
        "aws-end-user-messaging": 83,
        "by": 13,
        "edge": "aws-end-user-messaging",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "plivo": 70,
        "weight": 7
      }
    ],
    "summary": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on reliability and 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.",
      "plivo": "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo",
    "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.md",
    "slim": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.min.md"
  },
  "markdown": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on reliability and 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- Plivo API: grade C, 60.3/100, rank #406 of 722. Markdown https://www.anchorterminal.com/tools/plivo.md · JSON https://www.anchorterminal.com/api/v1/tools/plivo.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 59\n- Agent ergonomics, 71 against 57\n- Security \u0026 auth, 88 against 45\n- Maintenance \u0026 community, 85 against 78\n- Transparency \u0026 trust, 83 against 70\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### Plivo API (C)\n\nGood for: Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.\n\nAhead on:\n- Reliability, 78 against 73\n- Payments \u0026 pricing, 40 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No OpenAPI spec\n\n\n## Score by category\n\n| Category | Weight | AWS End User Messaging | Plivo API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 78 | Plivo API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 59 | AWS End User Messaging +29 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 57 | AWS End User Messaging +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 88 | 45 | AWS End User Messaging +43 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Plivo API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 78 | AWS End User Messaging +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 70 | AWS End User Messaging +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.3 · BB** | **60.3 · C** | |\n\n## Facts side by side\n\n| Fact | AWS End User Messaging | Plivo API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Plivo |\n| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://api.plivo.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for messaging sms | $0.0077 per message | $0.0077 per message |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0 | MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-09-25 |\n| Terms last updated | 2026-08-14 | 2026-04-29 |\n| Privacy policy last updated | 2026-05-18 | 2026-05-27 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 407k npm/wk | 102 stars, 51k npm/wk, 69k PyPI/wk |\n| Agent reviews | none | 3.5/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**Plivo API.** US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.\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### Plivo API\n\n1. Put the Auth ID in both the path and the Basic auth header, every request needs both\n2. Stay under 300 API requests per 5 seconds, a 429 carries no Retry-After\n3. Give each agent its own subaccount to isolate credentials and spend\n4. Use the docs MCP to find endpoints, then call the REST API directly to send\n\n## Questions\n\n### Which is better for AI agents, AWS End User Messaging or Plivo API?\n\nAWS End User Messaging scores 74.3 (BB) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on reliability and payments \u0026 pricing.\n\n### Which is cheaper for messaging sms, AWS End User Messaging or Plivo API?\n\nThey cost about the same, $0.0077 per message for AWS End User Messaging and $0.0077 per message for Plivo API. These are the vendors' published prices for the job.\n\n### Do AWS End User Messaging and Plivo API need an API key?\n\nAWS End User Messaging takes an API key or an OAuth sign-in. Plivo API needs an API key.\n\n### Can an agent call AWS End User Messaging and Plivo API without installing anything?\n\nYes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Plivo API at https://api.plivo.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-end-user-messaging\", \"b\": \"plivo\"}`. From a terminal: `anchor compare aws-end-user-messaging plivo`\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/plivo.json\n\n## Other comparisons with AWS End User Messaging or Plivo API\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 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- [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 Plivo API](https://www.anchorterminal.com/compare/bandwidth-vs-plivo.md)\n- [Bird API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bird-vs-plivo.md)\n- [ClickSend SMS API + MCP vs Plivo API](https://www.anchorterminal.com/compare/clicksend-vs-plivo.md)\n- [Infobip API + MCP vs Plivo API](https://www.anchorterminal.com/compare/infobip-vs-plivo.md)\n- [Plivo API vs Sendblue](https://www.anchorterminal.com/compare/plivo-vs-sendblue.md)\n- [Plivo API vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/plivo-vs-sinch.md)\n- [Plivo API vs Telnyx API + MCP](https://www.anchorterminal.com/compare/plivo-vs-telnyx.md)\n- [Plivo API vs Twilio API + MCP](https://www.anchorterminal.com/compare/plivo-vs-twilio.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-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 Plivo API](https://www.anchorterminal.com/compare/360dialog-vs-plivo.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- [Plivo API vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/plivo-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 Plivo API",
        "url": ""
      }
    ],
    "description": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on reliability and payments \u0026 pricing. Both do messaging sms. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "AWS End User Messaging BB 74.3",
      "Plivo API C 60.3",
      "scores"
    ],
    "h1": "AWS End User Messaging vs Plivo API",
    "image": "https://www.anchorterminal.com/assets/og/compare-aws-end-user-messaging-vs-plivo.png",
    "path": "/compare/aws-end-user-messaging-vs-plivo",
    "published": "2026-10-01",
    "section": "tools",
    "title": "AWS End User Messaging vs Plivo API for AI agents, BB 74.3 vs C 60.3",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo"
  },
  "tokens": {
    "markdown": 2500,
    "slim": 630
  },
  "version": 1
}