{ "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": 73, "ranked": true, "rankOf": 950, "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-bedrock-customization", "agentcore-code-interpreter", "amazon-textract", "amazon-sns", "amazon-s3", "amazon-eventbridge" ], "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-10T02:54:47.236818701Z", "lastOk": true, "lastStatus": 404, "lastMs": 253, "authRequired": false, "uptime24h": 99.6, "uptime30d": 99.7, "p50ms24h": 258, "p95ms24h": 325, "samples24h": 249, "samples30d": 330, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 249 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-pinpoint-sms-voice-v2", "version": "3.1148.0", "seenAt": "2026-10-09T16:41:10.199117735Z" }, { "registry": "npm", "name": "@aws-sdk/client-socialmessaging", "version": "3.1148.0", "seenAt": "2026-10-09T16:41:11.156236627Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.110", "released": "2026-10-08", "seenAt": "2026-10-09T16:41:12.424527937Z" } ], "githubStars": 229, "npmWeekly": 341013, "pypiWeekly": 577963463, "securityTxt": { "url": "https://amazonaws.com/.well-known/security.txt", "state": "expired", "expires": "2026-09-24T16:25:03.000Z", "checkedAt": "2026-10-09T15:40:31.547092582Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/sms-voice/latest/userguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:31.866988243Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/sms-voice/latest/userguide/doc-history.html", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:36:50.357099758Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "73a24c837402" }, { "url": "https://aws.amazon.com/end-user-messaging/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:32:59.995433602Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0f919d86f472" } ], "updatedAt": "2026-10-10T02:54:47.236818701Z" } }, "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Telegram Bot API's 43 (E), and leads in 6 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing.", "b": { "slug": "telegram-bot", "name": "Telegram Bot API", "vendor": "Telegram Messenger Inc.", "vendorUrl": "https://telegram.org", "kind": "http-api", "category": "messaging", "summary": "The Telegram Bot API is Telegram's HTTP interface for bot accounts. A bot sends and edits messages, media and polls, manages chats and takes payments, and receives user messages by long polling or webhook, with a token issued by @BotFather.", "url": "https://www.anchorterminal.com/tools/telegram-bot", "markdownUrl": "https://www.anchorterminal.com/tools/telegram-bot.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/telegram-bot.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/telegram-bot.json", "repo": "https://github.com/tdlib/telegram-bot-api", "license": "Proprietary hosted service under the Telegram Bot Platform Developer Terms of Service. The Bot API server source in tdlib/telegram-bot-api is BSL-1.0", "transports": [ "http" ], "remoteUrl": "https://api.telegram.org", "packages": [], "auth": "api-key", "authNotes": "Self-serve. A person with a Telegram account sends `/newbot` to @BotFather and receives one token per bot. The token goes in the URL path of every request, as `https://api.telegram.org/bot\u003ctoken\u003e/METHOD_NAME`. It has no scopes or expiry and gives full control of the bot. `/token` in @BotFather generates a new one. No OAuth, app review or sales approval applies.", "pricing": "free", "pricingNotes": "Free, with no card or contract. The one fee found is for paid broadcasts, 0.1 Telegram Stars per message sent above 30 a second, open to bots with at least 100,000 Stars and 100,000 monthly active users. A separate test environment exists for bots (checked 2026-10-09).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Bot API reference, the FAQ, the developer terms or the server source (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 4478, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://core.telegram.org/bots/api", "capabilities": [ "messaging.inbound" ], "tags": [ "hosted", "free", "api-key", "webhooks", "long-polling", "telegram", "chat", "open-source-server", "bug-bounty", "self-serve" ], "lastRelease": "2026-08-24", "graded": true, "anchor": { "graded": true, "score": 43, "grade": "E", "agentReady": false, "rank": 885, "ranked": true, "rankOf": 950, "categoryRank": 14, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 48, "maintenance": 38, "payments": 40, "reliability": 40, "schema": 44, "security": 35, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "Telegram's first-party bot interface is free, needs no card and documents 185 methods on one page with a dated changelog and numeric send limits. No OpenAPI document, status page, SLA or idempotency key was found, one token controls the whole bot and travels in the URL, and a person must create the bot in a chat with @BotFather.", "bestFor": "An agent that talks to people who use Telegram, with free sends and long polling that needs no public server.", "strengths": [ "Free to use with no card. Limits are published as numbers, about one message a second per chat, 20 a minute in a group and about 30 a second in bulk", "Flood errors return HTTP 429 with `retry_after` in the response `parameters`, and the open-source server sets a `Retry-After` header", "Inbound messages arrive by `getUpdates` long polling with no public server, or by webhook with a `secret_token` echoed in `X-Telegram-Bot-Api-Secret-Token`", "The Bot API server is open source under BSL-1.0 in tdlib/telegram-bot-api, at version 10.3, and can be self-hosted for larger files", "A dated changelog covers every version, and the server source still accepts `receiver_user_id` and `correct_option_id` after the changelog said they were replaced" ], "weaknesses": [ "No OpenAPI document, llms.txt or official SDK was found. The contract is one HTML reference page of about 860 KB", "One token gives full control of the bot, sits in the URL path of every request, and has no scopes or read-only form", "No status page, SLA or incident history was found, and the developer terms disclaim uptime and allow changes without notice", "No idempotency key exists for sends, and `error_code` contents are described as subject to change with no published error catalogue", "A person with a Telegram account must create the bot in a chat with @BotFather, and a bot cannot message a user who has not started it", "Developer terms section 4.3 prohibits collecting data for large datasets, machine learning models and AI products. Recorded as a fact, and it matters before any probe is run" ], "agentNotes": [ "Send `POST https://api.telegram.org/bot\u003ctoken\u003e/sendMessage` with `chat_id` and `text`. Keep the token out of logs, because it is part of the URL.", "On HTTP 429 wait the `parameters.retry_after` seconds before retrying. Stay under one message a second per chat and 20 a minute per group.", "Call `getUpdates` with `offset` set to the last `update_id` plus one, or the same updates return. Updates are kept for at most 24 hours.", "A retried send can post twice, as there is no idempotency key. Record the returned `message_id` before retrying after a timeout.", "In groups the bot sees only commands and replies unless privacy mode is disabled in @BotFather or the bot is an admin." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43 } ], "editorialScores": { "ergonomics": 48, "maintenance": 38, "payments": 40, "reliability": 40, "schema": 44, "security": 35, "transparency": 53 }, "provenanceScore": 74 }, "connect": { "http": "curl https://api.telegram.org/bot\u003ctoken\u003e/getMe" }, "letme": { "capability": "https://letme.dev/messaging.inbound", "tool": "https://letme.dev/telegram-bot" }, "area": "communication", "provenance": { "legalEntity": "Telegram Messenger Inc.", "domain": "telegram.org", "domainRegistered": "2003-12-15", "endpointOnVendorDomain": true, "terms": "https://telegram.org/tos/bot-developers", "privacy": "https://telegram.org/privacy", "statusPage": "", "changelog": "https://core.telegram.org/bots/api-changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Bot Platform Developer Terms of Service name Telegram Messenger Inc. as the contracting party and incorporate the Telegram Terms of Service and Privacy Policy. The page carries no date.", "The privacy policy names Telegram Messenger Inc. as controller, Telegram Group Inc and Telegraph Inc. in the British Virgin Islands and Telegram FZ-LLC in Dubai as group recipients, and EDPO as EEA representative. Its last listed change is 29 September 2024.", "The API answers at api.telegram.org and the docs at core.telegram.org, both telegram.org subdomains.", "telegram.org/.well-known/security.txt returns 404, and core.telegram.org/.well-known/security.txt and telegram.org/security.txt return ordinary web pages. The bug bounty page at core.telegram.org/bug-bounty takes reports at security@telegram.org.", "Neither core.telegram.org nor telegram.org serves a robots.txt (404 on both).", "No status page was found.", "RDAP for telegram.org gives a registration date of 2003-12-15." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/telegram-bot.json", "live": { "slug": "telegram-bot", "probe": { "target": "https://api.telegram.org", "method": "get", "lastAt": "2026-10-10T02:55:12.653741105Z", "lastOk": true, "lastStatus": 200, "lastMs": 389, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 114, "p95ms24h": 503, "samples24h": 115, "samples30d": 115, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "githubStars": 4480, "pages": [ { "url": "https://telegram.org/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:46:33.627004977Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "797939d5eedb" }, { "url": "https://telegram.org/tos/bot-developers", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:46:35.690260958Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e5a72833c44e" } ], "updatedAt": "2026-10-10T02:55:12.653741105Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Telegram Messenger Inc.", "name": "Vendor" }, { "a": "https://sms-voice.us-east-1.amazonaws.com", "b": "https://api.telegram.org", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0", "b": "Proprietary hosted service under the Telegram Bot Platform Developer Terms of Service. The Bot API server source in tdlib/telegram-bot-api is BSL-1.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-08-24", "name": "Last release" }, { "a": "2026-08-14", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2024-06-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": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "407k npm/wk", "b": "4.5k stars", "name": "Popularity" } ], "faq": [ { "answer": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Telegram Bot API's 43 (E), and leads in 6 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing.", "question": "Which is better for AI agents, AWS End User Messaging or Telegram Bot API?" }, { "answer": "AWS End User Messaging takes an API key or an OAuth sign-in. Telegram Bot API needs an API key.", "question": "Do AWS End User Messaging and Telegram Bot 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 Telegram Bot API at https://api.telegram.org.", "question": "Can an agent call AWS End User Messaging and Telegram Bot API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 73 against 40", "Schema \u0026 documentation, 88 against 44", "Agent ergonomics, 71 against 48", "Security \u0026 auth, 88 against 35", "Maintenance \u0026 community, 85 against 38", "Transparency \u0026 trust, 83 against 64" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices.", "slug": "aws-end-user-messaging", "watchFor": "Sandbox limits new accounts to $1 of SMS a month and ten verified numbers until a support case per Region is approved" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "also": null, "goodFor": "An agent that talks to people who use Telegram, with free sends and long polling that needs no public server.", "slug": "telegram-bot", "watchFor": "No OpenAPI document, llms.txt or official SDK was found. The contract is one HTML reference page of about 860 KB" } ], "job": { "capability": "messaging.inbound", "name": "Inbound messaging" }, "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-telegram-bot.json", "title": "360dialog WhatsApp API + MCP vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.json", "title": "Bandwidth Messaging API + MCP vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-telegram-bot.json", "title": "Bird API + MCP vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/bird-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-telegram-bot.json", "title": "ClickSend SMS API + MCP vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/clicksend-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.json", "title": "Infobip API + MCP vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/infobip-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-telegram-bot.json", "title": "Plivo API vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/plivo-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.json", "title": "Sendblue vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/sinch-vs-telegram-bot.json", "title": "Sinch Messaging APIs + MCP vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/sinch-vs-telegram-bot" }, { "json": "https://www.anchorterminal.com/compare/telegram-bot-vs-telnyx.json", "title": "Telegram Bot API vs Telnyx API + MCP", "url": "https://www.anchorterminal.com/compare/telegram-bot-vs-telnyx" }, { "json": "https://www.anchorterminal.com/compare/telegram-bot-vs-twilio.json", "title": "Telegram Bot API vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/telegram-bot-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/telegram-bot-vs-vonage.json", "title": "Telegram Bot API vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/telegram-bot-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/telegram-bot-vs-whatsapp-cloud-api.json", "title": "Telegram Bot API vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/telegram-bot-vs-whatsapp-cloud-api" }, { "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" } ], "scores": [ { "aws-end-user-messaging": 73, "by": 33, "edge": "aws-end-user-messaging", "key": "reliability", "name": "Reliability", "telegram-bot": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aws-end-user-messaging": 88, "by": 44, "edge": "aws-end-user-messaging", "key": "schema", "name": "Schema \u0026 documentation", "telegram-bot": 44, "weight": 13 }, { "aws-end-user-messaging": 71, "by": 23, "edge": "aws-end-user-messaging", "key": "ergonomics", "name": "Agent ergonomics", "telegram-bot": 48, "weight": 13 }, { "aws-end-user-messaging": 88, "by": 53, "edge": "aws-end-user-messaging", "key": "security", "name": "Security \u0026 auth", "telegram-bot": 35, "weight": 14 }, { "aws-end-user-messaging": 30, "by": 10, "edge": "telegram-bot", "key": "payments", "name": "Payments \u0026 pricing", "telegram-bot": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aws-end-user-messaging": 85, "by": 47, "edge": "aws-end-user-messaging", "key": "maintenance", "name": "Maintenance \u0026 community", "telegram-bot": 38, "weight": 7 }, { "aws-end-user-messaging": 83, "by": 19, "edge": "aws-end-user-messaging", "key": "transparency", "name": "Transparency \u0026 trust", "telegram-bot": 64, "weight": 7 } ], "summary": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Telegram Bot API's 43 (E), and leads in 6 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing. Both do inbound messaging.", "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.", "telegram-bot": "Telegram's first-party bot interface is free, needs no card and documents 185 methods on one page with a dated changelog and numeric send limits. No OpenAPI document, status page, SLA or idempotency key was found, one token controls the whole bot and travels in the URL, and a person must create the bot in a chat with @BotFather." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot", "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.md", "slim": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.min.md" }, "markdown": "AWS End User Messaging scores 74.3 (BB) on agent readiness against Telegram Bot API's 43 (E), and leads in 6 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing. Both do inbound messaging.\n\n- AWS End User Messaging: grade BB, 74.3/100, rank #73 of 950. 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- Telegram Bot API: grade E, 43/100, rank #885 of 950. Markdown https://www.anchorterminal.com/tools/telegram-bot.md · JSON https://www.anchorterminal.com/api/v1/tools/telegram-bot.json\n- Best SMS, WhatsApp and messaging APIs for AI agents: https://www.anchorterminal.com/best/messaging/index.md\n- All 91 messaging comparisons: https://www.anchorterminal.com/compare/messaging/index.md\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- Reliability, 73 against 40\n- Schema \u0026 documentation, 88 against 44\n- Agent ergonomics, 71 against 48\n- Security \u0026 auth, 88 against 35\n- Maintenance \u0026 community, 85 against 38\n- Transparency \u0026 trust, 83 against 64\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### Telegram Bot API (E)\n\nGood for: An agent that talks to people who use Telegram, with free sends and long polling that needs no public server.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: No OpenAPI document, llms.txt or official SDK was found. The contract is one HTML reference page of about 860 KB\n\n\n## Score by category\n\n| Category | Weight | AWS End User Messaging | Telegram Bot API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 40 | AWS End User Messaging +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 44 | AWS End User Messaging +44 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 48 | AWS End User Messaging +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 88 | 35 | AWS End User Messaging +53 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Telegram Bot API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 38 | AWS End User Messaging +47 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 64 | AWS End User Messaging +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.3 · BB** | **43 · E** | |\n\n## Facts side by side\n\n| Fact | AWS End User Messaging | Telegram Bot API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Telegram Messenger Inc. |\n| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://api.telegram.org` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0 | Proprietary hosted service under the Telegram Bot Platform Developer Terms of Service. The Bot API server source in tdlib/telegram-bot-api is BSL-1.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-06 | 2026-08-24 |\n| Terms last updated | 2026-08-14 | no date given |\n| Privacy policy last updated | 2026-05-18 | 2024-06-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 | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 407k npm/wk | 4.5k stars |\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**Telegram Bot API.** Telegram's first-party bot interface is free, needs no card and documents 185 methods on one page with a dated changelog and numeric send limits. No OpenAPI document, status page, SLA or idempotency key was found, one token controls the whole bot and travels in the URL, and a person must create the bot in a chat with @BotFather.\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### Telegram Bot API\n\n1. Send `POST https://api.telegram.org/bot\u003ctoken\u003e/sendMessage` with `chat_id` and `text`. Keep the token out of logs, because it is part of the URL.\n2. On HTTP 429 wait the `parameters.retry_after` seconds before retrying. Stay under one message a second per chat and 20 a minute per group.\n3. Call `getUpdates` with `offset` set to the last `update_id` plus one, or the same updates return. Updates are kept for at most 24 hours.\n4. A retried send can post twice, as there is no idempotency key. Record the returned `message_id` before retrying after a timeout.\n5. In groups the bot sees only commands and replies unless privacy mode is disabled in @BotFather or the bot is an admin.\n\n## Questions\n\n### Which is better for AI agents, AWS End User Messaging or Telegram Bot API?\n\nAWS End User Messaging scores 74.3 (BB) on agent readiness against Telegram Bot API's 43 (E), and leads in 6 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing.\n\n### Do AWS End User Messaging and Telegram Bot API need an API key?\n\nAWS End User Messaging takes an API key or an OAuth sign-in. Telegram Bot API needs an API key.\n\n### Can an agent call AWS End User Messaging and Telegram Bot API without installing anything?\n\nYes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Telegram Bot API at https://api.telegram.org.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-end-user-messaging\", \"b\": \"telegram-bot\"}`. From a terminal: `anchor compare aws-end-user-messaging telegram-bot`\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/telegram-bot.json\n\n## Other comparisons with AWS End User Messaging or Telegram Bot 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 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 Telegram Bot API](https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot.md)\n- [Bandwidth Messaging API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.md)\n- [Bird API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/bird-vs-telegram-bot.md)\n- [ClickSend SMS API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/clicksend-vs-telegram-bot.md)\n- [Infobip API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.md)\n- [Plivo API vs Telegram Bot API](https://www.anchorterminal.com/compare/plivo-vs-telegram-bot.md)\n- [Sendblue vs Telegram Bot API](https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.md)\n- [Sinch Messaging APIs + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/sinch-vs-telegram-bot.md)\n- [Telegram Bot API vs Telnyx API + MCP](https://www.anchorterminal.com/compare/telegram-bot-vs-telnyx.md)\n- [Telegram Bot API vs Twilio API + MCP](https://www.anchorterminal.com/compare/telegram-bot-vs-twilio.md)\n- [Telegram Bot API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telegram-bot-vs-vonage.md)\n- [Telegram Bot API vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/telegram-bot-vs-whatsapp-cloud-api.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", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "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 Telegram Bot API", "url": "" } ], "description": "AWS End User Messaging scores 74.3 (BB) to Telegram Bot's 43 (E) for inbound messaging. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "AWS End User Messaging BB 74.3", "Telegram Bot API E 43", "scores" ], "h1": "AWS End User Messaging vs Telegram Bot API", "image": "https://www.anchorterminal.com/assets/og/compare-aws-end-user-messaging-vs-telegram-bot.png", "path": "/compare/aws-end-user-messaging-vs-telegram-bot", "published": "2026-10-01", "section": "tools", "title": "AWS End User Messaging vs Telegram Bot for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot" }, "tokens": { "markdown": 2800, "slim": 680 }, "version": 1 }