Head to head · Inbound messaging · October 2026 research run

360dialog WhatsApp API + MCP vs Bandwidth Messaging API + MCP

Bandwidth Messaging API + MCP scores 73.1 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in 6 of 7 scored categories. Both do inbound 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

Bandwidth Messaging API + MCP BB

Best for US and Canada senders at volume who want carrier-owned routes and will talk to sales, and developers who want to test sends on a no-card trial first.

Ahead on

  • Schema & documentation, 86 against 70
  • Agent ergonomics, 73 against 53
  • Security & auth, 65 against 35
  • Payments & pricing, 60 against 53
  • Maintenance & community, 78 against 8
  • Transparency & trust, 75 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

Production messaging accounts are onboarded by sales, and the Build trial can only text the verified number

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 Bandwidth Messaging API + MCP +70

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.

Bandwidth Messaging API + MCP 78

Dated release notes, the latest on 16 October 2026 (30). Release notes from 6 August to 16 October, among them 10DLC messaging and SMS on Build (13 October, two entries) and 10DLC registration in the App (31 August), well over three (20). Closed service with release notes and account management. The MCP repository's last commit is still 21 July 2026 and v0.3.0 (11 June) its newest tag (8 of 15). Official SDKs in six languages, node-sdk v8.3.1 and python-sdk v23.3.1 on 13 October 2026 (15). SDKs are generated from the spec, CI not checked (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.

Security & auth Bandwidth Messaging API + MCP +30

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).

Bandwidth Messaging API + MCP 65

OAuth 2.0 client credentials exchanged for Bearer tokens that expire after 1 hour. Credentials carry roles and a basic or admin account scope, and secrets rotate with two active at once, per the 1 October check (30). Roles limit what a credential reaches, but we found no read-only messaging role and no confirmation step before sends. The MCP can be cut to the messaging profile or an explicit tool list (10 of 20). Inbound messages are untrusted text. Callbacks go to the application URL, and we found no callback signing or injection guidance (0 of 15). Message records by API through listMessages (10 of 15). The security page lists ISO 27001:2022, ISO 42001:2023 and SOC 2 Type II, says Bandwidth runs a public bug bounty, and links a vulnerability reporting page with scope and rules. No reward terms were found on that page, no security.txt (404 on 2 November) and no advisories for bandwidth-sdk in OSV. Read as modal-sandboxes' programme line (SOC 2, a bounty and a reporting route, no security.txt) (15 of 20). 30 + 10 + 0 + 10 + 15 = 65.

Transparency & trust Bandwidth Messaging API + MCP +26

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).

Bandwidth Messaging API + MCP 75

Closed service with clear terms (communications services agreement). The MCP server repository still has no licence file (15). Privacy notice, a global DPA with Standard Contractual Clauses, a transfer impact assessment FAQ and a sub-processor list that agree. No retention periods found (20 of 30). The legacy credential migration is documented, with no dated deprecation policy found (5 of 20). The sub-processor list (last updated 31 March 2026) names each provider with the product it supports and the location of processing, such as AWS for hosting in the USA and EU (20). 15 + 20 + 5 + 20 = 60.

Agent ergonomics Bandwidth Messaging API + MCP +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).

Bandwidth Messaging API + MCP 73

listMessages needs at least one filter and pages its results, with no field selection (15 of 25). Filters on to, from, message ID and date range (20). Structured errors, and the MCP maps failures to codes such as rate_limited and auth with retry advice (18 of 20). No idempotency key on sends. Excess messages queue rather than fail (5 of 20). Official SDKs in six languages. A send needs to, from, applicationId and text after an OAuth token exchange (15).

Schema & documentation Bandwidth Messaging API + MCP +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).

Bandwidth Messaging API + MCP 86

OpenAPI spec at dev.bandwidth.com/spec/messaging.yml (25). llms.txt linking Markdown versions of the docs, re-read on 2 November (10). Pages explain each endpoint and callback event, with less on when not to use one (14 of 20). Typed request bodies from the spec (13 of 15). Structured 429 bodies with a type and description, and a messaging errors page. We didn't recheck the full messaging error list (12 of 15). Versioned /api/v2 path and dated release notes (12 of 15). Total 86.

Payments & pricing Bandwidth Messaging API + MCP +7

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.

Bandwidth Messaging API + MCP 60

No x402, MPP or L402 (0). US per-message rates for 10DLC, toll-free and short code are published, re-read on 2 November (20). Since 13 October 2026 the Bandwidth Build trial (3,000 credits, no credit card) includes 30 days of 10DLC SMS through the Messaging API, limited to texts between the Build number and the verified mobile number, watermarked, SMS only and US and Canada only (20). An agent can start a Build registration with the Bandwidth CLI, but a person verifies a phone code, sets a password from an emailed link and creates API credentials in the Bandwidth App, and sending to customers needs a full account through the account team (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeight360dialog WhatsApp API + MCPBandwidth Messaging API + MCPEdge
Reliability16%7575even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7086Bandwidth Messaging API + MCP +16
Agent ergonomics13%5373Bandwidth Messaging API + MCP +20
Security & auth14%3565Bandwidth Messaging API + MCP +30
Payments & pricing10%5360Bandwidth Messaging API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%878Bandwidth Messaging API + MCP +70
Transparency & trust7%4975Bandwidth Messaging API + MCP +26
Negative events≤1500
TotalD 52.7/100BB 73.1/100

Facts side by side

Fact360dialog WhatsApp API + MCPBandwidth Messaging API + MCP
KindHTTP APIHTTP API
Vendor360dialogBandwidth
Hosted endpointhttps://waba-v2.360dialog.iohttps://messaging.bandwidth.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-16
Terms last updatedcouldn't be read2025-09-11
Privacy policy last updated2026-09-102026-08-25
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone2 stars, 13k npm/wk, 39k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Bandwidth Messaging API + MCP higher.

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.

Bandwidth Messaging API + MCP

10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published, with default rate limits and a sub-processor list with locations. Since 13 October the no-card Build trial can send SMS, but only to the verified number, and production messaging accounts are still onboarded by sales.

Before you call either

360dialog WhatsApp API + MCP

  1. Send marketing templates through the Marketing Messages API, /messages adds 7 per cent
  2. Ask a docs page a question with ?ask= before reading the whole page
  3. Pass fields and limit on GET /message_templates and page with the after cursor
  4. Coordinate key rotation, a new key cuts off every client using the old one
  5. Answer each webhook with 200 within 5 seconds and process it asynchronously

Bandwidth Messaging API + MCP

  1. Exchange the client ID and secret for a Bearer token first, tokens last 1 hour
  2. Set BW_MCP_PROFILE=messaging to load only the messaging tools
  3. Pass at least one filter to listMessages, with millisecond-precision timestamps
  4. On a 429, read the allowed rate in the error and pace sends to it
  5. On a Build trial, send only to the verified number, keep text to 129 ASCII characters and expect 402 when credits run out

Questions

Which is better for AI agents, 360dialog WhatsApp API + MCP or Bandwidth Messaging API + MCP?

Bandwidth Messaging API + MCP scores 73.1 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in 6 of 7 scored categories.

Do 360dialog WhatsApp API + MCP and Bandwidth Messaging API + MCP need an API key?

360dialog WhatsApp API + MCP takes an API key or an OAuth sign-in. Bandwidth Messaging API + MCP uses an OAuth sign-in.

Can an agent call 360dialog WhatsApp API + MCP and Bandwidth Messaging API + MCP without installing anything?

Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and Bandwidth Messaging API + MCP at https://messaging.bandwidth.com/api/v2.

Other comparisons with 360dialog WhatsApp API + MCP or Bandwidth Messaging API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.