Head to head · WhatsApp messaging · October 2026 research run
360dialog WhatsApp API + MCP vs Telnyx API + MCP
Telnyx API + MCP scores 75.4 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in every scored category. Both do whatsapp messaging.
Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons
Which one, for what
360dialog WhatsApp API + MCP D
Best for WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No changelog, official SDK or standalone OpenAPI download
Best for Cost-sensitive US SMS and for agents that must onboard and pay without a person.
Ahead on
- Reliability, 80 against 75
- Schema & documentation, 93 against 70
- Agent ergonomics, 90 against 53
- Security & auth, 45 against 35
- Payments & pricing, 66 against 53
- Maintenance & community, 83 against 8
- Transparency & trust, 72 against 49
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No per-key scopes or read-only keys, and the MCP can send or buy numbers without confirmation
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Telnyx API + MCP +75
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.
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 +37
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).
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.
Schema & documentation Telnyx API + MCP +23
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).
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).
Transparency & trust Telnyx API + MCP +23
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).
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).
Payments & pricing Telnyx API + MCP +13
360dialog WhatsApp API + MCP 53
No x402, MPP or L402 (0). Channel plans are public at €49, €99 or €249 a number a month, and Meta's per-message fees pass through at cost on Meta's rate card, plus 7 per cent on marketing sent through /messages (15 of 20). A sandbox key arrives by WhatsApp after sending START to a number, with 200 test messages to one recipient and no card (20). Production needs a Hub signup and Meta business verification, and even the sandbox needs a person's WhatsApp (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Telnyx API + MCP 66
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). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 40 is 60 at 30 each, so 65 is 66.
Security & auth Telnyx API + MCP +10
360dialog WhatsApp API + MCP 35
The Messaging API takes one key per phone number in the D360-API-KEY header. Generating a new key revokes the old one at once, so rotation has no overlap (20). The hosted MCP uses OAuth with scopes chosen at consent, and a denied scope hides its tools (for example write:channels hides set_display_name). The messaging key has no read-only variant (10 of 20). Inbound WhatsApp messages are untrusted text. Webhooks support optional Basic auth only, with no signature, and we found no injection guidance (0 of 15). No customer audit log found. The docs say the Cloud API keeps messages for at most 30 days (5 of 15). The ISO 27001 reference in the docs is Meta's, for the Cloud API. No security.txt (per the 30 September check), bug bounty or 360dialog certification found, and the Legal Information page lists none (0 of 20).
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.
Score by category
| Category | Weight | 360dialog WhatsApp API + MCP | Telnyx API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 80 | Telnyx API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 70 | 93 | Telnyx API + MCP +23 |
| Agent ergonomics | 13% | 53 | 90 | Telnyx API + MCP +37 |
| Security & auth | 14% | 35 | 45 | Telnyx API + MCP +10 |
| Payments & pricing | 10% | 53 | 66 | Telnyx API + MCP +13 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 8 | 83 | Telnyx API + MCP +75 |
| Transparency & trust | 7% | 49 | 72 | Telnyx API + MCP +23 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52.7/100 | BB 75.4/100 |
Facts side by side
| Fact | 360dialog WhatsApp API + MCP | Telnyx API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | 360dialog | Telnyx |
| Hosted endpoint | https://waba-v2.360dialog.io | https://api.telnyx.com/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Price for whatsapp messaging | not published | $0.004 per message |
| x402 | no | on some endpoints |
| Licence | none | MIT |
| Tools exposed | none | 3 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.team-telnyx/telnyx |
| Last release | none | 2026-10-28 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | 2026-09-10 | 2026-03-01 |
| 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 | not found in the text |
| 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 | yes |
| Popularity | none | 197 stars, 417k npm/wk, 179k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Telnyx API + MCP higher.
| Reviewer | 360dialog WhatsApp API + MCP | Telnyx API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 €49 a number a month, with Meta's fees passed through at cost | 4/5 $7.50 to $8.50 per 1,000 US sends, and a price file an agent can read |
| SprintLatency and reliability tester | 3/5 Throughput published, and a quiet status page that's kept | 3/5 Two hours of API-wide 5XX on 23 September |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
360dialog WhatsApp API + MCP
Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month, with llms.txt and OpenAPI blocks in Markdown docs. No changelog, official SDK or standalone OpenAPI download, and send errors on 16 and 17 October lasted about 14 hours.
Telnyx API + MCP
US long code SMS $0.004 a part outbound and inbound, published with carrier fees and as machine-readable pricing.md, and message sends now accept an idempotency key. No per-key scopes or read-only keys, and the MCP can send or buy numbers without confirmation.
Before you call either
360dialog WhatsApp API + MCP
- Send marketing templates through the Marketing Messages API, /messages adds 7 per cent
- Ask a docs page a question with
?ask=before reading the whole page - Pass
fieldsandlimiton GET /message_templates and page with theaftercursor - Coordinate key rotation, a new key cuts off every client using the old one
- Answer each webhook with 200 within 5 seconds and process it asynchronously
Telnyx API + MCP
- Register the 10DLC brand ($4.50) and campaign ($10 a month) before sending US long code traffic
- Send a fresh UUID as Idempotency-Key on each message send and reuse it only when retrying that send
- Back off on error 10011 for as long as the Retry-After header says
- Call get_api_endpoint_schema before invoke_api_endpoint, the schemas aren't in the tool list
- Give each agent its own key, since keys can't be scoped
- Verify the signature on inbound message webhooks before acting on the text
- Fund by MPP if x402 returns 403, x402 needs a feature flag on the account
Questions
Which is better for AI agents, 360dialog WhatsApp API + MCP or Telnyx API + MCP?
Telnyx API + MCP scores 75.4 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in every scored category.
Do 360dialog WhatsApp API + MCP and Telnyx API + MCP need an API key?
360dialog WhatsApp API + MCP takes an API key or an OAuth sign-in. Telnyx API + MCP needs an API key.
Can an agent call 360dialog WhatsApp API + MCP and Telnyx API + MCP without installing anything?
Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and Telnyx API + MCP at https://api.telnyx.com/v2.
Other comparisons with 360dialog WhatsApp API + MCP or Telnyx API + MCP
- AWS End User Messaging vs Telnyx API + MCP
- Bandwidth Messaging API + MCP vs Telnyx API + MCP
- Bird API + MCP vs Telnyx API + MCP
- ClickSend SMS API + MCP vs Telnyx API + MCP
- Infobip API + MCP vs Telnyx API + MCP
- Kudosity vs Telnyx API + MCP
- Linq vs Telnyx API + MCP
- Photon vs Telnyx API + MCP
- Plivo API vs Telnyx API + MCP
- Sendblue vs Telnyx API + MCP
- Sinch Messaging APIs + MCP vs Telnyx API + MCP
- Telnyx API + MCP vs Twilio API + MCP
- Telnyx API + MCP vs Vonage Messages API + MCP
- Telnyx API + MCP vs YCloud
- 360dialog WhatsApp API + MCP vs AWS End User Messaging
- 360dialog WhatsApp API + MCP vs Bird API + MCP
- 360dialog WhatsApp API + MCP vs Infobip API + MCP
- 360dialog WhatsApp API + MCP vs Kudosity
- 360dialog WhatsApp API + MCP vs Linq
- 360dialog WhatsApp API + MCP vs Photon
- 360dialog WhatsApp API + MCP vs Plivo API
- 360dialog WhatsApp API + MCP vs Prelude
- 360dialog WhatsApp API + MCP vs Sinch Messaging APIs + MCP
- 360dialog WhatsApp API + MCP vs Twilio API + MCP
- 360dialog WhatsApp API + MCP vs Vonage Messages API + MCP
- 360dialog WhatsApp API + MCP vs Wati
- 360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)
- 360dialog WhatsApp API + MCP vs YCloud
- Telnyx API + MCP vs Wati
- Telnyx API + MCP vs WhatsApp Business Platform (Cloud API)
- 360dialog WhatsApp API + MCP vs Bandwidth Messaging API + MCP
- 360dialog WhatsApp API + MCP vs ClickSend SMS API + MCP
- 360dialog WhatsApp API + MCP vs Sendblue
- 360dialog WhatsApp API + MCP vs Telegram Bot API
- Telegram Bot API vs Telnyx API + MCP
- Prelude vs Telnyx API + MCP
Machine-readable
- This page as Markdown
/compare/360dialog-vs-telnyx.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/360dialog.json·/api/v1/tools/telnyx.json - From a terminal
anchor compare 360dialog telnyx(the CLI) - Over MCP
compare_tools {"a": "360dialog", "b": "telnyx"}at/mcp, no key