# Prelude vs YCloud (slim)

> Prelude scores 67.6 (B) to YCloud's 64.8 (B) for messaging verify. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/prelude-vs-ycloud.md (~4,150 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/compare/prelude-vs-ycloud.json · canonical https://www.anchorterminal.com/compare/prelude-vs-ycloud
- 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 YCloud's 64.8 (B), and leads in 4 of 7 scored categories. YCloud leads on reliability, payments & pricing and transparency & trust. Both do messaging verify.

- Prelude: B 67.6, rank #316 of 1486 · https://www.anchorterminal.com/tools/prelude.min.md
- YCloud: B 64.8, rank #455 of 1486 · https://www.anchorterminal.com/tools/ycloud.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 Security & auth, 63 against 31; Maintenance & community, 83 against 74.
- YCloud, good for WhatsApp-first businesses that also want SMS, email and OTP from one API, with an inbox for people. Ahead on Reliability, 79 against 65; Payments & pricing, 35 against 30; Transparency & trust, 53 against 42. Also Free to start without a card.

| Category | Prelude | YCloud |
| --- | --- | --- |
| Reliability (16%) | 65 | 79 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 90 |
| Agent ergonomics (13%) | 85 | 83 |
| Security & auth (14%) | 63 | 31 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 74 |
| Transparency & trust (7%) | 42 | 53 |

| Fact (where they differ) | Prelude | YCloud |
| --- | --- | --- |
| Vendor | DING SAS (Prelude) | YCloud International Pte. Ltd. |
| Hosted endpoint | `https://api.prelude.dev` | `https://api.ycloud.com/v2` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Licence | Proprietary service; the terms are on a Notion page we couldn't read. The backend SDKs are Apache-2.0 | Proprietary service under YCloud's terms of service. The Node.js SDK is MIT |
| Last release | 2026-10-16 | 2026-11-03 |
| Terms last updated | couldn't be read | 2026-09-03 |
| Privacy policy last updated | couldn't be read | 2026-04-03 |
| 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 | not found in the text |
| Popularity | 98k npm/wk | none |

Why the edge:
- Security & auth, Prelude +32: Prelude 63 (API keys as bearer tokens with no scopes found; the MCP server uses OAuth with a per-user consent screen (20 of 30). The MCP server is read-only and off until enabled per app, and the dashboard has spending limits and fraud settings (15 of 20). Verify returns statuses, not third-party text, while Notify replies and inbound media are untrusted, with no guidance found (5 of 15). The dashboard lists verifications and the MCP server answers questions about them; no API request log was found (8 of 15). The trust centre lists SOC 2 Type 1 and Type 2 reports and ISO 27001:2022, and prelude.so has a valid security.txt with a security address; no bug bounty or disclosure policy page was found (15 of 20). 20 + 15 + 5 + 8 + 15 = 63.); YCloud 31 (One API key in the `X-API-Key` header, never in the URL, rotated by creating a new key and revoking the old one; no scopes found (20 of 30). Trial accounts send only to pre-verified numbers; no read-only key or approval step (4 of 20). Inbound WhatsApp and SMS text arrives through webhooks, with no prompt-injection guidance (0 of 15). Every response carries a request ID; no operator request log was found in the docs (5 of 15). No certification is named on the pages read, the about page shows an unlabelled ISO image, and there is no security.txt or disclosure policy (2 of 20). 20 + 4 + 0 + 5 + 2 = 31.)
- Reliability, YCloud +14: 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.); YCloud 79 (Read with the hosted lines. status.ycloud.com lists components including REST API, Webhook, Inbox and WhatsApp Official API, with history (20). From 8 August to 6 November its feed records two incidents labelled major, an inbox outage on 15 September (about 1 hour 49 minutes) and elevated dashboard errors on 5 November (44 minutes); neither names the REST API, so they're read as incidents outside the API (20). Limits with numbers per endpoint, account and sender (15). 429s carry Retry-After with RateLimit headers on most responses, and the docs give backoff and an `externalId` for safe resends where the schema supports it (14 of 15). No SLA; the terms say availability can't be guaranteed (0). API v2 is generally available (10). 20 + 20 + 15 + 14 + 0 + 10 = 79.)
- Transparency & trust, YCloud +11: 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.); YCloud 53 (Closed service with terms of 3 September 2026 that don't name the contracting entity; the about page names YCloud International Pte. Ltd. The Node SDK is MIT (12 of 30). The privacy policy (3 April 2026) gives no retention periods, mentions no DPA and says the primary servers are in Singapore (8 of 30). The terms promise reasonable notice of changes only to those who subscribe to it; v1 is kept as legacy (7 of 20). No sub-processor list; the data location is named (5 of 20). 12 + 8 + 7 + 5 = 32.)
- Maintenance & community, Prelude +9: 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.); YCloud 74 (`@ycloud-cpaas/ycloud-sdk-node` 1.17.2 on 3 November 2026 (30). Releases 1.17.0 (23 October), 1.17.1 (26 October) and 1.17.2 in the window (20). Closed service with a ticket desk; GitHub issue replies weren't sampled (6 of 15). Current official SDKs in four languages, generated from the spec; no MCP server in the docs or registry (15). The Node SDK repository has no CI workflow in the clone we read (3 of 10). 30 + 20 + 6 + 15 + 3 = 74.)
- Payments & pricing, YCloud +5: 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.); YCloud 35 (No x402, MPP or L402 (0). Plan prices public, WhatsApp at Meta's rate with no markup and email at $0.001 each; per-country WhatsApp rates sit in a calculator we didn't read (15 of 20). The Free plan includes the messaging API with no card (20). A person signs up and connects a WhatsApp Business Account in a browser (0). 0 + 15 + 20 + 0 = 35.)