{
  "data": {
    "a": {
      "slug": "bandwidth",
      "name": "Bandwidth Messaging API + MCP",
      "vendor": "Bandwidth",
      "vendorUrl": "https://www.bandwidth.com",
      "kind": "http-api",
      "category": "messaging",
      "summary": "US carrier's messaging API for SMS, MMS and RCS over 10DLC, toll-free and short codes, with published US rates.",
      "url": "https://www.anchorterminal.com/tools/bandwidth",
      "markdownUrl": "https://www.anchorterminal.com/tools/bandwidth.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bandwidth.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bandwidth.json",
      "repo": "https://github.com/Bandwidth/mcp-server",
      "transports": [
        "http",
        "stdio",
        "streamable-http"
      ],
      "remoteUrl": "https://messaging.bandwidth.com/api/v2",
      "packages": [
        {
          "registry": "npm",
          "name": "bandwidth-sdk"
        },
        {
          "registry": "pypi",
          "name": "bandwidth-sdk"
        }
      ],
      "auth": "oauth",
      "authNotes": "OAuth 2.0 client credentials. Exchange the client ID and secret at api.bandwidth.com/api/v1/oauth2/token for a Bearer token. Legacy API users with Basic auth are being migrated. The MCP server takes BW_CLIENT_ID and BW_CLIENT_SECRET.",
      "pricing": "paid",
      "pricingNotes": "Messaging is contract-first with account-managed onboarding. Published US rates are 10DLC SMS $0.004 and MMS $0.015 a message, toll-free SMS $0.007 and MMS $0.020, short code SMS $0.008 and MMS $0.020. The Build free trial (3,000 credits, no card) covers voice and SIP only (https://www.bandwidth.com/pricing/).",
      "priceSummary": "Paid",
      "where": "both",
      "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": 2,
        "npmWeekly": 12740,
        "pypiWeekly": 39218,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://dev.bandwidth.com",
      "llmsTxt": "https://dev.bandwidth.com/llms.txt",
      "openapi": "https://dev.bandwidth.com/spec/messaging.yml",
      "capabilities": [
        "messaging.sms",
        "messaging.mms",
        "messaging.rcs",
        "messaging.voice",
        "messaging.verify",
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "mcp",
        "llms-txt",
        "openapi",
        "typescript",
        "python",
        "webhooks",
        "sms",
        "enterprise"
      ],
      "lastRelease": "2026-09-22",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 64.3,
        "grade": "B",
        "agentReady": false,
        "rank": 353,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 7,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 73,
          "maintenance": 78,
          "payments": 20,
          "reliability": 70,
          "schema": 86,
          "security": 55,
          "transparency": 63
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published. Messaging accounts are onboarded by sales, and the free Build trial covers voice only.",
        "bestFor": "US and Canada senders at volume who want carrier-owned routes and will talk to sales.",
        "strengths": [
          "10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published",
          "OAuth 2.0 client credentials with roles, account scope and two-secret rotation",
          "A full queue returns 429 stating the allowed rate and queue size",
          "OpenAPI spec for messaging and llms.txt with Markdown pages",
          "MCP tool profiles keep a messaging agent to the send, list and media tools"
        ],
        "weaknesses": [
          "Messaging accounts are onboarded by sales, and the free Build trial covers voice only",
          "No callback signing found",
          "No SLA, sub-processor list or retention periods found",
          "The MCP is beta, installed by cloning the repo, with no licence file",
          "No security.txt, bug bounty or disclosure policy found"
        ],
        "agentNotes": [
          "Exchange the client ID and secret for a Bearer token first, tokens last 1 hour",
          "Set `BW_MCP_PROFILE=messaging` to load only the messaging tools",
          "Pass at least one filter to listMessages, with millisecond-precision timestamps",
          "On a 429, read the allowed rate in the error and pace sends to it"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.3
          }
        ],
        "editorialScores": {
          "ergonomics": 73,
          "maintenance": 78,
          "payments": 20,
          "reliability": 70,
          "schema": 86,
          "security": 55,
          "transparency": 35
        },
        "provenanceScore": 90
      },
      "connect": {
        "http": "curl -X POST \"https://messaging.bandwidth.com/api/v2/users/$BW_ACCOUNT_ID/messages\" -H \"Authorization: Bearer $BW_ACCESS_TOKEN\" \\\n  -H \"Content-Type: application/json\" -d '{\"to\":[\"+15555550123\"],\"from\":\"+15555550100\",\"text\":\"Hello from Bandwidth\",\"applicationId\":\"'$BW_MESSAGING_APPLICATION_ID'\"}'",
        "config": {
          "mcpServers": {
            "bandwidth": {
              "args": [
                "--from",
                "/path/to/mcp-server",
                "start"
              ],
              "command": "uvx",
              "env": {
                "BW_CLIENT_ID": "${BW_CLIENT_ID}",
                "BW_CLIENT_SECRET": "${BW_CLIENT_SECRET}",
                "BW_MCP_PROFILE": "messaging"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/bandwidth"
      },
      "sameCompany": [
        "bandwidth-voice"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "SMS outbound, US 10DLC",
          "unit": "message",
          "usd": 0.004,
          "note": "US, published list rate"
        },
        {
          "item": "SMS outbound, US toll-free",
          "unit": "message",
          "usd": 0.007,
          "note": "US"
        },
        {
          "item": "SMS outbound, US short code",
          "unit": "message",
          "usd": 0.008,
          "note": "US"
        },
        {
          "item": "MMS outbound, US 10DLC",
          "unit": "message",
          "usd": 0.015,
          "note": "US"
        }
      ],
      "provenance": {
        "legalEntity": "Bandwidth Inc.",
        "domain": "bandwidth.com",
        "domainRegistered": "1995-02-20",
        "endpointOnVendorDomain": true,
        "terms": "https://www.bandwidth.com/legal/communications-services-agreement/",
        "privacy": "https://www.bandwidth.com/legal/privacy/",
        "statusPage": "https://status.bandwidth.com",
        "changelog": "https://www.bandwidth.com/release-notes/",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "score": 90
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/bandwidth.json",
      "live": {
        "slug": "bandwidth",
        "probe": {
          "target": "https://messaging.bandwidth.com/api/v2",
          "method": "get",
          "lastAt": "2026-10-10T01:37:44.387551803Z",
          "lastOk": false,
          "lastStatus": 503,
          "lastMs": 346,
          "lastNote": "server error",
          "authRequired": false,
          "uptime24h": 0,
          "uptime30d": 0,
          "p50ms24h": 0,
          "p95ms24h": 0,
          "samples24h": 250,
          "samples30d": 2453,
          "days": [
            {
              "date": "2026-09-30",
              "probes": 35,
              "ok": 0
            },
            {
              "date": "2026-10-01",
              "probes": 276,
              "ok": 0
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 0
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 0
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 0
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 0
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 0
            },
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 0
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 0
            },
            {
              "date": "2026-10-10",
              "probes": 17,
              "ok": 0
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.bandwidth.com",
          "indicator": "major",
          "summary": "Partial System Outage",
          "checkedAt": "2026-10-10T01:33:22.09538373Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "Bandwidth/mcp-server",
            "version": "v0.3.0",
            "released": "2026-06-11",
            "seenAt": "2026-10-09T16:42:22.845091173Z"
          },
          {
            "registry": "npm",
            "name": "bandwidth-sdk",
            "version": "8.3.0",
            "seenAt": "2026-10-09T16:42:22.60156522Z"
          },
          {
            "registry": "pypi",
            "name": "bandwidth-sdk",
            "version": "23.3.0",
            "released": "2026-09-22",
            "seenAt": "2026-10-09T16:42:22.714217104Z"
          }
        ],
        "githubStars": 2,
        "npmWeekly": 14809,
        "pypiWeekly": 26765,
        "securityTxt": {
          "url": "https://bandwidth.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:40:12.81833044Z"
        },
        "llmsTxt": {
          "url": "https://dev.bandwidth.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:01:30.582838766Z"
        },
        "domain": {
          "domain": "bandwidth.com",
          "registered": "1995-02-20",
          "source": "https://rdap.verisign.com/com/v1/domain/bandwidth.com",
          "checkedAt": "2026-10-04T13:08:39.296680691Z"
        },
        "updatedAt": "2026-10-10T01:37:44.387551803Z"
      }
    },
    "answer": "Bandwidth Messaging API + MCP scores 64.3 (B) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 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-10T01:38:09.926012316Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 129,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 116,
          "p95ms24h": 503,
          "samples24h": 102,
          "samples30d": 102,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 17,
              "ok": 17
            }
          ]
        },
        "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-10T01:38:09.926012316Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Bandwidth",
        "b": "Telegram Messenger Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://messaging.bandwidth.com/api/v2",
        "b": "https://api.telegram.org",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, stdio, Streamable HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "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": "2026-09-22",
        "b": "2026-08-24",
        "name": "Last release"
      },
      {
        "a": "2025-09-11",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-25",
        "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": "2 stars, 13k npm/wk, 39k PyPI/wk",
        "b": "4.5k stars",
        "name": "Popularity"
      },
      {
        "a": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Bandwidth Messaging API + MCP scores 64.3 (B) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing.",
        "question": "Which is better for AI agents, Bandwidth Messaging API + MCP or Telegram Bot API?"
      },
      {
        "answer": "Bandwidth Messaging API + MCP uses an OAuth sign-in. Telegram Bot API needs an API key.",
        "question": "Do Bandwidth Messaging API + MCP and Telegram Bot API need an API key?"
      },
      {
        "answer": "Yes. Bandwidth Messaging API + MCP has a hosted endpoint at https://messaging.bandwidth.com/api/v2 and Telegram Bot API at https://api.telegram.org.",
        "question": "Can an agent call Bandwidth Messaging API + MCP and Telegram Bot API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 70 against 40",
          "Schema \u0026 documentation, 86 against 44",
          "Agent ergonomics, 73 against 48",
          "Security \u0026 auth, 55 against 35",
          "Maintenance \u0026 community, 78 against 38"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "US and Canada senders at volume who want carrier-owned routes and will talk to sales.",
        "slug": "bandwidth",
        "watchFor": "Messaging accounts are onboarded by sales, and the free Build trial covers voice only"
      },
      {
        "aheadOn": [
          "Payments \u0026 pricing, 40 against 20"
        ],
        "also": null,
        "goodFor": "An agent that talks to people who use Telegram, with free sends and long polling that needs no public server.",
        "slug": "telegram-bot",
        "watchFor": "No OpenAPI document, llms.txt or official SDK was found. The contract is one HTML reference page of about 860 KB"
      }
    ],
    "job": {
      "capability": "messaging.inbound",
      "name": "Inbound messaging"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bandwidth.json",
        "title": "AWS End User Messaging vs Bandwidth Messaging API + MCP",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bandwidth"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-bird.json",
        "title": "Bandwidth Messaging API + MCP vs Bird API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-bird"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-clicksend.json",
        "title": "Bandwidth Messaging API + MCP vs ClickSend SMS API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-clicksend"
      },
      {
        "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/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/bandwidth-vs-sendblue.json",
        "title": "Bandwidth Messaging API + MCP vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-sendblue"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-sinch.json",
        "title": "Bandwidth Messaging API + MCP vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-telnyx.json",
        "title": "Bandwidth Messaging API + MCP vs Telnyx API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-telnyx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-twilio.json",
        "title": "Bandwidth Messaging API + MCP vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage.json",
        "title": "Bandwidth Messaging API + MCP vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage"
      },
      {
        "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-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-whatsapp-cloud-api.json",
        "title": "Bandwidth Messaging API + MCP vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api"
      },
      {
        "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"
      }
    ],
    "scores": [
      {
        "bandwidth": 70,
        "by": 30,
        "edge": "bandwidth",
        "key": "reliability",
        "name": "Reliability",
        "telegram-bot": 40,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bandwidth": 86,
        "by": 42,
        "edge": "bandwidth",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "telegram-bot": 44,
        "weight": 13
      },
      {
        "bandwidth": 73,
        "by": 25,
        "edge": "bandwidth",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "telegram-bot": 48,
        "weight": 13
      },
      {
        "bandwidth": 55,
        "by": 20,
        "edge": "bandwidth",
        "key": "security",
        "name": "Security \u0026 auth",
        "telegram-bot": 35,
        "weight": 14
      },
      {
        "bandwidth": 20,
        "by": 20,
        "edge": "telegram-bot",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "telegram-bot": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bandwidth": 78,
        "by": 40,
        "edge": "bandwidth",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "telegram-bot": 38,
        "weight": 7
      },
      {
        "bandwidth": 63,
        "by": 1,
        "edge": "telegram-bot",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "telegram-bot": 64,
        "weight": 7
      }
    ],
    "summary": "Bandwidth Messaging API + MCP scores 64.3 (B) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing. Both do inbound messaging.",
    "verdicts": {
      "bandwidth": "10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published. Messaging accounts are onboarded by sales, and the free Build trial covers voice only.",
      "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/bandwidth-vs-telegram-bot",
    "json": "https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.md",
    "slim": "https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.min.md"
  },
  "markdown": "Bandwidth Messaging API + MCP scores 64.3 (B) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing. Both do inbound messaging.\n\n- Bandwidth Messaging API + MCP: grade B, 64.3/100, rank #353 of 950. Markdown https://www.anchorterminal.com/tools/bandwidth.md · JSON https://www.anchorterminal.com/api/v1/tools/bandwidth.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### Bandwidth Messaging API + MCP (B)\n\nGood for: US and Canada senders at volume who want carrier-owned routes and will talk to sales.\n\nAhead on:\n- Reliability, 70 against 40\n- Schema \u0026 documentation, 86 against 44\n- Agent ergonomics, 73 against 48\n- Security \u0026 auth, 55 against 35\n- Maintenance \u0026 community, 78 against 38\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Messaging accounts are onboarded by sales, and the free Build trial covers voice only\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 20\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 | Bandwidth Messaging API + MCP | Telegram Bot API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 40 | Bandwidth Messaging API + MCP +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 44 | Bandwidth Messaging API + MCP +42 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 48 | Bandwidth Messaging API + MCP +25 |\n| Security \u0026 auth | 14% (17.5 this run) | 55 | 35 | Bandwidth Messaging API + MCP +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Telegram Bot API +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 38 | Bandwidth Messaging API + MCP +40 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 64 | Telegram Bot API +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.3 · B** | **43 · E** | |\n\n## Facts side by side\n\n| Fact | Bandwidth Messaging API + MCP | Telegram Bot API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bandwidth | Telegram Messenger Inc. |\n| Hosted endpoint | `https://messaging.bandwidth.com/api/v2` | `https://api.telegram.org` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP |\n| Auth | OAuth | 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 | 2026-09-22 | 2026-08-24 |\n| Terms last updated | 2025-09-11 | no date given |\n| Privacy policy last updated | 2026-08-25 | 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 | 2 stars, 13k npm/wk, 39k PyPI/wk | 4.5k stars |\n| Agent reviews | 3.5/5 (2) | none |\n\n## Verdicts\n\n**Bandwidth Messaging API + MCP.** 10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published. Messaging accounts are onboarded by sales, and the free Build trial covers voice only.\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### Bandwidth Messaging API + MCP\n\n1. Exchange the client ID and secret for a Bearer token first, tokens last 1 hour\n2. Set `BW_MCP_PROFILE=messaging` to load only the messaging tools\n3. Pass at least one filter to listMessages, with millisecond-precision timestamps\n4. On a 429, read the allowed rate in the error and pace sends to it\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, Bandwidth Messaging API + MCP or Telegram Bot API?\n\nBandwidth Messaging API + MCP scores 64.3 (B) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on payments \u0026 pricing.\n\n### Do Bandwidth Messaging API + MCP and Telegram Bot API need an API key?\n\nBandwidth Messaging API + MCP uses an OAuth sign-in. Telegram Bot API needs an API key.\n\n### Can an agent call Bandwidth Messaging API + MCP and Telegram Bot API without installing anything?\n\nYes. Bandwidth Messaging API + MCP has a hosted endpoint at https://messaging.bandwidth.com/api/v2 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/bandwidth-vs-telegram-bot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bandwidth\", \"b\": \"telegram-bot\"}`. From a terminal: `anchor compare bandwidth telegram-bot`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bandwidth.json and https://www.anchorterminal.com/api/v1/tools/telegram-bot.json\n\n## Other comparisons with Bandwidth Messaging API + MCP or Telegram Bot API\n\n- [AWS End User Messaging vs Bandwidth Messaging API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bandwidth.md)\n- [Bandwidth Messaging API + MCP vs Bird API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-bird.md)\n- [Bandwidth Messaging API + MCP vs ClickSend SMS API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-clicksend.md)\n- [Bandwidth Messaging API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-infobip.md)\n- [Bandwidth Messaging API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bandwidth-vs-plivo.md)\n- [Bandwidth Messaging API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bandwidth-vs-sendblue.md)\n- [Bandwidth Messaging API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-sinch.md)\n- [Bandwidth Messaging API + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-telnyx.md)\n- [Bandwidth Messaging API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-twilio.md)\n- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Bandwidth Messaging API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-bandwidth.md)\n- [360dialog WhatsApp API + MCP vs 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 WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api.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",
  "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": "Bandwidth Messaging API + MCP vs Telegram Bot API",
        "url": ""
      }
    ],
    "description": "Bandwidth Messaging scores 64.3 (B) to Telegram Bot's 43 (E) for inbound messaging. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Bandwidth Messaging API + MCP B 64.3",
      "Telegram Bot API E 43",
      "scores"
    ],
    "h1": "Bandwidth Messaging API + MCP vs Telegram Bot API",
    "image": "https://www.anchorterminal.com/assets/og/compare-bandwidth-vs-telegram-bot.png",
    "path": "/compare/bandwidth-vs-telegram-bot",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Bandwidth Messaging vs Telegram Bot for AI agents (2026)",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot"
  },
  "tokens": {
    "markdown": 2600,
    "slim": 680
  },
  "version": 1
}