{
  "data": {
    "a": {
      "slug": "sendblue",
      "name": "Sendblue",
      "vendor": "Round One, Inc.",
      "vendorUrl": "https://www.sendblue.com",
      "kind": "http-api",
      "category": "messaging",
      "summary": "Sendblue is a hosted API from Round One, Inc. for sending and receiving iMessage, RCS, SMS and MMS from dedicated or shared phone numbers. Agents use a REST API, TypeScript and Python SDKs, a CLI and an MCP server.",
      "url": "https://www.anchorterminal.com/tools/sendblue",
      "markdownUrl": "https://www.anchorterminal.com/tools/sendblue.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sendblue.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sendblue.json",
      "repo": "https://github.com/sendblue-api/sendblue-ts",
      "license": "Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT",
      "transports": [
        "http",
        "stdio"
      ],
      "remoteUrl": "https://api.sendblue.com",
      "packages": [
        {
          "registry": "npm",
          "name": "sendblue"
        },
        {
          "registry": "pypi",
          "name": "sendblue"
        },
        {
          "registry": "npm",
          "name": "sendblue-api-mcp"
        },
        {
          "registry": "npm",
          "name": "@sendblue/cli"
        }
      ],
      "auth": "api-key",
      "authNotes": "Every request carries the account's key pair in the `sb-api-key-id` and `sb-api-secret-key` headers, and requests from a browser are refused. The keys come from the dashboard or from `sendblue show-keys` after the CLI creates the account, which needs a person to text a one-time code or enter an email code. `POST /v3/auth/tokens` mints a temporary bearer token, account-wide or limited to named phone numbers, valid for 900 seconds by default and revocable. The MCP server reads `SENDBLUE_API_API_KEY` and `SENDBLUE_API_API_SECRET` from the environment. Agency subaccounts with their own keys need approval from support.",
      "pricing": "freemium",
      "pricingNotes": "Flat price per line with no per-message fee. The Free Sandbox is $0 with no card, on a shared number with up to 10 verified contacts. The AI Agent plan is $100 a month per dedicated line and is inbound-first. Proactive outbound messaging is on the Enterprise or Blue Ocean plan, priced through sales. The terms add 3 per cent for card payments and $60 per line to port a number out (https://www.sendblue.com/pricing, checked 2026-10-08).",
      "priceSummary": "$100 / mo",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs, either `llms.txt`, the pricing page or the terms (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 18,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 249505,
        "pypiWeekly": 39912,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.sendblue.com",
      "llmsTxt": "https://docs.sendblue.com/llms.txt",
      "capabilities": [
        "messaging.sms",
        "messaging.mms",
        "messaging.rcs",
        "messaging.inbound",
        "messaging.verify"
      ],
      "tags": [
        "hosted",
        "imessage",
        "sms",
        "rcs",
        "mcp",
        "cli",
        "llms-txt",
        "typescript",
        "python",
        "webhooks",
        "no-card",
        "status-page"
      ],
      "lastRelease": "2026-10-07",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 61.7,
        "grade": "C",
        "agentReady": false,
        "rank": 458,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 9,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 76,
          "maintenance": 72,
          "payments": 40,
          "reliability": 71,
          "schema": 66,
          "security": 46,
          "transparency": 58
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.",
        "bestFor": "An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.",
        "strengths": [
          "One request to `/api/send-message` sends iMessage and can fall back to RCS or SMS, with no per-message fee on any plan",
          "The CLI creates a free account, a shared line and API keys from a terminal, with no card, once a person texts a one-time code",
          "Temporary bearer tokens from `/v3/auth/tokens` can be limited to named phone numbers, expire after 900 seconds by default and can be revoked",
          "Every docs page has a Markdown twin at `/index.md`, and `llms.txt` summarises each page with its limits and conditions",
          "Rate limits are published with numbers for each plan, and declined sends return an `error_key` an agent can branch on"
        ],
        "weaknesses": [
          "Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first",
          "No OpenAPI file was found at any public address, although the SDKs and the reference are generated from one",
          "The docs install `sendblue-api-mcp`, last published on 5 August 2025 with 18 tools. The API now has 54 configured endpoints",
          "`/api/send-message` takes no idempotency key, and the SDKs retry 429 and 5xx responses twice by default",
          "No public DPA, sub-processor list, retention period, deprecation policy or security.txt was found"
        ],
        "agentNotes": [
          "Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails",
          "On the free plan a recipient must text the Sendblue number once before any message to them is accepted",
          "Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six",
          "Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting",
          "Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied",
          "Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 61.7
          }
        ],
        "editorialScores": {
          "ergonomics": 76,
          "maintenance": 72,
          "payments": 40,
          "reliability": 71,
          "schema": 66,
          "security": 46,
          "transparency": 29
        },
        "provenanceScore": 86
      },
      "connect": {
        "install": "npm install sendblue",
        "http": "curl -X POST https://api.sendblue.com/api/send-message \\\n  -H \"sb-api-key-id: $SENDBLUE_API_KEY_ID\" -H \"sb-api-secret-key: $SENDBLUE_API_KEY_SECRET\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"number\":\"+19998887777\",\"from_number\":\"+18887776666\",\"content\":\"Hello from Sendblue!\"}'",
        "claudeCode": "claude mcp add sendblue_api --env SENDBLUE_API_API_KEY=your-api-key --env SENDBLUE_API_API_SECRET=your-api-secret -- npx -y sendblue-api-mcp --client=claude-code --tools=all",
        "config": {
          "mcpServers": {
            "sendblue_api": {
              "args": [
                "-y",
                "sendblue-api-mcp",
                "--tools=all"
              ],
              "command": "npx",
              "env": {
                "SENDBLUE_API_API_KEY": "your-api-key",
                "SENDBLUE_API_API_SECRET": "your-api-secret"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/messaging.sms",
        "tool": "https://letme.dev/sendblue"
      },
      "area": "communication",
      "unitPrices": [
        {
          "item": "AI Agent plan, dedicated line",
          "unit": "month",
          "usd": 100,
          "note": "Per line, inbound-first, no per-message fee. Outbound plans are priced through sales"
        }
      ],
      "provenance": {
        "legalEntity": "Round One, Inc.",
        "domain": "sendblue.com",
        "domainRegistered": "2011-06-25",
        "endpointOnVendorDomain": true,
        "terms": "https://www.sendblue.com/terms-of-service",
        "privacy": "https://www.sendblue.com/privacy-policy",
        "statusPage": "https://status.sendblue.com",
        "changelog": "https://github.com/sendblue-api/sendblue-ts/blob/main/CHANGELOG.md",
        "securityTxt": "none",
        "checked": "2026-10-08",
        "notes": [
          "The terms of service (effective 19 March 2025) and the privacy policy (effective 1 May 2024) both name Round One, Inc. as Sendblue. The site footer gives 344 West End Avenue, New York NY 10024.",
          "The terms cover registering for and using the services, so they govern API use. The privacy policy covers the website and the services and says Sendblue is a processor for its business customers.",
          "The API answers at api.sendblue.com, and the SDKs default to api.sendblue.co, a second domain the vendor uses.",
          "`/.well-known/security.txt` returns 404 on www.sendblue.com, docs.sendblue.com and api.sendblue.com.",
          "There is no API changelog in the docs. The changelog link is the TypeScript SDK's, whose recent entries mostly read as regenerated clients.",
          "RDAP for sendblue.com gives a registration date of 2011-06-25."
        ],
        "score": 86
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/sendblue.json",
      "live": {
        "slug": "sendblue",
        "probe": {
          "target": "https://api.sendblue.com",
          "method": "get",
          "lastAt": "2026-10-10T01:38:06.403762785Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 1731,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 760,
          "p95ms24h": 1108,
          "samples24h": 250,
          "samples30d": 317,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 50,
              "ok": 50
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 17,
              "ok": 17
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.sendblue.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:51:14.917629413Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "sendblue-api/sendblue-ts",
            "version": "v3.20.0",
            "released": "2026-10-09",
            "seenAt": "2026-10-09T17:19:09.249235538Z"
          },
          {
            "registry": "npm",
            "name": "@sendblue/cli",
            "version": "0.10.0",
            "seenAt": "2026-10-09T17:19:07.127689876Z"
          },
          {
            "registry": "npm",
            "name": "sendblue",
            "version": "3.20.0",
            "seenAt": "2026-10-09T17:19:04.894887395Z"
          },
          {
            "registry": "npm",
            "name": "sendblue-api-mcp",
            "version": "2.0.1",
            "seenAt": "2026-10-09T17:19:06.169286695Z"
          },
          {
            "registry": "pypi",
            "name": "sendblue",
            "version": "1.32.0",
            "released": "2026-10-09",
            "seenAt": "2026-10-09T17:19:06.052930344Z"
          }
        ],
        "githubStars": 2,
        "npmWeekly": 131574,
        "pypiWeekly": 39072,
        "securityTxt": {
          "url": "https://sendblue.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:39:46.869185766Z"
        },
        "llmsTxt": {
          "url": "https://docs.sendblue.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:45.616753818Z"
        },
        "pages": [
          {
            "url": "https://raw.githubusercontent.com/sendblue-api/sendblue-ts/main/CHANGELOG.md",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:46:03.149693897Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "3f314fc28e56"
          },
          {
            "url": "https://www.sendblue.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:53:59.846399213Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "c6313cb3e62e"
          },
          {
            "url": "https://www.sendblue.com/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:01.955112717Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "13a9f496f59c"
          },
          {
            "url": "https://www.sendblue.com/terms-of-service",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:03.914334745Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "a3ed89c021ca"
          }
        ],
        "updatedAt": "2026-10-10T01:38:06.403762785Z"
      }
    },
    "answer": "Sendblue scores 61.7 (C) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on transparency \u0026 trust.",
    "b": {
      "slug": "telegram-bot",
      "name": "Telegram Bot API",
      "vendor": "Telegram Messenger Inc.",
      "vendorUrl": "https://telegram.org",
      "kind": "http-api",
      "category": "messaging",
      "summary": "The Telegram Bot API is Telegram's HTTP interface for bot accounts. A bot sends and edits messages, media and polls, manages chats and takes payments, and receives user messages by long polling or webhook, with a token issued by @BotFather.",
      "url": "https://www.anchorterminal.com/tools/telegram-bot",
      "markdownUrl": "https://www.anchorterminal.com/tools/telegram-bot.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/telegram-bot.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/telegram-bot.json",
      "repo": "https://github.com/tdlib/telegram-bot-api",
      "license": "Proprietary hosted service under the Telegram Bot Platform Developer Terms of Service. The Bot API server source in tdlib/telegram-bot-api is BSL-1.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.telegram.org",
      "packages": [],
      "auth": "api-key",
      "authNotes": "Self-serve. A person with a Telegram account sends `/newbot` to @BotFather and receives one token per bot. The token goes in the URL path of every request, as `https://api.telegram.org/bot\u003ctoken\u003e/METHOD_NAME`. It has no scopes or expiry and gives full control of the bot. `/token` in @BotFather generates a new one. No OAuth, app review or sales approval applies.",
      "pricing": "free",
      "pricingNotes": "Free, with no card or contract. The one fee found is for paid broadcasts, 0.1 Telegram Stars per message sent above 30 a second, open to bots with at least 100,000 Stars and 100,000 monthly active users. A separate test environment exists for bots (checked 2026-10-09).",
      "priceSummary": "Free",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Bot API reference, the FAQ, the developer terms or the server source (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 4478,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://core.telegram.org/bots/api",
      "capabilities": [
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "free",
        "api-key",
        "webhooks",
        "long-polling",
        "telegram",
        "chat",
        "open-source-server",
        "bug-bounty",
        "self-serve"
      ],
      "lastRelease": "2026-08-24",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 43,
        "grade": "E",
        "agentReady": false,
        "rank": 885,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 14,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 48,
          "maintenance": 38,
          "payments": 40,
          "reliability": 40,
          "schema": 44,
          "security": 35,
          "transparency": 64
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": 0,
        "verdict": "Telegram's first-party bot interface is free, needs no card and documents 185 methods on one page with a dated changelog and numeric send limits. No OpenAPI document, status page, SLA or idempotency key was found, one token controls the whole bot and travels in the URL, and a person must create the bot in a chat with @BotFather.",
        "bestFor": "An agent that talks to people who use Telegram, with free sends and long polling that needs no public server.",
        "strengths": [
          "Free to use with no card. Limits are published as numbers, about one message a second per chat, 20 a minute in a group and about 30 a second in bulk",
          "Flood errors return HTTP 429 with `retry_after` in the response `parameters`, and the open-source server sets a `Retry-After` header",
          "Inbound messages arrive by `getUpdates` long polling with no public server, or by webhook with a `secret_token` echoed in `X-Telegram-Bot-Api-Secret-Token`",
          "The Bot API server is open source under BSL-1.0 in tdlib/telegram-bot-api, at version 10.3, and can be self-hosted for larger files",
          "A dated changelog covers every version, and the server source still accepts `receiver_user_id` and `correct_option_id` after the changelog said they were replaced"
        ],
        "weaknesses": [
          "No OpenAPI document, llms.txt or official SDK was found. The contract is one HTML reference page of about 860 KB",
          "One token gives full control of the bot, sits in the URL path of every request, and has no scopes or read-only form",
          "No status page, SLA or incident history was found, and the developer terms disclaim uptime and allow changes without notice",
          "No idempotency key exists for sends, and `error_code` contents are described as subject to change with no published error catalogue",
          "A person with a Telegram account must create the bot in a chat with @BotFather, and a bot cannot message a user who has not started it",
          "Developer terms section 4.3 prohibits collecting data for large datasets, machine learning models and AI products. Recorded as a fact, and it matters before any probe is run"
        ],
        "agentNotes": [
          "Send `POST https://api.telegram.org/bot\u003ctoken\u003e/sendMessage` with `chat_id` and `text`. Keep the token out of logs, because it is part of the URL.",
          "On HTTP 429 wait the `parameters.retry_after` seconds before retrying. Stay under one message a second per chat and 20 a minute per group.",
          "Call `getUpdates` with `offset` set to the last `update_id` plus one, or the same updates return. Updates are kept for at most 24 hours.",
          "A retried send can post twice, as there is no idempotency key. Record the returned `message_id` before retrying after a timeout.",
          "In groups the bot sees only commands and replies unless privacy mode is disabled in @BotFather or the bot is an admin."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 43
          }
        ],
        "editorialScores": {
          "ergonomics": 48,
          "maintenance": 38,
          "payments": 40,
          "reliability": 40,
          "schema": 44,
          "security": 35,
          "transparency": 53
        },
        "provenanceScore": 74
      },
      "connect": {
        "http": "curl https://api.telegram.org/bot\u003ctoken\u003e/getMe"
      },
      "letme": {
        "capability": "https://letme.dev/messaging.inbound",
        "tool": "https://letme.dev/telegram-bot"
      },
      "area": "communication",
      "provenance": {
        "legalEntity": "Telegram Messenger Inc.",
        "domain": "telegram.org",
        "domainRegistered": "2003-12-15",
        "endpointOnVendorDomain": true,
        "terms": "https://telegram.org/tos/bot-developers",
        "privacy": "https://telegram.org/privacy",
        "statusPage": "",
        "changelog": "https://core.telegram.org/bots/api-changelog",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The Bot Platform Developer Terms of Service name Telegram Messenger Inc. as the contracting party and incorporate the Telegram Terms of Service and Privacy Policy. The page carries no date.",
          "The privacy policy names Telegram Messenger Inc. as controller, Telegram Group Inc and Telegraph Inc. in the British Virgin Islands and Telegram FZ-LLC in Dubai as group recipients, and EDPO as EEA representative. Its last listed change is 29 September 2024.",
          "The API answers at api.telegram.org and the docs at core.telegram.org, both telegram.org subdomains.",
          "telegram.org/.well-known/security.txt returns 404, and core.telegram.org/.well-known/security.txt and telegram.org/security.txt return ordinary web pages. The bug bounty page at core.telegram.org/bug-bounty takes reports at security@telegram.org.",
          "Neither core.telegram.org nor telegram.org serves a robots.txt (404 on both).",
          "No status page was found.",
          "RDAP for telegram.org gives a registration date of 2003-12-15."
        ],
        "score": 74
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/telegram-bot.json",
      "live": {
        "slug": "telegram-bot",
        "probe": {
          "target": "https://api.telegram.org",
          "method": "get",
          "lastAt": "2026-10-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": "Round One, Inc.",
        "b": "Telegram Messenger Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://api.sendblue.com",
        "b": "https://api.telegram.org",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, stdio",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Free",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is 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": "18",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-07",
        "b": "2026-08-24",
        "name": "Last release"
      },
      {
        "a": "2025-03-19",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2024-05-01",
        "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": "250k npm/wk, 40k PyPI/wk",
        "b": "4.5k stars",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Sendblue scores 61.7 (C) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on transparency \u0026 trust.",
        "question": "Which is better for AI agents, Sendblue or Telegram Bot API?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Sendblue and Telegram Bot API need an API key?"
      },
      {
        "answer": "Yes. Sendblue has a hosted endpoint at https://api.sendblue.com and Telegram Bot API at https://api.telegram.org.",
        "question": "Can an agent call Sendblue and Telegram Bot API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 71 against 40",
          "Schema \u0026 documentation, 66 against 44",
          "Agent ergonomics, 76 against 48",
          "Security \u0026 auth, 46 against 35",
          "Maintenance \u0026 community, 72 against 38"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.",
        "slug": "sendblue",
        "watchFor": "Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first"
      },
      {
        "aheadOn": [
          "Transparency \u0026 trust, 64 against 58"
        ],
        "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-sendblue.json",
        "title": "AWS End User Messaging vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/bird-vs-sendblue.json",
        "title": "Bird API + MCP vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/bird-vs-sendblue"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clicksend-vs-sendblue.json",
        "title": "ClickSend SMS API + MCP vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/clicksend-vs-sendblue"
      },
      {
        "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/plivo-vs-sendblue.json",
        "title": "Plivo API vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/plivo-vs-sendblue"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-sinch.json",
        "title": "Sendblue vs Sinch Messaging APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-sinch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-telnyx.json",
        "title": "Sendblue vs Telnyx API + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-telnyx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-twilio.json",
        "title": "Sendblue vs Twilio API + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-twilio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sendblue-vs-vonage.json",
        "title": "Sendblue vs Vonage Messages API + MCP",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-vonage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/360dialog-vs-sendblue.json",
        "title": "360dialog WhatsApp API + MCP vs Sendblue",
        "url": "https://www.anchorterminal.com/compare/360dialog-vs-sendblue"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/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-whatsapp-cloud-api.json",
        "title": "Sendblue vs WhatsApp Business Platform (Cloud API)",
        "url": "https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api"
      },
      {
        "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": [
      {
        "by": 31,
        "edge": "sendblue",
        "key": "reliability",
        "name": "Reliability",
        "sendblue": 71,
        "telegram-bot": 40,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 22,
        "edge": "sendblue",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "sendblue": 66,
        "telegram-bot": 44,
        "weight": 13
      },
      {
        "by": 28,
        "edge": "sendblue",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "sendblue": 76,
        "telegram-bot": 48,
        "weight": 13
      },
      {
        "by": 11,
        "edge": "sendblue",
        "key": "security",
        "name": "Security \u0026 auth",
        "sendblue": 46,
        "telegram-bot": 35,
        "weight": 14
      },
      {
        "by": 0,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "sendblue": 40,
        "telegram-bot": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 34,
        "edge": "sendblue",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "sendblue": 72,
        "telegram-bot": 38,
        "weight": 7
      },
      {
        "by": 6,
        "edge": "telegram-bot",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "sendblue": 58,
        "telegram-bot": 64,
        "weight": 7
      }
    ],
    "summary": "Sendblue scores 61.7 (C) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on transparency \u0026 trust. Both do inbound messaging.",
    "verdicts": {
      "sendblue": "Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.",
      "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/sendblue-vs-telegram-bot",
    "json": "https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.md",
    "slim": "https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.min.md"
  },
  "markdown": "Sendblue scores 61.7 (C) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on transparency \u0026 trust. Both do inbound messaging.\n\n- Sendblue: grade C, 61.7/100, rank #458 of 950. Markdown https://www.anchorterminal.com/tools/sendblue.md · JSON https://www.anchorterminal.com/api/v1/tools/sendblue.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### Sendblue (C)\n\nGood for: An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.\n\nAhead on:\n- Reliability, 71 against 40\n- Schema \u0026 documentation, 66 against 44\n- Agent ergonomics, 76 against 48\n- Security \u0026 auth, 46 against 35\n- Maintenance \u0026 community, 72 against 38\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first\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- Transparency \u0026 trust, 64 against 58\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 | Sendblue | Telegram Bot API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 40 | Sendblue +31 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 44 | Sendblue +22 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 48 | Sendblue +28 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 35 | Sendblue +11 |\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) | 72 | 38 | Sendblue +34 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 64 | Telegram Bot API +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.7 · C** | **43 · E** | |\n\n## Facts side by side\n\n| Fact | Sendblue | Telegram Bot API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Round One, Inc. | Telegram Messenger Inc. |\n| Hosted endpoint | `https://api.sendblue.com` | `https://api.telegram.org` |\n| Transports | HTTP, stdio | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is 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| Tools exposed | 18 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-07 | 2026-08-24 |\n| Terms last updated | 2025-03-19 | no date given |\n| Privacy policy last updated | 2024-05-01 | 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 | 250k npm/wk, 40k PyPI/wk | 4.5k stars |\n\n## Verdicts\n\n**Sendblue.** Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.\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### Sendblue\n\n1. Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails\n2. On the free plan a recipient must text the Sendblue number once before any message to them is accepted\n3. Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six\n4. Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting\n5. Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied\n6. Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context\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, Sendblue or Telegram Bot API?\n\nSendblue scores 61.7 (C) on agent readiness against Telegram Bot API's 43 (E), and leads in 5 of 7 scored categories. Telegram Bot API leads on transparency \u0026 trust.\n\n### Do Sendblue and Telegram Bot API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Sendblue and Telegram Bot API without installing anything?\n\nYes. Sendblue has a hosted endpoint at https://api.sendblue.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/sendblue-vs-telegram-bot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"sendblue\", \"b\": \"telegram-bot\"}`. From a terminal: `anchor compare sendblue telegram-bot`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sendblue.json and https://www.anchorterminal.com/api/v1/tools/telegram-bot.json\n\n## Other comparisons with Sendblue or Telegram Bot API\n\n- [AWS End User Messaging vs Sendblue](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.md)\n- [Bandwidth Messaging API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bandwidth-vs-sendblue.md)\n- [Bird API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bird-vs-sendblue.md)\n- [ClickSend SMS API + MCP vs Sendblue](https://www.anchorterminal.com/compare/clicksend-vs-sendblue.md)\n- [Infobip API + MCP vs Sendblue](https://www.anchorterminal.com/compare/infobip-vs-sendblue.md)\n- [Plivo API vs Sendblue](https://www.anchorterminal.com/compare/plivo-vs-sendblue.md)\n- [Sendblue vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/sendblue-vs-sinch.md)\n- [Sendblue vs Telnyx API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-telnyx.md)\n- [Sendblue vs Twilio API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-twilio.md)\n- [Sendblue vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Sendblue](https://www.anchorterminal.com/compare/360dialog-vs-sendblue.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- [Plivo API vs Telegram Bot API](https://www.anchorterminal.com/compare/plivo-vs-telegram-bot.md)\n- [Sendblue vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api.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": "Sendblue vs Telegram Bot API",
        "url": ""
      }
    ],
    "description": "Sendblue scores 61.7 (C) to Telegram Bot's 43 (E) for inbound messaging. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Sendblue C 61.7",
      "Telegram Bot API E 43",
      "scores"
    ],
    "h1": "Sendblue vs Telegram Bot API",
    "image": "https://www.anchorterminal.com/assets/og/compare-sendblue-vs-telegram-bot.png",
    "path": "/compare/sendblue-vs-telegram-bot",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Sendblue vs Telegram Bot for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot"
  },
  "tokens": {
    "markdown": 2650,
    "slim": 730
  },
  "version": 1
}