{ "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 Sendblue's 61.7 (C), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics and payments \u0026 pricing.", "b": { "slug": "sendblue", "name": "Sendblue", "vendor": "Round One, Inc.", "vendorUrl": "https://www.sendblue.com", "kind": "http-api", "category": "messaging", "summary": "Sendblue is a hosted API from Round One, Inc. for sending and receiving iMessage, RCS, SMS and MMS from dedicated or shared phone numbers. Agents use a REST API, TypeScript and Python SDKs, a CLI and an MCP server.", "url": "https://www.anchorterminal.com/tools/sendblue", "markdownUrl": "https://www.anchorterminal.com/tools/sendblue.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sendblue.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sendblue.json", "repo": "https://github.com/sendblue-api/sendblue-ts", "license": "Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.sendblue.com", "packages": [ { "registry": "npm", "name": "sendblue" }, { "registry": "pypi", "name": "sendblue" }, { "registry": "npm", "name": "sendblue-api-mcp" }, { "registry": "npm", "name": "@sendblue/cli" } ], "auth": "api-key", "authNotes": "Every request carries the account's key pair in the `sb-api-key-id` and `sb-api-secret-key` headers, and requests from a browser are refused. The keys come from the dashboard or from `sendblue show-keys` after the CLI creates the account, which needs a person to text a one-time code or enter an email code. `POST /v3/auth/tokens` mints a temporary bearer token, account-wide or limited to named phone numbers, valid for 900 seconds by default and revocable. The MCP server reads `SENDBLUE_API_API_KEY` and `SENDBLUE_API_API_SECRET` from the environment. Agency subaccounts with their own keys need approval from support.", "pricing": "freemium", "pricingNotes": "Flat price per line with no per-message fee. The Free Sandbox is $0 with no card, on a shared number with up to 10 verified contacts. The AI Agent plan is $100 a month per dedicated line and is inbound-first. Proactive outbound messaging is on the Enterprise or Blue Ocean plan, priced through sales. The terms add 3 per cent for card payments and $60 per line to port a number out (https://www.sendblue.com/pricing, checked 2026-10-08).", "priceSummary": "$100 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, either `llms.txt`, the pricing page or the terms (checked 2026-10-08).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": null, "npmWeekly": 249505, "pypiWeekly": 39912, "asOf": "2026-10-08" }, "docsUrl": "https://docs.sendblue.com", "llmsTxt": "https://docs.sendblue.com/llms.txt", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.rcs", "messaging.inbound", "messaging.verify" ], "tags": [ "hosted", "imessage", "sms", "rcs", "mcp", "cli", "llms-txt", "typescript", "python", "webhooks", "no-card", "status-page" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 61.7, "grade": "C", "agentReady": false, "rank": 358, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 72, "payments": 40, "reliability": 71, "schema": 66, "security": 46, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.", "bestFor": "An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.", "strengths": [ "One request to `/api/send-message` sends iMessage and can fall back to RCS or SMS, with no per-message fee on any plan", "The CLI creates a free account, a shared line and API keys from a terminal, with no card, once a person texts a one-time code", "Temporary bearer tokens from `/v3/auth/tokens` can be limited to named phone numbers, expire after 900 seconds by default and can be revoked", "Every docs page has a Markdown twin at `/index.md`, and `llms.txt` summarises each page with its limits and conditions", "Rate limits are published with numbers for each plan, and declined sends return an `error_key` an agent can branch on" ], "weaknesses": [ "Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first", "No OpenAPI file was found at any public address, although the SDKs and the reference are generated from one", "The docs install `sendblue-api-mcp`, last published on 5 August 2025 with 18 tools. The API now has 54 configured endpoints", "`/api/send-message` takes no idempotency key, and the SDKs retry 429 and 5xx responses twice by default", "No public DPA, sub-processor list, retention period, deprecation policy or security.txt was found" ], "agentNotes": [ "Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails", "On the free plan a recipient must text the Sendblue number once before any message to them is accepted", "Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six", "Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting", "Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied", "Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.7 } ], "editorialScores": { "ergonomics": 76, "maintenance": 72, "payments": 40, "reliability": 71, "schema": 66, "security": 46, "transparency": 29 }, "provenanceScore": 86 }, "connect": { "install": "npm install sendblue", "http": "curl -X POST https://api.sendblue.com/api/send-message \\\n -H \"sb-api-key-id: $SENDBLUE_API_KEY_ID\" -H \"sb-api-secret-key: $SENDBLUE_API_KEY_SECRET\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"number\":\"+19998887777\",\"from_number\":\"+18887776666\",\"content\":\"Hello from Sendblue!\"}'", "claudeCode": "claude mcp add sendblue_api --env SENDBLUE_API_API_KEY=your-api-key --env SENDBLUE_API_API_SECRET=your-api-secret -- npx -y sendblue-api-mcp --client=claude-code --tools=all", "config": { "mcpServers": { "sendblue_api": { "args": [ "-y", "sendblue-api-mcp", "--tools=all" ], "command": "npx", "env": { "SENDBLUE_API_API_KEY": "your-api-key", "SENDBLUE_API_API_SECRET": "your-api-secret" } } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/sendblue" }, "area": "communication", "unitPrices": [ { "item": "AI Agent plan, dedicated line", "unit": "month", "usd": 100, "note": "Per line, inbound-first, no per-message fee. Outbound plans are priced through sales" } ], "provenance": { "legalEntity": "Round One, Inc.", "domain": "sendblue.com", "domainRegistered": "2011-06-25", "endpointOnVendorDomain": true, "terms": "https://www.sendblue.com/terms-of-service", "privacy": "https://www.sendblue.com/privacy-policy", "statusPage": "https://status.sendblue.com", "changelog": "https://github.com/sendblue-api/sendblue-ts/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms of service (effective 19 March 2025) and the privacy policy (effective 1 May 2024) both name Round One, Inc. as Sendblue. The site footer gives 344 West End Avenue, New York NY 10024.", "The terms cover registering for and using the services, so they govern API use. The privacy policy covers the website and the services and says Sendblue is a processor for its business customers.", "The API answers at api.sendblue.com, and the SDKs default to api.sendblue.co, a second domain the vendor uses.", "`/.well-known/security.txt` returns 404 on www.sendblue.com, docs.sendblue.com and api.sendblue.com.", "There is no API changelog in the docs. The changelog link is the TypeScript SDK's, whose recent entries mostly read as regenerated clients.", "RDAP for sendblue.com gives a registration date of 2011-06-25." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sendblue.json", "live": { "slug": "sendblue", "probe": { "target": "https://api.sendblue.com", "method": "get", "lastAt": "2026-10-08T21:12:21.131570615Z", "lastOk": true, "lastStatus": 200, "lastMs": 731, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 772, "p95ms24h": 921, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.sendblue.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:09.808226694Z" }, "updatedAt": "2026-10-08T21:12:21.131570615Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Round One, Inc.", "name": "Vendor" }, { "a": "https://sms-voice.us-east-1.amazonaws.com", "b": "https://api.sendblue.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "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": "Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT", "name": "Licence" }, { "a": "none", "b": "18", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-10-07", "name": "Last release" }, { "a": "2026-08-14", "b": "2025-03-19", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2024-05-01", "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": "250k npm/wk, 40k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sendblue's 61.7 (C), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, AWS End User Messaging or Sendblue?" }, { "answer": "AWS End User Messaging takes an API key or an OAuth sign-in. Sendblue needs an API key.", "question": "Do AWS End User Messaging and Sendblue need an API key?" }, { "answer": "Yes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Sendblue at https://api.sendblue.com.", "question": "Can an agent call AWS End User Messaging and Sendblue without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 88 against 66", "Security \u0026 auth, 88 against 46", "Maintenance \u0026 community, 85 against 72", "Transparency \u0026 trust, 83 against 58" ], "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": [ "Agent ergonomics, 76 against 71", "Payments \u0026 pricing, 40 against 30" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.", "slug": "sendblue", "watchFor": "Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first" } ], "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-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-sendblue.json", "title": "Bandwidth Messaging API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-sendblue.json", "title": "Bird API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/bird-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-sendblue.json", "title": "ClickSend SMS API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/clicksend-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-sendblue.json", "title": "Infobip API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/infobip-vs-sendblue" }, { "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/sendblue-vs-sinch.json", "title": "Sendblue vs Sinch Messaging APIs + MCP", "url": "https://www.anchorterminal.com/compare/sendblue-vs-sinch" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-telnyx.json", "title": "Sendblue vs Telnyx API + MCP", "url": "https://www.anchorterminal.com/compare/sendblue-vs-telnyx" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-twilio.json", "title": "Sendblue vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/sendblue-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/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/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/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/360dialog-vs-sendblue.json", "title": "360dialog WhatsApp API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/360dialog-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api.json", "title": "Sendblue vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api" } ], "scores": [ { "aws-end-user-messaging": 73, "by": 2, "edge": "aws-end-user-messaging", "key": "reliability", "name": "Reliability", "sendblue": 71, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aws-end-user-messaging": 88, "by": 22, "edge": "aws-end-user-messaging", "key": "schema", "name": "Schema \u0026 documentation", "sendblue": 66, "weight": 13 }, { "aws-end-user-messaging": 71, "by": 5, "edge": "sendblue", "key": "ergonomics", "name": "Agent ergonomics", "sendblue": 76, "weight": 13 }, { "aws-end-user-messaging": 88, "by": 42, "edge": "aws-end-user-messaging", "key": "security", "name": "Security \u0026 auth", "sendblue": 46, "weight": 14 }, { "aws-end-user-messaging": 30, "by": 10, "edge": "sendblue", "key": "payments", "name": "Payments \u0026 pricing", "sendblue": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aws-end-user-messaging": 85, "by": 13, "edge": "aws-end-user-messaging", "key": "maintenance", "name": "Maintenance \u0026 community", "sendblue": 72, "weight": 7 }, { "aws-end-user-messaging": 83, "by": 25, "edge": "aws-end-user-messaging", "key": "transparency", "name": "Transparency \u0026 trust", "sendblue": 58, "weight": 7 } ], "summary": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sendblue's 61.7 (C), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics 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.", "sendblue": "Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue", "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.md", "slim": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.min.md" }, "markdown": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sendblue's 61.7 (C), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics 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- Sendblue: grade C, 61.7/100, rank #358 of 722. Markdown https://www.anchorterminal.com/tools/sendblue.md · JSON https://www.anchorterminal.com/api/v1/tools/sendblue.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 66\n- Security \u0026 auth, 88 against 46\n- Maintenance \u0026 community, 85 against 72\n- Transparency \u0026 trust, 83 against 58\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### Sendblue (C)\n\nGood for: An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.\n\nAhead on:\n- Agent ergonomics, 76 against 71\n- Payments \u0026 pricing, 40 against 30\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first\n\n\n## Score by category\n\n| Category | Weight | AWS End User Messaging | Sendblue | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 71 | AWS End User Messaging +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 66 | AWS End User Messaging +22 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 76 | Sendblue +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 88 | 46 | AWS End User Messaging +42 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Sendblue +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 72 | AWS End User Messaging +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 58 | AWS End User Messaging +25 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.3 · BB** | **61.7 · C** | |\n\n## Facts side by side\n\n| Fact | AWS End User Messaging | Sendblue |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Round One, Inc. |\n| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://api.sendblue.com` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Freemium |\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 | Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT |\n| Tools exposed | none | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-10-07 |\n| Terms last updated | 2026-08-14 | 2025-03-19 |\n| Privacy policy last updated | 2026-05-18 | 2024-05-01 |\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 | 250k npm/wk, 40k PyPI/wk |\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**Sendblue.** Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.\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### Sendblue\n\n1. Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails\n2. On the free plan a recipient must text the Sendblue number once before any message to them is accepted\n3. Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six\n4. Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting\n5. Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied\n6. Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context\n\n## Questions\n\n### Which is better for AI agents, AWS End User Messaging or Sendblue?\n\nAWS End User Messaging scores 74.3 (BB) on agent readiness against Sendblue's 61.7 (C), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics and payments \u0026 pricing.\n\n### Do AWS End User Messaging and Sendblue need an API key?\n\nAWS End User Messaging takes an API key or an OAuth sign-in. Sendblue needs an API key.\n\n### Can an agent call AWS End User Messaging and Sendblue without installing anything?\n\nYes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Sendblue at https://api.sendblue.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-end-user-messaging\", \"b\": \"sendblue\"}`. From a terminal: `anchor compare aws-end-user-messaging sendblue`\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/sendblue.json\n\n## Other comparisons with AWS End User Messaging or Sendblue\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 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 Sendblue](https://www.anchorterminal.com/compare/bandwidth-vs-sendblue.md)\n- [Bird API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bird-vs-sendblue.md)\n- [ClickSend SMS API + MCP vs Sendblue](https://www.anchorterminal.com/compare/clicksend-vs-sendblue.md)\n- [Infobip API + MCP vs Sendblue](https://www.anchorterminal.com/compare/infobip-vs-sendblue.md)\n- [Plivo API vs Sendblue](https://www.anchorterminal.com/compare/plivo-vs-sendblue.md)\n- [Sendblue vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/sendblue-vs-sinch.md)\n- [Sendblue vs Telnyx API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-telnyx.md)\n- [Sendblue vs Twilio API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-twilio.md)\n- [Sendblue vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sendblue-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- [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- [360dialog WhatsApp API + MCP vs Sendblue](https://www.anchorterminal.com/compare/360dialog-vs-sendblue.md)\n- [Sendblue vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sendblue-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 Sendblue", "url": "" } ], "description": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Sendblue's 61.7 (C), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics 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", "Sendblue C 61.7", "scores" ], "h1": "AWS End User Messaging vs Sendblue", "image": "https://www.anchorterminal.com/assets/og/compare-aws-end-user-messaging-vs-sendblue.png", "path": "/compare/aws-end-user-messaging-vs-sendblue", "published": "2026-10-01", "section": "tools", "title": "AWS End User Messaging vs Sendblue for AI agents, BB 74.3 vs C 61.7", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue" }, "tokens": { "markdown": 2700, "slim": 730 }, "version": 1 }