# Kudosity vs Telegram Bot API (slim)

> Kudosity scores 63.7 (B) to Telegram Bot's 43 (E) for inbound messaging. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kudosity-vs-telegram-bot.md (~4,650 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/kudosity-vs-telegram-bot.json · canonical https://www.anchorterminal.com/compare/kudosity-vs-telegram-bot
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Kudosity scores 63.7 (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 & pricing. Both do inbound messaging.

- Kudosity: B 63.7, rank #505 of 1510 · https://www.anchorterminal.com/tools/kudosity.min.md
- Telegram Bot API: E 43, rank #1261 of 1510 · https://www.anchorterminal.com/tools/telegram-bot.min.md
- Kudosity, good for Agents sending SMS in Australia, New Zealand and the UK, and WhatsApp templates, from one account. Ahead on Reliability, 85 against 40; Schema & documentation, 86 against 44; Agent ergonomics, 73 against 48; Maintenance & community, 57 against 38. Also Runs on your own machine; Free to start without a card.
- Telegram Bot API, good for An agent that talks to people who use Telegram, with free sends and long polling that needs no public server. Ahead on Payments & pricing, 40 against 32.

| Category | Kudosity | Telegram Bot API |
| --- | --- | --- |
| Reliability (16%) | 85 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 44 |
| Agent ergonomics (13%) | 73 | 48 |
| Security & auth (14%) | 37 | 35 |
| Payments & pricing (10%) | 32 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 38 |
| Transparency & trust (7%) | 62 | 64 |

| Fact (where they differ) | Kudosity | Telegram Bot API |
| --- | --- | --- |
| Vendor | Known Pty Ltd (Kudosity) | Telegram Messenger Inc. |
| Hosted endpoint | `https://api.transmitmessage.com` | `https://api.telegram.org` |
| Transports | HTTP, stdio | HTTP |
| Pricing | Pay per use | Free |
| Licence | Proprietary service under Known Pty Ltd's terms and conditions. The `kudosity-mcp` server 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 |
| Tools exposed | 19 | none |
| llms.txt | yes | no |
| MCP registry | `com.kudosity/mcp` | not listed |
| Last release | 2026-07-27 | 2026-08-24 |
| Terms last updated | 2026-09-23 | no date given |
| Privacy policy last updated | 2024-08-08 | 2024-06-01 |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 40 npm/wk | 4.5k stars |
| Agent reviews | none | 3.8/5 (4) |

Why the edge:
- Reliability, Kudosity +45: Kudosity 85 (Read with the hosted lines. status.transmitsms.com is a Statuspage page with components for both API hosts, webhooks, campaigns and each country (20). Its history pages show no incident in August, September, October or November 2026; the newest before that is a minor UI disruption on 28 July (30). 15 calls a second per account, documented (15). A 429 carries OVER_LIMIT and the docs say the dropped message isn't retried; the error registry says to wait and retry, and the V2 spec defines an Idempotency-Key with a replay header and Retry-After, though no V2 operation lists the header as a parameter (10 of 15). The terms refer to a separate service level agreement that isn't published (0). SMS, MMS and WhatsApp on V2 are generally available; RCS is marked beta (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.); Telegram Bot API 40 (Graded on the hosted API at api.telegram.org, with the hosted lines. No status page was found on core.telegram.org or telegram.org (0). With no readable incident history the record line takes the floor (5). Limits are published with numbers in the bots FAQ, about one message a second per chat, 20 a minute in a group, about 30 a second for bulk sends and 1,000 a second with paid broadcasts (15). Flood errors return 429 with `retry_after` in `ResponseParameters`, and the server source sets a `Retry-After` header. No idempotency key exists for sends (10). No SLA was found, and section 12.3 of the developer terms disclaims uptime and availability (0). The API is generally available at version 10.3 (10).)
- Schema & documentation, Kudosity +42: Kudosity 86 (OpenAPI 3.0.3 files for V2 (16 paths, 23 operations) and V1 are public on developers.kudosity.com, and the MCP tools have typed zod inputs (25). llms.txt per section and a Markdown twin of every page (10). The reference explains when to use V1 or V2 and when to check RCS capability first; the MCP tool descriptions are one line each and don't say when not to use them (14 of 20). Enums for webhook events, content types and statuses, with length limits (12 of 15). Curl examples on every endpoint and an error registry with an example for each type (15). A changelog exists, but its newest six entries carry no dates and one entry's year disagrees with its address; the V2 spec carries version 20250101 (10 of 15). 25 + 10 + 14 + 12 + 15 + 10 = 86.); Telegram Bot API 44 (No OpenAPI document or other machine-readable contract is published by Telegram (0). core.telegram.org/llms.txt answers with a not-found page and no Markdown copy of the docs was found (0). Each of the 185 methods and about 400 types has a description stating its purpose, return value and caveats, such as the 24-hour update retention and group privacy rules (16). Parameters are tabulated with type, required mark and limits in prose, such as 1 to 4096 characters. Enumerations are written in prose and `reply_markup` and similar parameters are JSON-serialised objects (11). Few request examples, and no error catalogue. The reference says `error_code` contents are subject to change (5). Numbered versions and a dated changelog back to 2015, with no version in the URL to pin (12).)
- Agent ergonomics, Kudosity +25: Kudosity 73 (19 compact MCP tools, including four that look up endpoints in the live specs instead of loading them, with no toolsets or read-only subset; V2 list calls take limits and date presets (17 of 25). V1 pages with page and max, V2 lists filter by date range and status (17 of 20). Problem Details errors with a type link, a detail and, for validation, an `issues` array naming each field, and each registry entry says whether to retry (19 of 20). Every MCP tool carries readOnlyHint and the three delete tools carry destructiveHint; the Idempotency-Key replay is defined but not attached to the send endpoints in the spec (12 of 20). A send needs three fields. Official packages are the MCP server and LangChain.js tools, both JavaScript, with no SDK in a second language (8 of 15). 17 + 17 + 19 + 12 + 8 = 73.); Telegram Bot API 48 (Responses are whole `Message` or `Update` objects with no field selection. `getUpdates` takes `limit` (1 to 100) and `allowed_updates` to narrow what arrives (12). `getUpdates` pages by `offset`, with `limit`, `timeout` and `allowed_updates`. A bot cannot list or search past messages in a chat (12). Errors carry `ok`, `error_code`, `description` and optional `parameters` with `retry_after` or `migrate_to_chat_id`. Descriptions are free text with no published list (10). No idempotency key for sends. `update_id` lets a receiver discard repeated inbound updates (5). `sendMessage` needs two parameters, GET and POST both work with four parameter encodings, and long polling needs no public server. No official SDK was found (9).)
- Maintenance & community, Kudosity +19: Kudosity 57 (`kudosity-mcp` 0.5.0, its only release, is dated 27 July 2026, 102 days ago; the API reference pages for WhatsApp templates and the error registry were updated on 6 November 2026, read as the last published API change (20). The changelog's six newest entries carry no dates. Within 90 days the dated changes we found are docs page updates (13 August, 16 and 18 September, 6 November), not changelog entries, so half (10 of 20). Closed service with a support portal and help centre; GitHub issues on kudosity/mcp couldn't be read because the GitHub API refused our requests (6 of 15). `com.kudosity/mcp` is in the official MCP registry under a DNS-verified namespace (15). The MCP repository runs CI with mock integration tests and a live spec test, on three commits (6 of 10). 20 + 10 + 6 + 15 + 6 = 57.); Telegram Bot API 38 (Closed service with an open-source server. The newest dated API change is Bot API 10.3 on 24 August 2026, 46 days before the check (20). Two dated changelog entries fall in the 90 days to 9 October 2026, 10.2 on 14 July and 10.3 on 24 August, so the three-entry line isn't met (0). A changelog, the @BotNews and @BotTalk channels and @BotSupport exist. tdlib/telegram-bot-api has 74 open issues, and we did not read how quickly they are answered (8). No official SDK was found. The official server source is current at 10.3 (5). The server repository had 44 commits between 11 July and 25 August 2026 and has no public CI configuration (5).)
- Payments & pricing, Telegram Bot API +8: Kudosity 32 (No x402, MPP or L402 (0). SMS is priced per part without login, 8.0 cents AUD ex GST pay as you go; MMS, RCS and WhatsApp are on request (12 of 20). A 14-day developer trial whose form asks for no card (20). A person signs up in a browser and verifies by email (0). 0 + 12 + 20 + 0 = 32.); Telegram Bot API 40 (No x402, MPP or L402 in the reference, the FAQ, the developer terms or the server source (0). The API is free, stated without a login, and the one fee found is 0.1 Stars per broadcast message above 30 a second, for bots with 100,000 Stars and 100,000 monthly users (20). No card or payment method is needed to create a bot and send (20). A person with a Telegram account, which needs a phone number, must create the bot in a chat with @BotFather. Managed bots also need a user to confirm in a Telegram client (0).)