{ "data": { "a": { "slug": "infobip", "name": "Infobip API + MCP", "vendor": "Infobip", "vendorUrl": "https://www.infobip.com", "kind": "http-api", "category": "messaging", "summary": "Per-channel REST APIs and a unified Messages API for SMS, MMS, WhatsApp, RCS and Viber, plus 2FA.", "url": "https://www.anchorterminal.com/tools/infobip", "markdownUrl": "https://www.anchorterminal.com/tools/infobip.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/infobip.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/infobip.json", "repo": "https://github.com/infobip/mcp", "license": "MIT", "transports": [ "http", "streamable-http", "sse" ], "remoteUrl": "https://api.infobip.com", "packages": [ { "registry": "npm", "name": "@infobip-api/sdk" }, { "registry": "pypi", "name": "infobip-api-python-client" } ], "auth": "mixed", "authNotes": "API key with scopes, sent as `Authorization: App \u003ckey\u003e`, or OAuth 2.0. Each account has its own base URL at \u003csubdomain\u003e.api.infobip.com. The MCP servers accept OAuth 2.1 with discovery or the same App key header.", "pricing": "usage", "pricingNotes": "Pay as you go. The SMS page shows the average across networks, about $0.0082 a message to the US and $0.044 to the UK. US WhatsApp $0.00476 per utility or authentication message, $0.0374 per marketing message and $0.005 per free-form message; the first 1,000 service conversations per WhatsApp Business Account a month are free. The 60-day free trial allows up to 100 messages per channel to your verified number (https://www.infobip.com/sms/pricing).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 36, "npmWeekly": 17770, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://www.infobip.com/docs/api", "llmsTxt": "https://www.infobip.com/docs/llms.txt", "openapi": "https://api.infobip.com/platform/1/openapi", "registryName": "com.infobip/mcp", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.whatsapp", "messaging.rcs", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "free-tier", "mcp", "llms-txt", "openapi", "webhooks", "whatsapp", "sms", "enterprise" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 59.1, "grade": "C", "agentReady": false, "rank": 559, "ranked": true, "rankOf": 950, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 60, "payments": 25, "reliability": 43, "schema": 90, "security": 67, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "API keys with scopes, expiry dates and IP allowlists, and OAuth 2.1 on the MCP servers. Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours).", "bestFor": "Teams that need many channels and countries from one vendor with tightly scoped keys, or that already use Infobip.", "strengths": [ "API keys with scopes, expiry dates and IP allowlists, and OAuth 2.1 on the MCP servers", "18 hosted MCP servers split by channel, with the Message server at 1 or 2 tools", "One OpenAPI 3.1 spec for the whole platform, plus llms.txt and a no-key docs MCP", "Valid security.txt, ISO 27001, 27017 and 27018, and SOC 2 Type 2", "Sub-processor page with data locations and change alerts" ], "weaknesses": [ "Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours)", "No messaging rate limits or SLA published", "Published SMS prices are network averages, and per-network rates need a portal login", "JavaScript SDK unreleased since November 2023", "No webhook signing found" ], "agentNotes": [ "Use the account's own base URL (\u003csubdomain\u003e.api.infobip.com), not a generic host", "Connect only the MCP server for the channel you need, the RCS server alone has 27 tools", "Create a key with only the scopes the agent needs and an expiry date", "Send trial messages from ServiceSMS to verified numbers only (up to 5)" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.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": 59.1 } ], "editorialScores": { "ergonomics": 56, "maintenance": 60, "payments": 25, "reliability": 43, "schema": 90, "security": 67, "transparency": 55 }, "provenanceScore": 97 }, "connect": { "http": "curl -X POST \"https://$INFOBIP_BASE_URL/sms/3/messages\" \\\n -H \"Authorization: App $INFOBIP_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"messages\":[{\"sender\":\"ServiceSMS\",\"destinations\":[{\"to\":\"447415774332\"}],\"content\":{\"text\":\"Hello from Infobip\"}}]}'", "claudeCode": "claude mcp add --transport http infobip-sms https://mcp.infobip.com/sms", "config": { "mcpServers": { "infobip-sms": { "headers": { "Authorization": "App ${INFOBIP_API_KEY}" }, "type": "http", "url": "https://mcp.infobip.com/sms" } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/infobip" }, "sameCompany": [ "infobip-calls" ], "area": "communication", "unitPrices": [ { "item": "SMS outbound, US", "unit": "message", "usd": 0.0082, "note": "average across networks" }, { "item": "SMS outbound, UK", "unit": "message", "usd": 0.044, "note": "average across networks" }, { "item": "WhatsApp utility or authentication, US", "unit": "message", "usd": 0.00476 }, { "item": "WhatsApp marketing, US", "unit": "message", "usd": 0.0374 }, { "item": "WhatsApp free-form, US", "unit": "message", "usd": 0.005 } ], "provenance": { "legalEntity": "Infobip Ltd", "domain": "infobip.com", "domainRegistered": "2003-10-16", "endpointOnVendorDomain": true, "terms": "https://www.infobip.com/policies/service-terms-conditions", "privacy": "https://www.infobip.com/policies/privacy-notice", "statusPage": "https://status.infobip.com", "changelog": "https://www.infobip.com/docs/release-notes", "securityTxt": "valid", "checked": "2026-09-30", "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/infobip.json", "live": { "slug": "infobip", "probe": { "target": "https://api.infobip.com", "method": "get", "lastAt": "2026-10-10T03:53:30.735676235Z", "lastOk": true, "lastStatus": 200, "lastMs": 98, "authRequired": false, "uptime24h": 100, "uptime30d": 99.76, "p50ms24h": 96, "p95ms24h": 138, "samples24h": 249, "samples30d": 2476, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 275 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 269 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 271 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 267 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.infobip.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:24.911436631Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.infobip/mcp", "version": "2.0.0", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@infobip-api/sdk", "version": "0.3.2", "seenAt": "2026-10-09T16:59:02.991579926Z" }, { "registry": "pypi", "name": "infobip-api-python-client", "version": "6.0.0", "released": "2026-01-22", "seenAt": "2026-10-09T16:59:03.369770205Z" }, { "registry": "pypi", "name": "infobip-api-python-sdk", "version": "5.0.1", "released": "2023-05-26", "seenAt": "2026-10-01T13:22:43.582658414Z" } ], "githubStars": 36, "npmWeekly": 8254, "pypiWeekly": 15545, "securityTxt": { "url": "https://infobip.com/.well-known/security.txt", "state": "valid", "expires": "2030-01-01T00:00:00.000Z", "checkedAt": "2026-10-09T15:39:50.59986368Z" }, "llmsTxt": { "url": "https://www.infobip.com/docs/llms.txt", "ok": false, "status": 404, "checkedAt": "2026-10-09T14:02:13.070609056Z" }, "domain": { "domain": "infobip.com", "registered": "2003-10-16", "source": "https://rdap.verisign.com/com/v1/domain/infobip.com", "checkedAt": "2026-10-04T13:06:32.73892323Z" }, "pages": [ { "url": "https://www.infobip.com/sms/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-09T18:51:15.942701953Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b5e060a84bd2" } ], "updatedAt": "2026-10-10T03:58:24.911436631Z" } }, "answer": "Infobip API + MCP scores 59.1 (C) 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-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": "Infobip", "b": "Telegram Messenger Inc.", "name": "Vendor" }, { "a": "https://api.infobip.com", "b": "https://api.telegram.org", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, SSE (legacy)", "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": "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": "com.infobip/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-09-09", "b": "2026-08-24", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-01-22", "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": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "36 stars, 18k npm/wk", "b": "4.5k stars", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Infobip API + MCP scores 59.1 (C) 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, Infobip API + MCP or Telegram Bot API?" }, { "answer": "Infobip API + MCP takes an API key or an OAuth sign-in. Telegram Bot API needs an API key.", "question": "Do Infobip API + MCP and Telegram Bot API need an API key?" }, { "answer": "Yes. Infobip API + MCP has a hosted endpoint at https://api.infobip.com and Telegram Bot API at https://api.telegram.org.", "question": "Can an agent call Infobip API + MCP and Telegram Bot API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 90 against 44", "Agent ergonomics, 56 against 48", "Security \u0026 auth, 67 against 35", "Maintenance \u0026 community, 60 against 38", "Transparency \u0026 trust, 76 against 64" ], "also": null, "goodFor": "Teams that need many channels and countries from one vendor with tightly scoped keys, or that already use Infobip.", "slug": "infobip", "watchFor": "Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours)" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 25" ], "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-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/bandwidth-vs-infobip.json", "title": "Bandwidth Messaging API + MCP vs Infobip API + MCP", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-infobip" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-infobip.json", "title": "Bird API + MCP vs Infobip API + MCP", "url": "https://www.anchorterminal.com/compare/bird-vs-infobip" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-infobip.json", "title": "ClickSend SMS API + MCP vs Infobip API + MCP", "url": "https://www.anchorterminal.com/compare/clicksend-vs-infobip" }, { "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/infobip-vs-sendblue.json", "title": "Infobip API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/infobip-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-sinch.json", "title": "Infobip API + MCP vs Sinch Messaging APIs + MCP", "url": "https://www.anchorterminal.com/compare/infobip-vs-sinch" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-telnyx.json", "title": "Infobip API + MCP vs Telnyx API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-vs-telnyx" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-twilio.json", "title": "Infobip API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-vonage.json", "title": "Infobip API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-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/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-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/infobip-vs-whatsapp-cloud-api.json", "title": "Infobip API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api" } ], "scores": [ { "by": 3, "edge": "infobip", "infobip": 43, "key": "reliability", "name": "Reliability", "telegram-bot": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 46, "edge": "infobip", "infobip": 90, "key": "schema", "name": "Schema \u0026 documentation", "telegram-bot": 44, "weight": 13 }, { "by": 8, "edge": "infobip", "infobip": 56, "key": "ergonomics", "name": "Agent ergonomics", "telegram-bot": 48, "weight": 13 }, { "by": 32, "edge": "infobip", "infobip": 67, "key": "security", "name": "Security \u0026 auth", "telegram-bot": 35, "weight": 14 }, { "by": 15, "edge": "telegram-bot", "infobip": 25, "key": "payments", "name": "Payments \u0026 pricing", "telegram-bot": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 22, "edge": "infobip", "infobip": 60, "key": "maintenance", "name": "Maintenance \u0026 community", "telegram-bot": 38, "weight": 7 }, { "by": 12, "edge": "infobip", "infobip": 76, "key": "transparency", "name": "Transparency \u0026 trust", "telegram-bot": 64, "weight": 7 } ], "summary": "Infobip API + MCP scores 59.1 (C) 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": { "infobip": "API keys with scopes, expiry dates and IP allowlists, and OAuth 2.1 on the MCP servers. Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours).", "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/infobip-vs-telegram-bot", "json": "https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.md", "slim": "https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.min.md" }, "markdown": "Infobip API + MCP scores 59.1 (C) 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- Infobip API + MCP: grade C, 59.1/100, rank #559 of 950. Markdown https://www.anchorterminal.com/tools/infobip.md · JSON https://www.anchorterminal.com/api/v1/tools/infobip.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### Infobip API + MCP (C)\n\nGood for: Teams that need many channels and countries from one vendor with tightly scoped keys, or that already use Infobip.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 44\n- Agent ergonomics, 56 against 48\n- Security \u0026 auth, 67 against 35\n- Maintenance \u0026 community, 60 against 38\n- Transparency \u0026 trust, 76 against 64\n\nWatch for: Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours)\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 25\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 | Infobip API + MCP | Telegram Bot API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 43 | 40 | Infobip API + MCP +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 44 | Infobip API + MCP +46 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 48 | Infobip API + MCP +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 67 | 35 | Infobip API + MCP +32 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 40 | Telegram Bot API +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 38 | Infobip API + MCP +22 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 76 | 64 | Infobip API + MCP +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.1 · C** | **43 · E** | |\n\n## Facts side by side\n\n| Fact | Infobip API + MCP | Telegram Bot API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Infobip | Telegram Messenger Inc. |\n| Hosted endpoint | `https://api.infobip.com` | `https://api.telegram.org` |\n| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP |\n| Auth | OAuth or 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| MCP registry | `com.infobip/mcp` | not listed |\n| Last release | 2026-09-09 | 2026-08-24 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2026-01-22 | 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 | not found in the text | not found in the text |\n| Popularity | 36 stars, 18k npm/wk | 4.5k stars |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Infobip API + MCP.** API keys with scopes, expiry dates and IP allowlists, and OAuth 2.1 on the MCP servers. Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours).\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### Infobip API + MCP\n\n1. Use the account's own base URL (\u003csubdomain\u003e.api.infobip.com), not a generic host\n2. Connect only the MCP server for the channel you need, the RCS server alone has 27 tools\n3. Create a key with only the scopes the agent needs and an expiry date\n4. Send trial messages from ServiceSMS to verified numbers only (up to 5)\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, Infobip API + MCP or Telegram Bot API?\n\nInfobip API + MCP scores 59.1 (C) 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 Infobip API + MCP and Telegram Bot API need an API key?\n\nInfobip API + MCP takes an API key or an OAuth sign-in. Telegram Bot API needs an API key.\n\n### Can an agent call Infobip API + MCP and Telegram Bot API without installing anything?\n\nYes. Infobip API + MCP has a hosted endpoint at https://api.infobip.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/infobip-vs-telegram-bot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"infobip\", \"b\": \"telegram-bot\"}`. From a terminal: `anchor compare infobip telegram-bot`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/infobip.json and https://www.anchorterminal.com/api/v1/tools/telegram-bot.json\n\n## Other comparisons with Infobip API + MCP or Telegram Bot API\n\n- [AWS End User Messaging vs Infobip API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-infobip.md)\n- [Bandwidth Messaging API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-infobip.md)\n- [Bird API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/bird-vs-infobip.md)\n- [ClickSend SMS API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-infobip.md)\n- [Infobip API + MCP vs Plivo API](https://www.anchorterminal.com/compare/infobip-vs-plivo.md)\n- [Infobip API + MCP vs Sendblue](https://www.anchorterminal.com/compare/infobip-vs-sendblue.md)\n- [Infobip API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/infobip-vs-sinch.md)\n- [Infobip API + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/infobip-vs-telnyx.md)\n- [Infobip API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/infobip-vs-twilio.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-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- [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 Infobip API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-infobip.md)\n- [Infobip API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/infobip-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": "Infobip API + MCP vs Telegram Bot API", "url": "" } ], "description": "Infobip scores 59.1 (C) to Telegram Bot's 43 (E) for inbound messaging. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Infobip API + MCP C 59.1", "Telegram Bot API E 43", "scores" ], "h1": "Infobip API + MCP vs Telegram Bot API", "image": "https://www.anchorterminal.com/assets/og/compare-infobip-vs-telegram-bot.png", "path": "/compare/infobip-vs-telegram-bot", "published": "2026-10-01", "section": "tools", "title": "Infobip vs Telegram Bot for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/infobip-vs-telegram-bot" }, "tokens": { "markdown": 2550, "slim": 680 }, "version": 1 }