{ "data": { "a": { "slug": "360dialog", "name": "360dialog WhatsApp API + MCP", "vendor": "360dialog", "vendorUrl": "https://360dialog.com", "kind": "http-api", "category": "messaging", "summary": "WhatsApp Business Solution Provider with a Cloud API proxy for sending and receiving WhatsApp messages, billed per number per month with Meta's fees passed through.", "url": "https://www.anchorterminal.com/tools/360dialog", "markdownUrl": "https://www.anchorterminal.com/tools/360dialog.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/360dialog.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/360dialog.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://waba-v2.360dialog.io", "packages": [], "auth": "mixed", "authNotes": "Messaging API takes a per-channel key in the D360-API-KEY header. The hosted MCP uses OAuth with scopes chosen at consent, so denied scopes hide their tools.", "pricing": "paid", "pricingNotes": "Regular €49 ($59) a number a month, Premium €99 ($119), Higher Throughput €249 ($299), plus Meta's WhatsApp message fees at cost. Marketing messages sent through /messages instead of the Marketing Messages API cost 7 per cent over Meta's rate. A sandbox key allows 200 test messages to your own number (https://docs.360dialog.com/docs/get-started/pricing).", "priceSummary": "$59 / mo", "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": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.360dialog.com/docs", "llmsTxt": "https://docs.360dialog.com/docs/llms.txt", "capabilities": [ "messaging.whatsapp", "messaging.inbound" ], "tags": [ "hosted", "mcp", "llms-txt", "webhooks", "whatsapp", "card-required" ], "graded": true, "anchor": { "graded": true, "score": 52, "grade": "D", "agentReady": false, "rank": 569, "ranked": true, "rankOf": 722, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 8, "payments": 35, "reliability": 83, "schema": 70, "security": 35, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month. No changelog, official SDK or standalone OpenAPI download.", "bestFor": "WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.", "strengths": [ "Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month", "Sandbox with 200 messages and no card", "llms.txt over 297 pages, a .md version of every page, an ?ask= parameter and OpenAPI 3.1 blocks in the reference", "More than 60 error codes, each with a suggested fix", "Status page with no notices from July to 2 October 2026, and Meta outages logged when they happen" ], "weaknesses": [ "No changelog, official SDK or standalone OpenAPI download", "One key per number with no scopes, and a new key revokes the old one at once", "Webhooks support Basic auth only, with no signature", "No uptime SLA on any plan, only support response targets", "The hosted MCP can't send messages and doesn't publish its tool list" ], "agentNotes": [ "Send marketing templates through the Marketing Messages API, /messages adds 7 per cent", "Ask a docs page a question with `?ask=` before reading the whole page", "Pass `fields` and `limit` on GET /message_templates and page with the `after` cursor", "Coordinate key rotation, a new key cuts off every client using the old one", "Answer each webhook with 200 within 5 seconds and process it asynchronously" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52 } ], "editorialScores": { "ergonomics": 53, "maintenance": 8, "payments": 35, "reliability": 83, "schema": 70, "security": 35, "transparency": 35 }, "provenanceScore": 61 }, "connect": { "http": "curl -X POST https://waba-v2.360dialog.io/messages -H \"D360-API-KEY: $D360_API_KEY\" \\\n -H \"Content-Type: application/json\" -d '{\"messaging_product\":\"whatsapp\",\"recipient_type\":\"individual\",\"to\":\"4915112345678\",\"type\":\"text\",\"text\":{\"body\":\"Hello from 360dialog\"}}'", "claudeCode": "claude mcp add --transport http 360dialog https://mcp.360dialog.com/mcp" }, "letme": { "capability": "https://letme.dev/messaging.whatsapp", "tool": "https://letme.dev/360dialog" }, "area": "communication", "unitPrices": [ { "item": "Regular channel", "unit": "month", "usd": 59, "note": "per WhatsApp number, €49, Meta fees extra" }, { "item": "Premium channel", "unit": "month", "usd": 119, "note": "per WhatsApp number, €99, Meta fees extra" }, { "item": "Higher Throughput channel", "unit": "month", "usd": 299, "note": "per WhatsApp number, €249" } ], "provenance": { "legalEntity": "360dialog GmbH", "domain": "360dialog.com", "domainRegistered": "2012-02-22", "endpointOnVendorDomain": false, "terms": "https://hub.360dialog.com/lp/consent/360dialog-terms-of-use", "privacy": "https://360dialog.com/legal/privacy-policy", "statusPage": "https://status.360dialog.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The messaging API runs on 360dialog.io, a separate domain the company also uses. The MCP runs on 360dialog.com." ], "score": 61 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/360dialog.json", "live": { "slug": "360dialog", "probe": { "target": "https://waba-v2.360dialog.io", "method": "get", "lastAt": "2026-10-08T21:12:02.913836054Z", "lastOk": true, "lastStatus": 401, "lastMs": 123, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 127, "p95ms24h": 185, "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.360dialog.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:11.357495365Z" }, "securityTxt": { "url": "https://360dialog.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:55.447523683Z" }, "llmsTxt": { "url": "https://docs.360dialog.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T13:59:59.410778591Z" }, "domain": { "domain": "360dialog.com", "registered": "2012-02-22", "source": "https://rdap.verisign.com/com/v1/domain/360dialog.com", "checkedAt": "2026-10-04T13:06:52.743597557Z" }, "pages": [ { "url": "https://docs.360dialog.com/docs/get-started/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:18:05.598944708Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9b34ec104a49" }, { "url": "https://360dialog.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:14:55.315921817Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ae3552db9baf" }, { "url": "https://hub.360dialog.com/lp/consent/360dialog-terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:20:54.610699882Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "updatedAt": "2026-10-08T21:12:02.913836054Z" } }, "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments \u0026 pricing.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "360dialog", "b": "Amazon Web Services", "name": "Vendor" }, { "a": "https://waba-v2.360dialog.io", "b": "https://sms-voice.us-east-1.amazonaws.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$0.005 per message", "name": "Price for messaging whatsapp" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-06", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-08-14", "name": "Terms last updated" }, { "a": "2026-09-10", "b": "2026-05-18", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "407k npm/wk", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, 360dialog WhatsApp API + MCP or AWS End User Messaging?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do 360dialog WhatsApp API + MCP and AWS End User Messaging need an API key?" }, { "answer": "Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and AWS End User Messaging at https://sms-voice.us-east-1.amazonaws.com.", "question": "Can an agent call 360dialog WhatsApp API + MCP and AWS End User Messaging without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 83 against 73", "Payments \u0026 pricing, 35 against 30" ], "also": null, "goodFor": "WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.", "slug": "360dialog", "watchFor": "No changelog, official SDK or standalone OpenAPI download" }, { "aheadOn": [ "Schema \u0026 documentation, 88 against 70", "Agent ergonomics, 71 against 53", "Security \u0026 auth, 88 against 35", "Maintenance \u0026 community, 85 against 8", "Transparency \u0026 trust, 83 against 48" ], "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" } ], "job": { "capability": "messaging.whatsapp", "name": "Messaging whatsapp" }, "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/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/360dialog-vs-bird.json", "title": "360dialog WhatsApp API + MCP vs Bird API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-bird" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-infobip.json", "title": "360dialog WhatsApp API + MCP vs Infobip API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-infobip" }, { "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/360dialog-vs-sinch.json", "title": "360dialog WhatsApp API + MCP vs Sinch Messaging APIs + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-sinch" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-telnyx.json", "title": "360dialog WhatsApp API + MCP vs Telnyx API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-telnyx" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-twilio.json", "title": "360dialog WhatsApp API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/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/360dialog-vs-whatsapp-cloud-api.json", "title": "360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api" }, { "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-bandwidth.json", "title": "360dialog WhatsApp API + MCP vs Bandwidth Messaging API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-bandwidth" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-clicksend.json", "title": "360dialog WhatsApp API + MCP vs ClickSend SMS API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-clicksend" }, { "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" } ], "scores": [ { "360dialog": 83, "aws-end-user-messaging": 73, "by": 10, "edge": "360dialog", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "360dialog": 70, "aws-end-user-messaging": 88, "by": 18, "edge": "aws-end-user-messaging", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "360dialog": 53, "aws-end-user-messaging": 71, "by": 18, "edge": "aws-end-user-messaging", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "360dialog": 35, "aws-end-user-messaging": 88, "by": 53, "edge": "aws-end-user-messaging", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "360dialog": 35, "aws-end-user-messaging": 30, "by": 5, "edge": "360dialog", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "360dialog": 8, "aws-end-user-messaging": 85, "by": 77, "edge": "aws-end-user-messaging", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "360dialog": 48, "aws-end-user-messaging": 83, "by": 35, "edge": "aws-end-user-messaging", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments \u0026 pricing. Both do messaging whatsapp.", "verdicts": { "360dialog": "Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month. No changelog, official SDK or standalone OpenAPI download.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging", "json": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.md", "slim": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.min.md" }, "markdown": "AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments \u0026 pricing. Both do messaging whatsapp.\n\n- 360dialog WhatsApp API + MCP: grade D, 52/100, rank #569 of 722. Markdown https://www.anchorterminal.com/tools/360dialog.md · JSON https://www.anchorterminal.com/api/v1/tools/360dialog.json\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\n## Which one, for what\n\n### 360dialog WhatsApp API + MCP (D)\n\nGood for: WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.\n\nAhead on:\n- Reliability, 83 against 73\n- Payments \u0026 pricing, 35 against 30\n\nWatch for: No changelog, official SDK or standalone OpenAPI download\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 70\n- Agent ergonomics, 71 against 53\n- Security \u0026 auth, 88 against 35\n- Maintenance \u0026 community, 85 against 8\n- Transparency \u0026 trust, 83 against 48\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\n## Score by category\n\n| Category | Weight | 360dialog WhatsApp API + MCP | AWS End User Messaging | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 83 | 73 | 360dialog WhatsApp API + MCP +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 88 | AWS End User Messaging +18 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 71 | AWS End User Messaging +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 35 | 88 | AWS End User Messaging +53 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 30 | 360dialog WhatsApp API + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 8 | 85 | AWS End User Messaging +77 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 83 | AWS End User Messaging +35 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52 · D** | **74.3 · BB** | |\n\n## Facts side by side\n\n| Fact | 360dialog WhatsApp API + MCP | AWS End User Messaging |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 360dialog | Amazon Web Services |\n| Hosted endpoint | `https://waba-v2.360dialog.io` | `https://sms-voice.us-east-1.amazonaws.com` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Pay per use |\n| Price for messaging whatsapp | not published | $0.005 per message |\n| x402 | no | no |\n| Licence | none | Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-06 |\n| Terms last updated | couldn't be read | 2026-08-14 |\n| Privacy policy last updated | 2026-09-10 | 2026-05-18 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | none | 407k npm/wk |\n| Agent reviews | 3/5 (2) | none |\n\n## Verdicts\n\n**360dialog WhatsApp API + MCP.** Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month. No changelog, official SDK or standalone OpenAPI download.\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## Before you call either\n\n### 360dialog WhatsApp API + MCP\n\n1. Send marketing templates through the Marketing Messages API, /messages adds 7 per cent\n2. Ask a docs page a question with `?ask=` before reading the whole page\n3. Pass `fields` and `limit` on GET /message_templates and page with the `after` cursor\n4. Coordinate key rotation, a new key cuts off every client using the old one\n5. Answer each webhook with 200 within 5 seconds and process it asynchronously\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## Questions\n\n### Which is better for AI agents, 360dialog WhatsApp API + MCP or AWS End User Messaging?\n\nAWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments \u0026 pricing.\n\n### Do 360dialog WhatsApp API + MCP and AWS End User Messaging need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call 360dialog WhatsApp API + MCP and AWS End User Messaging without installing anything?\n\nYes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and AWS End User Messaging at https://sms-voice.us-east-1.amazonaws.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.json, and with the fewest tokens: https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"360dialog\", \"b\": \"aws-end-user-messaging\"}`. From a terminal: `anchor compare 360dialog aws-end-user-messaging`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/360dialog.json and https://www.anchorterminal.com/api/v1/tools/aws-end-user-messaging.json\n\n## Other comparisons with 360dialog WhatsApp API + MCP or AWS End User Messaging\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- [AWS End User Messaging vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Bird API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-bird.md)\n- [360dialog WhatsApp API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-infobip.md)\n- [360dialog WhatsApp API + MCP vs Plivo API](https://www.anchorterminal.com/compare/360dialog-vs-plivo.md)\n- [360dialog WhatsApp API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/360dialog-vs-sinch.md)\n- [360dialog WhatsApp API + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-telnyx.md)\n- [360dialog WhatsApp API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-twilio.md)\n- [360dialog WhatsApp API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api.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 Bandwidth Messaging API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-bandwidth.md)\n- [360dialog WhatsApp API + MCP vs ClickSend SMS API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-clicksend.md)\n- [360dialog WhatsApp API + MCP vs Sendblue](https://www.anchorterminal.com/compare/360dialog-vs-sendblue.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": "360dialog WhatsApp API + MCP vs AWS End User Messaging", "url": "" } ], "description": "AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments \u0026 pricing. Both do messaging whatsapp. Category scores, facts, verdicts…", "facts": [ "360dialog WhatsApp API + MCP D 52", "AWS End User Messaging BB 74.3", "scores" ], "h1": "360dialog WhatsApp API + MCP vs AWS End User Messaging", "image": "https://www.anchorterminal.com/assets/og/compare-360dialog-vs-aws-end-user-messaging.png", "path": "/compare/360dialog-vs-aws-end-user-messaging", "published": "2026-10-01", "section": "tools", "title": "360dialog WhatsApp API + MCP vs AWS End User Messaging for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/360dialog-vs-aws-end-user-messaging" }, "tokens": { "markdown": 2600, "slim": 780 }, "version": 1 }