# 360dialog WhatsApp API + MCP vs Kudosity (slim)

> Kudosity scores 63.7 (B) to 360dialog WhatsApp's 50.5 (D) for whatsapp messaging. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/360dialog-vs-kudosity.md (~4,850 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/360dialog-vs-kudosity.json · canonical https://www.anchorterminal.com/compare/360dialog-vs-kudosity
- 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 360dialog WhatsApp API + MCP's 50.5 (D), and leads in 6 of 7 scored categories. Both do whatsapp messaging.

- 360dialog WhatsApp API + MCP: D 50.5, rank #1047 of 1486 · https://www.anchorterminal.com/tools/360dialog.min.md
- Kudosity: B 63.7, rank #503 of 1486 · https://www.anchorterminal.com/tools/kudosity.min.md
- 360dialog WhatsApp API + MCP, good for WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.
- Kudosity, good for Agents sending SMS in Australia, New Zealand and the UK, and WhatsApp templates, from one account. Ahead on Reliability, 85 against 75; Schema & documentation, 86 against 70; Agent ergonomics, 73 against 53; Maintenance & community, 57 against 8; Transparency & trust, 62 against 49. Also Runs on your own machine; Free to start without a card.

| Category | 360dialog WhatsApp API + MCP | Kudosity |
| --- | --- | --- |
| Reliability (16%) | 75 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 86 |
| Agent ergonomics (13%) | 53 | 73 |
| Security & auth (14%) | 35 | 37 |
| Payments & pricing (10%) | 35 | 32 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 8 | 57 |
| Transparency & trust (7%) | 49 | 62 |

| Fact (where they differ) | 360dialog WhatsApp API + MCP | Kudosity |
| --- | --- | --- |
| Vendor | 360dialog | Known Pty Ltd (Kudosity) |
| Hosted endpoint | `https://waba-v2.360dialog.io` | `https://api.transmitmessage.com` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Licence | none | Proprietary service under Known Pty Ltd's terms and conditions. The `kudosity-mcp` server is MIT |
| Tools exposed | none | 19 |
| MCP registry | not listed | `com.kudosity/mcp` |
| Last release | none | 2026-07-27 |
| Terms last updated | couldn't be read | 2026-09-23 |
| Privacy policy last updated | 2026-09-10 | 2024-08-08 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 40 npm/wk |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Kudosity +49: 360dialog WhatsApp API + MCP 8 (No changelog or release notes found. The Usernames and BSUID page dates Meta's rollout of business-scoped user IDs by month (in webhooks March to April 2026, Meta's Contact Book April 2026, sending from early July 2026), and the Messages reference, which follows Meta's Cloud API payloads, carries the `recipient` field for it. These are Meta's Cloud API changes carried through 360dialog's proxy, not a dated change 360dialog made to its own API, so they don't set recency (0, as on 1 October). No dated API change since 6 August. The marketing message price cap ("Open Beta since 1 October 2026") is a beta and doesn't count, and Direct Send's move to general availability carries no date (0). Closed service with a support response-time page and no public changelog (8 of 15). No official SDKs (0). No packages to assess (0). 0+0+8+0+0 = 8.); 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.)
- Agent ergonomics, Kudosity +20: 360dialog WhatsApp API + MCP 53 (Responses follow Meta's Cloud API shapes. GET /message_templates takes a `fields` list for field selection and a `limit` (18 of 25). Cursor pagination with `after` and `before` and next and previous links on the template list. We checked that list only (15 of 20). Error codes with resolution steps an agent can act on (15 of 20). No idempotency key found, and the MCP docs don't mention tool annotations (0 of 20). No official SDKs. A send needs only the D360-API-KEY header and a Cloud API message body (5 of 15).); 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.)
- Schema & documentation, Kudosity +16: 360dialog WhatsApp API + MCP 70 (The Markdown reference pages embed an OpenAPI 3.1.0 document titled Messaging API, version 1.52.4 on 4 November (1.50.7 on 2 October), with a D360-API-KEY header scheme and response schemas. We read the Templates section in full. We found no standalone download, so an agent has to collect it page by page (20 of 25). llms.txt listing 305 pages, a .md version of every page and an ?ask= query parameter that answers questions (10). API reference pages describe endpoints and parameters, mostly following Meta's Cloud API payloads (12 of 20). Typed query parameters and response schemas in the spec, with enums not checked (10 of 15). More than 60 error codes, each with a suggested fix (13 of 15). The spec carries a version number and flags the legacy /v1/configs template endpoints as deprecated, but we found no changelog (5 of 15).); 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.)
- Transparency & trust, Kudosity +13: 360dialog WhatsApp API + MCP 49 (Closed service with terms of use in the Hub (15). The privacy policy covers the website, names 360dialog GmbH in Grünwald and was updated on 10 September 2026. The Legal Information page links two English DPA files we didn't open, and the docs say the Cloud API keeps messages for at most 30 days, but we found no sub-processor list for the service (15 of 30). No deprecation policy. The OpenAPI flags deprecated template endpoints without dates (5 of 20). Website trackers are listed with locations, but service sub-processors and hosting locations aren't (0 of 20).); 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.)
- Reliability, Kudosity +10: 360dialog WhatsApp API + MCP 75 (Status page at status.360dialog.com on Instatus, with 10 360dialog components, 3 Meta ones and subscriptions (20). In the 90 days from 6 August the page posts one incident, "Some disruptions to Messaging" from 16 October 17:12 to 17 October 07:11 UTC (13 hours 59 minutes), with customers reporting authorisation errors on sends after Meta changed messaging permissions on one of 360dialog's applications, worked around the same day. Read as partial by its label and scope (minor, 20); as a major outage the line would be 10. August, September and November show no notices. Throughput is published, up to 80 messages a second on standard plans and 1,000 on the Higher Throughput tier (15). The error list maps the endpoint rate-limit error to request throttling or exponential backoff, with no Retry-After and no idempotency key for sends, so backoff guidance alone (10, this run's settled value for that reading; 8 on 1 October). No SLA. The support page sets first-response targets and nothing commits to uptime (0, per the 2 October check). The Messaging API is generally available (10). 20+20+15+10+0+10 = 75.); 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.)