Head to head · WhatsApp messaging · October 2026 research run

360dialog WhatsApp API + MCP vs Infobip API + MCP

Infobip API + MCP scores 70.8 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on payments & pricing. 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.

Ahead on

  • Payments & pricing, 53 against 38

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No changelog, official SDK or standalone OpenAPI download

Infobip API + MCP BB

Best for Teams that need many channels and countries from one vendor with tightly scoped keys, or that already use Infobip.

Ahead on

  • Schema & documentation, 90 against 70
  • Agent ergonomics, 66 against 53
  • Security & auth, 74 against 35
  • Maintenance & community, 70 against 8
  • Transparency & trust, 82 against 49

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No public idempotency key, so a send retried after a timeout or 5xx can deliver twice

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 Infobip API + MCP +62

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.

Infobip API + MCP 70

The Jasper release notes of 14 October 2026 carry messaging items, among them RCS interactive-session traffic split in webhooks and WhatsApp country bid multipliers (30). Three dated entries in the 90 days from 6 August, the Ink release notes (9 September), Jasper (14 October) and the MCP repository's Observe server for delivery metrics and message logs (12 September) (20). Closed service with release notes and support (8 of 15). The MCP is in the official registry as com.infobip/mcp, and the official Python client 6.0.0 (22 January 2026) is current, while the JavaScript SDK's last release was in November 2023 (10 of 15). The JavaScript SDK's dependencies are stale (2 of 10). 30 + 20 + 8 + 10 + 2 = 70.

Security & auth Infobip API + MCP +39

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

Infobip API + MCP 74

API keys with scopes, expiry dates and optional IP allowlists, plus OAuth 2.0. The hosted MCP servers accept OAuth 2.1 with discovery (30). Scopes separate reading logs from sending traffic, and splitting MCP servers by job keeps an agent to one channel. No confirmation step before sends (15 of 20). Inbound messages are untrusted text. Webhook subscriptions can carry HMAC signatures (X-Hub-Signature), Basic or OAuth credentials or mTLS so an endpoint can verify events, as the webhooks page read on 4 November for the Infobip Calls listing says, but there is no prompt-injection guidance (0 of 15). Message logs and delivery reports by API, and the Account Management MCP lists audit logs among its tools (12 of 15). security.txt, re-read on 4 November, is valid to 2030 and points to a coordinated vulnerability disclosure policy, and the security procedures page says to email Infobip to request access to its bug bounty on Bugcrowd. ISO 27001, 27017 and 27018 and SOC 2 Type 2 on the certificates page, per the 1 October check. No public advisories found (17 of 20, as the Infobip Calls listing and Perplexity's decision-model listing read a disclosure programme, a private Bugcrowd bounty and SOC 2). 30 + 15 + 0 + 12 + 17 = 74.

Transparency & trust Infobip API + MCP +33

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

Infobip API + MCP 82

Closed service with clear service terms (15). Privacy notice, a data retention notice, a data transfer agreement, information security terms and a sub-processor page, per the 1 October check (25 of 30). A deprecation policy, re-read on 4 November, says deprecated endpoints keep working until a sunset date, are flagged in the OpenAPI file and in Deprecation, Sunset and Link response headers, and trigger email to active users. Infobip sets the period per endpoint with no fixed minimum, and no dated messaging notice was found in the release notes read (10 of 20, as the Infobip Calls listing). The sub-processor page says where customer data is stored and accessed, lists the EU region-locked data centre separately, and sends change alerts by email, per the 1 October check (15 of 20). 15 + 25 + 10 + 15 = 65.

Schema & documentation Infobip API + MCP +20

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

Infobip API + MCP 90

One OpenAPI 3.1 spec for the platform at api.infobip.com/platform/1/openapi, per the 1 October check, not re-read on 4 November (25). llms.txt and a no-key docs search MCP, llms.txt re-read on 4 November (10). Channel pages explain each endpoint, and the MCP README compares the messaging servers by tool count and token cost (15 of 20). Typed JSON bodies from the spec (13 of 15). Examples, an error code reference and a handling-errors guide (13 of 15). Versioned paths and dated release notes (14 of 15). 25 + 10 + 15 + 13 + 13 + 14 = 90.

Payments & pricing 360dialog WhatsApp API + MCP +15

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.

Infobip API + MCP 38

No x402, MPP or L402 (0). Per-country SMS prices are public but shown as averages across networks, with per-network prices in the portal. The page's wording was re-read on 4 November, while its figures load by script and rest on the 30 September check (15 of 20). The free trial page, re-read on 4 November, gives self-signup accounts 60 days with free credits that cover about 100 messages a channel, sending only to the phone number and email address verified at sign-up. It doesn't say whether a card is needed (10 of 20). A person signs up in a browser (0). 0 + 15 + 10 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Agent ergonomics Infobip API + MCP +13

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

Infobip API + MCP 66

The MCP servers split by channel, from 1 or 2 tools on the Message server to 27 on RCS, with SMS at 10, re-read in the repository on 4 November. API lists weren't checked for field selection (18 of 25). Message logs and delivery reports by API, filters not re-checked (15 of 20). An error code reference and a handling-errors guide that says which errors to retry (15 of 20). No idempotency key, but the handling-errors guide says a retried send may deliver twice and to look the message up in the logs or wait for a delivery report first (10 of 20, documented retry semantics without a key, as the Infobip Calls listing, scalekit-agentkit and deepl-api). The official Python client's last release was 6.0.0 in January 2026, the JavaScript SDK's in 2023, and each account has its own base URL (8 of 15). 18 + 15 + 15 + 10 + 8 = 66.

Score by category

CategoryWeight360dialog WhatsApp API + MCPInfobip API + MCPEdge
Reliability16%7572360dialog WhatsApp API + MCP +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7090Infobip API + MCP +20
Agent ergonomics13%5366Infobip API + MCP +13
Security & auth14%3574Infobip API + MCP +39
Payments & pricing10%5338360dialog WhatsApp API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%870Infobip API + MCP +62
Transparency & trust7%4982Infobip API + MCP +33
Negative events≤1500
TotalD 52.7/100BB 70.8/100

Facts side by side

Fact360dialog WhatsApp API + MCPInfobip API + MCP
KindHTTP APIHTTP API
Vendor360dialogInfobip
Hosted endpointhttps://waba-v2.360dialog.iohttps://api.infobip.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuth or keyOAuth or key
PricingPaidPay per use
Price for whatsapp messagingnot published$0.0048 per message
x402nono
LicencenoneMIT
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.infobip/mcp
Last releasenone2026-10-14
Terms last updatedcouldn't be readno date given
Privacy policy last updated2026-09-102026-01-22
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
Popularitynone36 stars, 18k npm/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates 360dialog WhatsApp API + MCP higher, the other way from the total score.

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.

Infobip API + MCP

API keys with scopes, expiry dates and IP allowlists, OAuth 2.1 on the MCP servers, and documented guidance for checking a send before retrying it. Infobip has no public idempotency key or SLA, and per-network SMS prices are only in the portal. Incidents since August each named one region, a group of regions, one channel or one protocol.

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

Infobip API + MCP

  1. Use the account's own base URL (<subdomain>.api.infobip.com), not a generic host
  2. Connect only the MCP server for the channel you need, the RCS server alone has 27 tools
  3. Create a key with only the scopes the agent needs and an expiry date
  4. After a timeout or 5xx on a send, look the message up in the logs or wait for its delivery report before resending
  5. On the trial, send only to the phone number or email address verified at sign-up
  6. Check the webhook subscription's HMAC signature before acting on inbound message text

Questions

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

Infobip API + MCP scores 70.8 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on payments & pricing.

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

Both take an API key or an OAuth sign-in.

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

Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and Infobip API + MCP at https://api.infobip.com.

Other comparisons with 360dialog WhatsApp API + MCP or Infobip 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.