# Kudosity vs Plivo API (slim)

> Kudosity and Plivo score within a point of each other for sms, 63.7 and 63.6 out of 100. Plivo is cheaper for sms, $0.0077 against $0.055 per message. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kudosity-vs-plivo.md (~4,750 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/kudosity-vs-plivo.json · canonical https://www.anchorterminal.com/compare/kudosity-vs-plivo
- 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 and Plivo API score within a point of each other on agent readiness, 63.7 (B) and 63.6 (B). Plivo API leads on reliability, security & auth, payments & pricing, maintenance & community and transparency & trust. Both do sms. Plivo API is cheaper for sms, $0.0077 against $0.055 per message.

- Kudosity: B 63.7, rank #505 of 1510 · https://www.anchorterminal.com/tools/kudosity.min.md
- Plivo API: B 63.6, rank #508 of 1510 · https://www.anchorterminal.com/tools/plivo.min.md
- Kudosity, good for Agents sending SMS in Australia, New Zealand and the UK, and WhatsApp templates, from one account. Ahead on Schema & documentation, 86 against 59; Agent ergonomics, 73 against 57. Also Runs on your own machine.
- Plivo API, good for Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice. Ahead on Reliability, 90 against 85; Security & auth, 50 against 37; Payments & pricing, 40 against 32; Maintenance & community, 78 against 57; Transparency & trust, 71 against 62. Also Cheaper for sms, $0.0077 against $0.055 per message.

| Category | Kudosity | Plivo API |
| --- | --- | --- |
| Reliability (16%) | 85 | 90 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 59 |
| Agent ergonomics (13%) | 73 | 57 |
| Security & auth (14%) | 37 | 50 |
| Payments & pricing (10%) | 32 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 78 |
| Transparency & trust (7%) | 62 | 71 |

| Fact (where they differ) | Kudosity | Plivo API |
| --- | --- | --- |
| Vendor | Known Pty Ltd (Kudosity) | Plivo |
| Hosted endpoint | `https://api.transmitmessage.com` | `https://api.plivo.com/v1` |
| Transports | HTTP, stdio | HTTP |
| Price for sms | $0.055 per message | $0.0077 per message |
| Licence | Proprietary service under Known Pty Ltd's terms and conditions. The `kudosity-mcp` server is MIT | MIT |
| Tools exposed | 19 | none |
| MCP registry | `com.kudosity/mcp` | not listed |
| Last release | 2026-07-27 | 2026-10-28 |
| Terms last updated | 2026-09-23 | 2026-04-29 |
| Privacy policy last updated | 2024-08-08 | 2026-05-27 |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 40 npm/wk | 102 stars, 51k npm/wk, 69k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Schema & documentation, Kudosity +27: 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.); Plivo API 59 (No OpenAPI spec found (0). llms.txt at plivo.com/docs/llms.txt (10). Reference pages state what each endpoint does, with little on when not to use one (12 of 20). Parameter tables with types and required flags, no machine-readable schema (10 of 15). Examples in each SDK language. We didn't recheck the messaging error list this run (12 of 15). Versioned v1 path and a public changelog (15).)
- Maintenance & community, Plivo API +21: 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.); Plivo API 78 (plivo-cli v1.3.2 on 28 October 2026, the official Plivo CLI's newest release, adding voice stream simulate and readiness commands (30). In the 90 days from 6 August, 13 plivo-cli releases from v0.3.0 (28 August) to v1.3.2 (v1.3.1 was tagged but never released), plivo-go 7.61.0, plivo-java 5.51.0 and plivo-dotnet 5.53.0 (19 August, Caller Reputation parameters) and plivo-python v4.63.0 (25 September, an auto-pagination fix), well over three (20). The product changelog's newest entry is 6 January 2025. Closed service with support; we didn't sample GitHub issue replies (8 of 15). Official SDKs current in several languages (15). CI and dependency state not checked, and plivo-node hasn't released since 28 July (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.)
- Agent ergonomics, Kudosity +16: 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.); Plivo API 57 (List endpoints take limit and offset, with no field selection (15 of 25). Message list filters weren't rechecked this run (15 of 20). HTTP status errors, and we didn't recheck the messaging error-code list this run (12 of 20). No idempotency key or safe-retry guidance for sends found (0 of 20). Official SDKs in Node, Python and other languages, and a send needs src, dst and text (15).)
- Security & auth, Plivo API +13: 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.); Plivo API 50 (HTTP Basic auth with an Auth ID and Auth Token per account or subaccount, the Auth ID also in every path. No per-key scopes found (20). Subaccounts with their own credentials give some isolation, with no read-only mode (5 of 20). Inbound SMS and WhatsApp bodies are untrusted text. Webhooks are signed, and we found no prompt-injection guidance (5 of 15). Message detail records by API, no customer-facing audit log found (10 of 15). SOC 2 audited annually, PCI DSS Level 1 and HIPAA per the security page. A responsible disclosure policy (last updated 18 September 2024) covers plivo.com and Plivo's products and sends reports to security@plivo.com; the 1 October check missed it. No security.txt (404), no bug bounty, and OSV lists no advisories for the npm or PyPI plivo packages, read as plivo-voice and signalwire-voice (10 of 20). 20 + 5 + 5 + 10 + 10 = 50.)
- Transparency & trust, Plivo API +9: 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.); Plivo API 71 (Closed service with clear terms at plivo.com/legal/tos (15). Privacy policy, encryption at rest and in transit, and a sub-processor list. We didn't find a DPA or message-log retention periods (20 of 30). No deprecation policy or dated notices found (0). About 40 sub-processors listed with purpose and location (all USA), last updated 2025-08-13, with no change alerts (15 of 20).)
- Payments & pricing, Plivo 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.); Plivo API 40 (No x402, MPP or L402 (0). US per-message SMS and MMS prices, carrier surcharges by carrier and number rental are published without a login (20). Free credits with no card, per the pricing page (20). A person signs up in a browser and verifies a phone number (0).)