# Kudosity vs Telnyx API + MCP (slim)

> Telnyx scores 75.3 (BB) to Kudosity's 63.7 (B) for sms. Telnyx is cheaper for sms, $0.004 against $0.055 per message. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kudosity-vs-telnyx.md (~5,300 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/kudosity-vs-telnyx.json · canonical https://www.anchorterminal.com/compare/kudosity-vs-telnyx
- 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)

Telnyx API + MCP scores 75.3 (BB) on agent readiness against Kudosity's 63.7 (B), and leads in 6 of 7 scored categories. Kudosity leads on reliability. Both do sms. Telnyx API + MCP is cheaper for sms, $0.004 against $0.055 per message.

- Kudosity: B 63.7, rank #503 of 1486 · https://www.anchorterminal.com/tools/kudosity.min.md
- Telnyx API + MCP: BB 75.3, rank #68 of 1486 · https://www.anchorterminal.com/tools/telnyx.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 80. Also Free to start without a card.
- Telnyx API + MCP, good for Cost-sensitive US SMS and for agents that must onboard and pay without a person. Ahead on Schema & documentation, 93 against 86; Agent ergonomics, 90 against 73; Security & auth, 45 against 37; Payments & pricing, 65 against 32; Maintenance & community, 83 against 57; Transparency & trust, 72 against 62. Also Cheaper for sms, $0.004 against $0.055 per message; Agent-ready, a grade of BB or better.

| Category | Kudosity | Telnyx API + MCP |
| --- | --- | --- |
| Reliability (16%) | 85 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 93 |
| Agent ergonomics (13%) | 73 | 90 |
| Security & auth (14%) | 37 | 45 |
| Payments & pricing (10%) | 32 | 65 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 83 |
| Transparency & trust (7%) | 62 | 72 |

| Fact (where they differ) | Kudosity | Telnyx API + MCP |
| --- | --- | --- |
| Vendor | Known Pty Ltd (Kudosity) | Telnyx |
| Hosted endpoint | `https://api.transmitmessage.com` | `https://api.telnyx.com/v2` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Price for sms | $0.055 per message | $0.004 per message |
| x402 | no | payer tooling only |
| Licence | Proprietary service under Known Pty Ltd's terms and conditions. The `kudosity-mcp` server is MIT | MIT |
| Tools exposed | 19 | 3 |
| MCP registry | `com.kudosity/mcp` | `io.github.team-telnyx/telnyx` |
| Last release | 2026-07-27 | 2026-10-28 |
| Terms last updated | 2026-09-23 | no date given |
| Privacy policy last updated | 2024-08-08 | 2026-03-01 |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 40 npm/wk | 197 stars, 417k npm/wk, 179k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Payments & pricing, Telnyx API + MCP +33: 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.); Telnyx API + MCP 65 (x402 exists on Telnyx's own API at /v2/x402/credit_account (USDC on Base), with MPP at /v2/machine-payments/account-credit (Stripe Link or Tempo USDC), but both top up account credit rather than pay per message. Telnyx's x402 skill says x402 sits behind an account feature flag (403 when it's off) and that per-payment minimum and maximum limits are configurable and stated in 422 errors; the MPP skill names no flag (25 of 40). Per-part SMS and MMS rates and carrier passthrough fees are published without a login, also as pricing.md (20). No free credit, a new account starts at zero (0). An agent can sign up through /v2/bot_challenge and /v2/bot_signup, confirm by a magic link sent to a mailbox it can read, mint a key at /v2/api_keys and fund the account by MPP or x402 with no browser (20).)
- Maintenance & community, Telnyx API + MCP +26: 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.); Telnyx API + MCP 83 (telnyx-node v7.29.0 and telnyx-python v4.190.0 both tagged on 2026-10-28 (30). 17 telnyx-node releases in the 90 days to 1 November, from v7.13.0 on 4 August to v7.29.0, and 20 telnyx-python tags in the same window, with dated release notes up to 30 October 2026, messaging entries among them on 26 October (MM7 gateway for MMS) and 29 October (automatic SMS chunking) (20). Closed service with public release notes and a support channel. We couldn't read GitHub issue replies (8 of 15). Current official SDKs. The MCP is in the official registry as io.github.team-telnyx/telnyx, though that entry still stops at 6.29.3 from March 2026 (15). Release automation runs in CI (10). 30 + 20 + 8 + 15 + 10 = 83.)
- Agent ergonomics, Telnyx API + MCP +17: 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.); Telnyx API + MCP 90 (List endpoints take page size and number, with no field selection. The hosted MCP lists 6 tools on 1 November (3 meta-tools that load endpoint schemas on demand and 3 read-only MCP App launchers), but we scored the API (15 of 25). Filters on message and number lists (20). JSON errors with a code, title and detail, and a documented code list (20). POST /v2/messages now declares an optional Idempotency-Key header in its reference, and so do the seven other send endpoints in the OpenAPI file (long code, short code, number pool, alphanumeric sender ID, group MMS, RCS and WhatsApp). Scheduled sends (POST /v2/messages/schedule) and account writes such as messaging profiles and number orders take none. That is the coverage the Telnyx Voice API listing earns 20 for, where command_id is on 38 of 40 call commands. Only successful responses are replayed, for up to 24 hours, a key still in progress returns 409 and a key reused with a different request returns 422. The Node SDK carries it from v7.27.0 (21 October 2026), where 17 October found none (20). A send needs from or a messaging profile, to and text. Official SDKs in Node, Python and more (15). 15 + 20 + 20 + 20 + 15 = 90.)
- Transparency & trust, Telnyx API + MCP +10: Kudosity 62 (Closed service with clear terms from Known Pty Ltd (23 September 2026); the MCP server is MIT (17 of 30). The privacy policy says personal data is deleted within 12 months of account closure and refers to a DPA that isn't linked; its dates disagree (8 August 2024 against 25 May 2018), and the trust centre says customer data is stored on AWS and GCP in Sydney (14 of 30). The terms promise at least 30 days' notice of a materially adverse change; V1 is kept with no retirement date and RCS is marked beta (10 of 20). Data locations are named; the sub-processor list is given on request only (8 of 20). 17 + 14 + 10 + 8 = 49.); Telnyx API + MCP 72 (Closed service with clear terms (15). Privacy policy (last updated effective 1 March 2026, read on 17 October, not re-read on 1 November) covering retention as long as reasonably necessary, a Telnyx DPA referenced from the sub-processor page, and about 50 sub-processors. We didn't find stated retention periods for message records (25 of 30). No deprecation policy or dated deprecation notices found, and the release notes read on 1 November carry none (0 of 20). Each sub-processor is listed with its entity, address, products and data categories, with change alerts, per the 6 October check (15 of 20).)
- Security & auth, Telnyx API + MCP +8: Kudosity 37 (One account-wide API key on V2 and Basic auth with the key and a secret the user types in on V1, both in headers. No scopes, read-only keys or rotation steps were found (12 of 30). No least-privilege mode. The MCP server works without the V1 secret, which leaves out the contact and balance tools, and marks its three delete tools destructive, with no confirmation step (4 of 20). Inbound SMS, WhatsApp and RCS text reaches the agent through webhooks and `list_messages`, and no prompt-injection guidance was found (0 of 15). Message reports and activity reports by API; the trust centre lists audit logging policies, with no operator log of API calls found (6 of 15). ISO/IEC 27001:2022 and SOC 2 Type 2 stated on kudosity.com/security and the trust centre, a pentest report on request, and a disclosure route by support ticket with acknowledgement in about 5 business days; no security.txt or bug bounty (15 of 20). 12 + 4 + 0 + 6 + 15 = 37.); Telnyx API + MCP 45 (Bearer API keys created and revoked in the portal, with no per-key scopes found. Claude connectors can authorise through the portal instead, and the OAuth authorisation-server metadata, re-read on 1 November, still lists 32 product scopes such as messaging.read, messaging.write and numbers.write, but no document says how a client picks them or that a token is held to them, so the line stays at plain revocable keys (20). No read-only key mode found. The hosted MCP's invoke_api_endpoint carries destructiveHint true but can send messages or buy numbers with no confirmation step on Telnyx's side (0 of 20). Inbound SMS and WhatsApp bodies are untrusted text. Messaging webhooks are signed, and we found no prompt-injection guidance (5 of 15). Message and detail records by API, with no account audit log found (10 of 15). SOC 2 Type II and ISO 27001 per Telnyx's compliance file, and telnyx-node has a SECURITY.md with a reporting route. security.txt returned 404 at both locations on 1 November and no bug bounty found (10 of 20). 20 + 0 + 5 + 10 + 10 = 45.)
- Schema & documentation, Telnyx API + MCP +7: 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.); Telnyx API + MCP 93 (Public OpenAPI 3 spec in the team-telnyx/openapi repository (25). llms.txt on developers.telnyx.com and telnyx.com, Markdown doc pages and a pricing.md (10). One reference page per endpoint with purpose and parameters, with little on when not to use one (15 of 20). Typed JSON bodies with enums (13 of 15). Request examples and a page of API error codes (15). Versioned /v2 path and public release notes (15).)