{ "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": 740, "ranked": true, "rankOf": 950, "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-10T03:53:17.283568345Z", "lastOk": true, "lastStatus": 401, "lastMs": 133, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 124, "p95ms24h": 200, "samples24h": 249, "samples30d": 2476, "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": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.360dialog.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:02.859076124Z" }, "securityTxt": { "url": "https://360dialog.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:51.238199064Z" }, "llmsTxt": { "url": "https://docs.360dialog.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:04.75070358Z" }, "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-09T18:36:24.378113737Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9b34ec104a49" }, { "url": "https://360dialog.com/legal/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-09T18:32:07.677770593Z", "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-09T18:40:14.041674087Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "updatedAt": "2026-10-10T03:53:17.283568345Z" } }, "answer": "360dialog WhatsApp API + MCP scores 52 (D) on agent readiness against Telegram Bot API's 43 (E), and leads in 3 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "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-10T03:53:46.369997744Z", "lastOk": true, "lastStatus": 200, "lastMs": 85, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 112, "p95ms24h": 464, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "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-10T03:53:46.369997744Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "360dialog", "b": "Telegram Messenger Inc.", "name": "Vendor" }, { "a": "https://waba-v2.360dialog.io", "b": "https://api.telegram.org", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "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": "none", "b": "2026-08-24", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-10", "b": "2024-06-01", "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": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "4.5k stars", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "360dialog WhatsApp API + MCP scores 52 (D) on agent readiness against Telegram Bot API's 43 (E), and leads in 3 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, 360dialog WhatsApp API + MCP or Telegram Bot API?" }, { "answer": "360dialog WhatsApp API + MCP takes an API key or an OAuth sign-in. Telegram Bot API needs an API key.", "question": "Do 360dialog WhatsApp API + MCP and Telegram Bot API need an API key?" }, { "answer": "Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and Telegram Bot API at https://api.telegram.org.", "question": "Can an agent call 360dialog WhatsApp API + MCP and Telegram Bot API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 83 against 40", "Schema \u0026 documentation, 70 against 44", "Agent ergonomics, 53 against 48" ], "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": [ "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 38 against 8", "Transparency \u0026 trust, 64 against 48" ], "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/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" }, { "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.json", "title": "AWS End User Messaging vs Telegram Bot API", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-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/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" } ], "scores": [ { "360dialog": 83, "by": 43, "edge": "360dialog", "key": "reliability", "name": "Reliability", "telegram-bot": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "360dialog": 70, "by": 26, "edge": "360dialog", "key": "schema", "name": "Schema \u0026 documentation", "telegram-bot": 44, "weight": 13 }, { "360dialog": 53, "by": 5, "edge": "360dialog", "key": "ergonomics", "name": "Agent ergonomics", "telegram-bot": 48, "weight": 13 }, { "360dialog": 35, "by": 0, "edge": "", "key": "security", "name": "Security \u0026 auth", "telegram-bot": 35, "weight": 14 }, { "360dialog": 35, "by": 5, "edge": "telegram-bot", "key": "payments", "name": "Payments \u0026 pricing", "telegram-bot": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "360dialog": 8, "by": 30, "edge": "telegram-bot", "key": "maintenance", "name": "Maintenance \u0026 community", "telegram-bot": 38, "weight": 7 }, { "360dialog": 48, "by": 16, "edge": "telegram-bot", "key": "transparency", "name": "Transparency \u0026 trust", "telegram-bot": 64, "weight": 7 } ], "summary": "360dialog WhatsApp API + MCP scores 52 (D) on agent readiness against Telegram Bot API's 43 (E), and leads in 3 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do inbound messaging.", "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.", "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/360dialog-vs-telegram-bot", "json": "https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot.md", "slim": "https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot.min.md" }, "markdown": "360dialog WhatsApp API + MCP scores 52 (D) on agent readiness against Telegram Bot API's 43 (E), and leads in 3 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do inbound messaging.\n\n- 360dialog WhatsApp API + MCP: grade D, 52/100, rank #740 of 950. Markdown https://www.anchorterminal.com/tools/360dialog.md · JSON https://www.anchorterminal.com/api/v1/tools/360dialog.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### 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 40\n- Schema \u0026 documentation, 70 against 44\n- Agent ergonomics, 53 against 48\n\nWatch for: No changelog, official SDK or standalone OpenAPI download\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 35\n- Maintenance \u0026 community, 38 against 8\n- Transparency \u0026 trust, 64 against 48\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 | 360dialog WhatsApp API + MCP | Telegram Bot API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 83 | 40 | 360dialog WhatsApp API + MCP +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 44 | 360dialog WhatsApp API + MCP +26 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 48 | 360dialog WhatsApp API + MCP +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 35 | 35 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Telegram Bot API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 8 | 38 | Telegram Bot API +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 64 | Telegram Bot API +16 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52 · D** | **43 · E** | |\n\n## Facts side by side\n\n| Fact | 360dialog WhatsApp API + MCP | Telegram Bot API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 360dialog | Telegram Messenger Inc. |\n| Hosted endpoint | `https://waba-v2.360dialog.io` | `https://api.telegram.org` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Free |\n| x402 | no | no |\n| Licence | none | 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 | none | 2026-08-24 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | 2026-09-10 | 2024-06-01 |\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 | yes |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | none | 4.5k stars |\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**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### 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### 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, 360dialog WhatsApp API + MCP or Telegram Bot API?\n\n360dialog WhatsApp API + MCP scores 52 (D) on agent readiness against Telegram Bot API's 43 (E), and leads in 3 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do 360dialog WhatsApp API + MCP and Telegram Bot API need an API key?\n\n360dialog WhatsApp API + MCP takes an API key or an OAuth sign-in. Telegram Bot API needs an API key.\n\n### Can an agent call 360dialog WhatsApp API + MCP and Telegram Bot API without installing anything?\n\nYes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io 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/360dialog-vs-telegram-bot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"360dialog\", \"b\": \"telegram-bot\"}`. From a terminal: `anchor compare 360dialog telegram-bot`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/360dialog.json and https://www.anchorterminal.com/api/v1/tools/telegram-bot.json\n\n## Other comparisons with 360dialog WhatsApp API + MCP or Telegram Bot API\n\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- [AWS End User Messaging vs Telegram Bot API](https://www.anchorterminal.com/compare/aws-end-user-messaging-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- [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", "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": "360dialog WhatsApp API + MCP vs Telegram Bot API", "url": "" } ], "description": "360dialog WhatsApp scores 52 (D) to Telegram Bot's 43 (E) for inbound messaging. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "360dialog WhatsApp API + MCP D 52", "Telegram Bot API E 43", "scores" ], "h1": "360dialog WhatsApp API + MCP vs Telegram Bot API", "image": "https://www.anchorterminal.com/assets/og/compare-360dialog-vs-telegram-bot.png", "path": "/compare/360dialog-vs-telegram-bot", "published": "2026-10-01", "section": "tools", "title": "360dialog WhatsApp vs Telegram Bot for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot" }, "tokens": { "markdown": 2600, "slim": 730 }, "version": 1 }