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