# Prelude vs WhatsApp Business Platform (Cloud API) (slim)

> Prelude scores 67.6 (B) to WhatsApp Business Platform's 65.3 (B) for whatsapp messaging. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/prelude-vs-whatsapp-cloud-api.md (~5,550 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/prelude-vs-whatsapp-cloud-api.json · canonical https://www.anchorterminal.com/compare/prelude-vs-whatsapp-cloud-api
- 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)

Prelude scores 67.6 (B) on agent readiness against WhatsApp Business Platform (Cloud API)'s 65.3 (B), and leads in 3 of 7 scored categories. WhatsApp Business Platform (Cloud API) leads on reliability, payments & pricing and transparency & trust. Both do whatsapp messaging.

- Prelude: B 67.6, rank #317 of 1510 · https://www.anchorterminal.com/tools/prelude.min.md
- WhatsApp Business Platform (Cloud API): B 65.3, rank #425 of 1510 · https://www.anchorterminal.com/tools/whatsapp-cloud-api.min.md
- Prelude, good for Agents or apps that verify a phone number or email with a code and want fraud blocking, and for transactional messages in Europe. Ahead on Schema & documentation, 93 against 82; Agent ergonomics, 85 against 67; Maintenance & community, 83 against 34.
- WhatsApp Business Platform (Cloud API), good for The direct route to WhatsApp for a business messaging its own customers, with no reseller fee. Ahead on Reliability, 75 against 65; Payments & pricing, 40 against 30; Transparency & trust, 73 against 42.

| Category | Prelude | WhatsApp Business Platform (Cloud API) |
| --- | --- | --- |
| Reliability (16%) | 65 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 82 |
| Agent ergonomics (13%) | 85 | 67 |
| Security & auth (14%) | 63 | 67 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 34 |
| Transparency & trust (7%) | 42 | 73 |

| Fact (where they differ) | Prelude | WhatsApp Business Platform (Cloud API) |
| --- | --- | --- |
| Vendor | DING SAS (Prelude) | Meta Platforms, Inc. |
| Hosted endpoint | `https://api.prelude.dev` | `https://graph.facebook.com` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Licence | Proprietary service; the terms are on a Notion page we couldn't read. The backend SDKs are Apache-2.0 | Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT |
| Last release | 2026-10-16 | 2026-08-11 |
| Privacy policy last updated | couldn't be read | 2025-08-22 |
| Popularity | 98k npm/wk | none |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Maintenance & community, Prelude +49: Prelude 83 (`@prelude.so/sdk` 0.16.0 published to npm on 16 October 2026, 21 days ago, carrying API updates (30). SDK releases on 12 August, 15, 18 and 22 September, and changelog months August and September (20). Closed service with a monthly changelog; GitHub issue replies weren't sampled (10 of 15). Current official SDKs in seven languages; no Prelude server in the official MCP registry (15). The SDK repository runs CI and publish workflows (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.); WhatsApp Business Platform (Cloud API) 34 (Closed service. The newest dated API change found is the OpenAPI document's update on 11 August 2026, still its last commit on 1 November and 82 days ago, after Graph API v26.0 on 29 July (20). One dated change since 3 August, and per the 8 October check the WhatsApp changelog's last entry is 12 May 2026, so the three-entry line isn't met (0). Per the 8 October check, a changelog, developer support, a community forum, bug reports and Direct Support with a 24-hour first-response aim for partners, with one changelog entry in 2026 (8). No current official SDK. The Node.js SDK is archived at 0.0.5-Alpha from April 2023, and the MCP server isn't in the official MCP registry (3). The OpenAPI repository has had no commit since 11 August and is still at v23.0 (3). Meta's developer pages weren't re-read on 1 November, so a newer changelog entry would be unseen. 34.)
- Transparency & trust, WhatsApp Business Platform (Cloud API) +31: Prelude 42 (Closed service whose general terms are a Notion page drawn by script, which we couldn't read; the SDKs are Apache-2.0 (8 of 30). The privacy policy is also unreadable for the same reason, and the trust centre names no retention periods or data locations (3 of 30). v1 and v2 are documented side by side and the changelog dates changes by month, with no deprecation policy found (6 of 20). No sub-processor list or data locations found (0 of 20). 8 + 3 + 6 + 0 = 17.); WhatsApp Business Platform (Cloud API) 73 (Editorial half only. Closed service with named terms and policies and an MIT OpenAPI document. The Meta Terms for WhatsApp Business Platform sit on www.facebook.com, which disallows our crawler, and weren't read (15). Per the 8 October check, the docs state Meta is processor for Cloud API and messages are kept at most 30 days and encrypted at rest. The WhatsApp Business Data Processing Terms read on 8 October sit on www.whatsapp.com, whose robots.txt disallows ClaudeBot, so that reading is struck and the docs' statements can't be checked against a second document (18). Graph API versions carry end dates about two years out, the pricing calendar fixes one, three and six months' notice, and deprecated fields are flagged in the docs, per the 8 October check (20). Processing is in Meta data centres with optional in-country storage, per the docs. The sub-processor terms read on 8 October are struck with the data processing terms, and no sub-processor list was read (8). 61.)
- Agent ergonomics, Prelude +18: Prelude 85 (List calls take `limit` from 1 to 200 with cursor or offset; the MCP server's tool list isn't on the docs page, so its size is unchecked (18 of 25). Cursor and offset pagination with filters (18 of 20). Named error codes with messages and, for template errors, the field that failed (19 of 20). Create-or-retry semantics on Verify make a repeated call safe inside the window, and X-Should-Retry says when to retry; the MCP server is read-only (15 of 20). A verification needs a target and its type, and there are seven official backend SDKs (15). 18 + 18 + 19 + 15 + 15 = 85.); WhatsApp Business Platform (Cloud API) 67 (Per the 8 October check, not re-read on 1 November. Graph API reads take `fields` and `limit`, and one field, `health_status`, summarises whether a number can send. The MCP server isn't what we graded (20). Cursor paging on list edges and filters on template and analytics reads. Inbound messages can't be listed or paged and arrive only by webhook (18). Errors carry `code`, `error_data.details` and `fbtrace_id`, and the reference maps codes to causes and fixes. Some failures arrive only by webhook (18). No idempotency key for sends was found in the docs or the OpenAPI document, and webhook receivers must deduplicate. The MCP send tool asks for confirmation (5). A text send needs four fields. Receiving needs a public HTTPS server, and Meta has no current SDK for Cloud API since archiving its Node.js one (6).)
- Schema & documentation, Prelude +11: Prelude 93 (OpenAPI for the 27 SDK endpoints is public at the URL in the SDK repository's .stats.yml, and every reference page embeds its endpoint's OpenAPI (25). llms.txt and Markdown pages (10). Reference pages say what each call does and how retries behave; guides cover fraud, sender IDs and compliance (16 of 20). Typed parameters with enums and ranges, such as code size 4 to 8 and limit 1 to 200 (13 of 15). Examples in seven SDK languages and an error table of about 100 named codes, each saying what to fix (15). Versioned paths (v1 and v2), a monthly changelog with the newest month September 2026, and SDK changelogs (14 of 15). 25 + 10 + 16 + 13 + 15 + 14 = 93.); WhatsApp Business Platform (Cloud API) 82 (Per the 8 October check, not re-read on 1 November, except the OpenAPI document. A public OpenAPI 3.1 document in facebook/openapi with 78 paths, 113 operations and 369 schemas, unchanged since 11 August 2026 on 1 November. It is pinned to v23.0 while the Graph API is at v26.0, so 3 off (22). llms.txt indexes and a Markdown copy of every guide and reference page (10). Guides explain when a template is required, when the service window applies and which token type suits which developer. Reference text is thin in places, and the send endpoint's description reads only Send Message (13). Request schemas carry types, required marks and 201 enum lists, with templates and interactive messages as nested objects (12). Request examples on most pages, example webhook payloads and an error code reference. Examples mix v17.0, v23.0 and v25.0 (13). Graph API versions with a dated table, and a WhatsApp changelog whose only 2026 entry is 12 May (12).)
- Reliability, WhatsApp Business Platform (Cloud API) +10: Prelude 65 (Read with the hosted lines. status.prelude.so has components for Verify, Auth, Watch, Intel, Notify and the dashboard, with history (20). From 8 August to 6 November its feed records one major incident, increased error rates and latencies across the APIs on 16 and 17 August, posted after it was resolved with no duration stated, and minor ones such as Verify latency on 9 and 10 August, SMS degradation in China and on Orange France and delayed webhooks on 23 October (10). No numeric API rate limits were found; only the MCP server's limits and per-window Verify retry limits are documented (7 of 15). A 429 carries Retry-After and X-Should-Retry, and repeating the create call inside the window performs a retry rather than a new verification (13 of 15). The pricing page lists a 99.95 SLA on Enterprise with no SLA document found (5 of 10). Verify and Notify v2 are generally available (10). 20 + 10 + 7 + 13 + 5 + 10 = 65.); WhatsApp Business Platform (Cloud API) 75 (Graded on the public Cloud API, with the hosted lines. metastatus.com lists the WhatsApp Business Platform with a Cloud API component, an incident history and availability and latency figures, per the 8 October check (20). Per the 8 October check, the Cloud API component showed no incident in the 90 days to 8 October 2026; the Marketing Messages API (19 July) and Meta Business Agent (1 October) incidents aren't the listed product and don't count. metastatus.com renders only with JavaScript and its history comes from the site's own data files, which this run doesn't call, and Meta hosts are paused for us beyond robots.txt, so the window since 8 October is unread. An unread part of the window is never credited, so the line is held at minor-only, as on the Meta Marketing API listing (20). Per the 8 October check, limits are published with numbers for throughput, per recipient and management calls (15). Throttling codes are documented with a 4^X second backoff rule for the per-recipient limit, with no Retry-After header on message sends and no idempotency key (10). No SLA found, and Meta's terms on www.facebook.com, which disallows our crawler, weren't read (0). Cloud API is generally available (10). 75.)
- Payments & pricing, WhatsApp Business Platform (Cloud API) +10: Prelude 30 (No x402, MPP or L402 (0). Per-verification price (€0.032) and per-message Notify prices published without login (20). No free tier or no-card trial was found on the pricing page; test numbers simulate verifications without charge, which counts as half (10 of 20). A person signs up in the dashboard (0). 0 + 20 + 10 + 0 = 30.); WhatsApp Business Platform (Cloud API) 40 (Per the 8 October check, not re-read on 1 November. No x402, MPP or L402 (0). Per-message pricing is public without a login, as CSV and PDF rate cards in 16 currencies and an interactive table on whatsappbusiness.com. We couldn't open the rate files and scored the line on the public pages that list them (20). A test WhatsApp Business account and number send template messages with no payment method (20). A person has to create a Meta account, a developer app and a system user in a browser (0).)