{ "data": { "a": { "slug": "plivo", "name": "Plivo API", "vendor": "Plivo", "vendorUrl": "https://www.plivo.com", "kind": "http-api", "category": "messaging", "summary": "CPaaS REST API for SMS, MMS, RCS and WhatsApp in 190+ countries, alongside voice.", "url": "https://www.anchorterminal.com/tools/plivo", "markdownUrl": "https://www.anchorterminal.com/tools/plivo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/plivo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/plivo.json", "repo": "https://github.com/plivo/plivo-node", "license": "MIT", "transports": [ "http" ], "remoteUrl": "https://api.plivo.com/v1", "packages": [ { "registry": "npm", "name": "plivo" }, { "registry": "pypi", "name": "plivo" } ], "auth": "api-key", "authNotes": "HTTP Basic auth with Auth ID and Auth Token. The Auth ID also appears in every request path. Subaccounts get their own credentials.", "pricing": "usage", "pricingNotes": "Pay as you go with free trial credits and no card to sign up. US long code SMS $0.0077 outbound and inbound, toll-free $0.0079, MMS $0.018, plus carrier surcharges ($0.0035 to $0.005 a message). Long code numbers $0.50 a month. WhatsApp US marketing $0.0275 and utility $0.00374 a message. UK SMS from $0.0372 (https://www.plivo.com/sms/pricing/us/).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 or stablecoin payment path in docs, pricing or agent discovery files (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 102, "npmWeekly": 50920, "pypiWeekly": 69307, "asOf": "2026-09-30" }, "docsUrl": "https://www.plivo.com/docs/", "llmsTxt": "https://www.plivo.com/docs/llms.txt", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.rcs", "messaging.whatsapp", "messaging.voice", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "llms-txt", "typescript", "python", "webhooks", "sms", "whatsapp" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 60.3, "grade": "C", "agentReady": false, "rank": 406, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 78, "payments": 40, "reliability": 78, "schema": 59, "security": 45, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.", "bestFor": "Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.", "strengths": [ "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier", "Free trial credits with no card", "Published API limit of 300 requests per 5 seconds", "plivo-python released on 2026-07-28 and 2026-09-25", "Signed webhooks, and SOC 2, PCI DSS Level 1 and HIPAA per Plivo's security page" ], "weaknesses": [ "No OpenAPI spec", "One Auth ID and token per account or subaccount, with no scopes or read-only keys", "The official MCP has one tool and only searches docs", "Inbound US SMS is billed at $0.0077 too, plus a T-Mobile inbound surcharge of $0.0025", "No availability SLA, the service levels document covers support response times only" ], "agentNotes": [ "Put the Auth ID in both the path and the Basic auth header, every request needs both", "Stay under 300 API requests per 5 seconds, a 429 carries no Retry-After", "Give each agent its own subaccount to isolate credentials and spend", "Use the docs MCP to find endpoints, then call the REST API directly to send" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.3 } ], "editorialScores": { "ergonomics": 57, "maintenance": 78, "payments": 40, "reliability": 78, "schema": 59, "security": 45, "transparency": 50 }, "provenanceScore": 89 }, "connect": { "http": "curl -X POST \"https://api.plivo.com/v1/Account/$PLIVO_AUTH_ID/Message/\" -u \"$PLIVO_AUTH_ID:$PLIVO_AUTH_TOKEN\" \\\n -H \"Content-Type: application/json\" -d '{\"src\":\"+14155550100\",\"dst\":\"+14155550101\",\"text\":\"Hello from Plivo\"}'" }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/plivo" }, "sameCompany": [ "plivo-voice" ], "area": "communication", "unitPrices": [ { "item": "SMS outbound, US long code", "unit": "message", "usd": 0.0077, "note": "US, carrier surcharge extra" }, { "item": "SMS outbound, UK", "unit": "message", "usd": 0.0372, "note": "UK, starting rate, varies by network" }, { "item": "MMS outbound, US long code", "unit": "message", "usd": 0.018, "note": "US, carrier surcharge extra" }, { "item": "WhatsApp marketing, US", "unit": "message", "usd": 0.0275 }, { "item": "WhatsApp utility or authentication, US", "unit": "message", "usd": 0.00374 } ], "provenance": { "legalEntity": "Plivo Inc.", "domain": "plivo.com", "domainRegistered": "2011-04-17", "endpointOnVendorDomain": true, "terms": "https://www.plivo.com/legal/tos/", "privacy": "https://www.plivo.com/legal/privacy/", "statusPage": "https://status.plivo.com", "changelog": "https://www.plivo.com/changelog/", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Legal entity taken from the site footer." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/plivo.json", "live": { "slug": "plivo", "probe": { "target": "https://api.plivo.com/v1", "method": "get", "lastAt": "2026-10-08T19:52:59.26359439Z", "lastOk": true, "lastStatus": 404, "lastMs": 347, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 331, "p95ms24h": 411, "samples24h": 272, "samples30d": 2143, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 225, "ok": 225 } ] }, "vendorStatus": { "page": "https://status.plivo.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T19:50:58.928002856Z" }, "versions": [ { "registry": "github", "name": "plivo/plivo-node", "version": "v4.79.0", "released": "2026-07-28", "seenAt": "2026-10-08T16:25:45.057976425Z" }, { "registry": "npm", "name": "plivo", "version": "4.79.0", "seenAt": "2026-10-08T16:25:44.885061881Z" }, { "registry": "pypi", "name": "plivo", "version": "4.63.0", "released": "2026-09-25", "seenAt": "2026-10-08T16:25:44.931424459Z" } ], "githubStars": 102, "npmWeekly": 53685, "pypiWeekly": 77271, "securityTxt": { "url": "https://plivo.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:53.379676193Z" }, "llmsTxt": { "url": "https://www.plivo.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:48.345646617Z" }, "domain": { "domain": "plivo.com", "registered": "2011-04-17", "source": "https://rdap.verisign.com/com/v1/domain/plivo.com", "checkedAt": "2026-10-04T13:07:46.742269573Z" }, "pages": [ { "url": "https://www.plivo.com/sms/pricing/us/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:29:46.683488468Z", "changedAt": "2026-10-08T18:29:46.683488468Z", "fingerprint": "465b0a3363d5" } ], "updatedAt": "2026-10-08T19:52:59.26359439Z" } }, "answer": "WhatsApp Business Platform (Cloud API) scores 67.1 (B) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on maintenance \u0026 community.", "b": { "slug": "whatsapp-cloud-api", "name": "WhatsApp Business Platform (Cloud API)", "vendor": "Meta Platforms, Inc.", "vendorUrl": "https://developers.facebook.com", "kind": "http-api", "category": "messaging", "summary": "Meta's WhatsApp Business Platform Cloud API sends and receives WhatsApp messages for a business phone number through the Graph API, with inbound messages and status updates arriving by webhook. Access uses a Meta developer app and OAuth access tokens.", "url": "https://www.anchorterminal.com/tools/whatsapp-cloud-api", "markdownUrl": "https://www.anchorterminal.com/tools/whatsapp-cloud-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/whatsapp-cloud-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json", "repo": "https://github.com/facebook/openapi", "license": "Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT", "transports": [ "http" ], "remoteUrl": "https://graph.facebook.com", "packages": [], "auth": "oauth", "authNotes": "Every call needs a Bearer access token from a Meta developer app with the WhatsApp use case. Access is self-serve for a business using its own account, with no App Review. A person creates the app, a business portfolio and a system user in Meta's dashboards, then generates a system user token with `whatsapp_business_messaging` and `whatsapp_business_management`. Apps that act for other businesses need Advanced access through App Review and onboard customers with Embedded Signup. Business verification raises the messaging limit above 250 recipients a day.", "pricing": "usage", "pricingNotes": "Charged per delivered message, by category (marketing, utility, authentication, service) and recipient country, with no platform or per-number fee found. Meta publishes rate cards as CSV and PDF in 16 currencies. We couldn't read the files, and the one rate we saw in prose is 0.68 US cents for a utility or authentication message to Brazil. Service messages are charged from 1 October 2026 per Meta's timeline. A test account and test number send without a payment method, so an agent can start without a contract (checked 2026-10-08).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the WhatsApp documentation, the llms.txt indexes, the pricing pages or the OpenAPI document (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.facebook.com/documentation/business-messaging/whatsapp/overview", "llmsTxt": "https://developers.facebook.com/documentation/business-messaging/whatsapp/llms.txt", "openapi": "https://raw.githubusercontent.com/facebook/openapi/main/business-messaging-api_v23.0.yaml", "capabilities": [ "messaging.whatsapp", "messaging.inbound" ], "tags": [ "hosted", "usage-based", "oauth", "openapi", "llms-txt", "webhooks", "whatsapp", "mcp", "sandbox", "status-page", "bug-bounty", "soc2" ], "lastRelease": "2026-08-11", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 218, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 34, "payments": 40, "reliability": 80, "schema": 82, "security": 67, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform.", "bestFor": "The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.", "strengths": [ "A test WhatsApp Business account and test number are created with the app and send template messages with no payment method on file", "OpenAPI 3.1 document under MIT in facebook/openapi (78 paths, 113 operations), plus llms.txt indexes and a Markdown copy of each docs page", "Limits are published with numbers, including 80 messages a second per number, 5,000 requests an hour per active account and one message every 6 seconds per recipient", "Message data is kept for at most 30 days, with local storage and no-storage options per phone number, and SOC 2 Type II and ISO 27001 reports for Cloud API", "Webhook payloads are signed with HMAC-SHA256 in `X-Hub-Signature-256`, and mutual TLS is available" ], "weaknesses": [ "A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists", "No idempotency key for message sends was found in the reviewed documentation or the OpenAPI document, so a retried send can reach the user twice", "Meta's pricing page says the 15 January 2026 terms permit general-purpose AI assistants only where Meta is legally required to allow them", "Outside the 24-hour customer service window only pre-approved templates can be sent, and a new business portfolio is limited to 250 recipients in 24 hours", "Meta archived its Node.js SDK, and the published OpenAPI document is pinned to v23.0 while the Graph API is at v26.0" ], "agentNotes": [ "Check when the user last wrote. Free-form messages are accepted only within 24 hours of the user's last message. After that, send an approved template.", "Record the message id from each send and match it to `messages` webhook statuses. Many failures arrive only by webhook, and no idempotency key was found.", "On error 130429 or 131056 wait and retry. Meta's guidance for the per-recipient limit is 4^X seconds, with X rising by one per failure.", "Verify `X-Hub-Signature-256` with the app secret on every webhook, and deduplicate, because failed deliveries are retried for up to 7 days.", "Request `health_status` on the phone number before a campaign to see whether the app, business, account, number and template can send." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.1 } ], "editorialScores": { "ergonomics": 67, "maintenance": 34, "payments": 40, "reliability": 80, "schema": 82, "security": 67, "transparency": 70 }, "provenanceScore": 94 }, "connect": { "http": "curl 'https://graph.facebook.com/v23.0/\u003cBUSINESS_PHONE_NUMBER_ID\u003e/messages' \\\n -H 'Content-Type: application/json' \\\n -H 'Authorization: Bearer \u003cSYSTEM_USER_ACCESS_TOKEN\u003e' \\\n -d '{\"messaging_product\":\"whatsapp\",\"recipient_type\":\"individual\",\"to\":\"\u003cWHATSAPP_USER_PHONE_NUMBER\u003e\",\"type\":\"text\",\"text\":{\"body\":\"Hello!\"}}'", "claudeCode": "claude mcp add --transport http whatsapp_business_tools https://mcp.facebook.com/whatsapp_business_tools" }, "letme": { "capability": "https://letme.dev/messaging.whatsapp", "tool": "https://letme.dev/whatsapp-cloud-api" }, "sameCompany": [ "meta-marketing-api" ], "area": "communication", "unitPrices": [ { "item": "Utility or authentication template, Brazil", "unit": "message", "usd": 0.0068, "note": "the one rate quoted in prose on Meta's non-template pricing page. Rates vary by country and category, and the rate card files weren't read" } ], "provenance": { "legalEntity": "Meta Platforms, Inc.", "domain": "facebook.com", "domainRegistered": "1997-03-29", "endpointOnVendorDomain": true, "terms": "https://www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform", "privacy": "https://www.whatsapp.com/legal/business-data-processing-terms", "statusPage": "https://metastatus.com/whatsapp-business-api", "changelog": "https://developers.facebook.com/documentation/business-messaging/whatsapp/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The API answers at graph.facebook.com and the MCP server at mcp.facebook.com, both facebook.com subdomains.", "www.whatsapp.com/legal/business-solution-terms and /legal/meta-terms-whatsapp-business both redirect to www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform. That page and the Cloud API hosting terms at www.facebook.com/legal/WhatsApp-Business-Platform-Cloud-API render only with JavaScript, so their text wasn't read.", "The privacy field points at the WhatsApp Business Data Processing Terms (last updated 22 August 2025), which we read. Meta's docs name the Cloud API hosting terms as the other data document for Cloud API customers.", "The legal entity is taken from the copyright line of the MIT licence in facebook/openapi. The data processing terms name WhatsApp LLC and WhatsApp Ireland Limited as contracting entities.", "www.facebook.com/.well-known/security.txt and www.whatsapp.com/.well-known/security.txt name a contact, the bug bounty policy at bugbounty.meta.com and a disclosure policy, and expire on 7 November 2026.", "RDAP for facebook.com gives a registration date of 1997-03-29.", "The WhatsApp changelog's newest entry is 12 May 2026, and the one before it 8 December 2025." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/whatsapp-cloud-api.json", "live": { "slug": "whatsapp-cloud-api", "probe": { "target": "https://graph.facebook.com", "method": "get", "lastAt": "2026-10-08T19:53:06.486229417Z", "lastOk": true, "lastStatus": 400, "lastMs": 113, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 111, "p95ms24h": 118, "samples24h": 27, "samples30d": 27, "days": [ { "date": "2026-10-08", "probes": 27, "ok": 27 } ] }, "vendorStatus": { "page": "https://metastatus.com/whatsapp-business-api", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:20.381545782Z" }, "pages": [ { "url": "https://developers.facebook.com/documentation/business-messaging/whatsapp/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:37.55658412Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c1607719e42e" }, { "url": "https://www.whatsapp.com/legal/business-data-processing-terms", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:35.269938621Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3a883fb460c8" }, { "url": "https://www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform", "kind": "terms", "status": 0, "checkedAt": "2026-10-08T18:27:43.250256264Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true } ], "updatedAt": "2026-10-08T19:53:06.486229417Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Plivo", "b": "Meta Platforms, Inc.", "name": "Vendor" }, { "a": "https://api.plivo.com/v1", "b": "https://graph.facebook.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.0037 per message", "b": "not published", "name": "Price for messaging whatsapp" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-25", "b": "2026-08-11", "name": "Last release" }, { "a": "2026-04-29", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-05-27", "b": "2025-08-22", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "102 stars, 51k npm/wk, 69k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "WhatsApp Business Platform (Cloud API) scores 67.1 (B) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Plivo API or WhatsApp Business Platform (Cloud API)?" }, { "answer": "Plivo API needs an API key. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.", "question": "Do Plivo API and WhatsApp Business Platform (Cloud API) need an API key?" }, { "answer": "Yes. Plivo API has a hosted endpoint at https://api.plivo.com/v1 and WhatsApp Business Platform (Cloud API) at https://graph.facebook.com.", "question": "Can an agent call Plivo API and WhatsApp Business Platform (Cloud API) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Maintenance \u0026 community, 78 against 34" ], "also": [ "Free to start without a card" ], "goodFor": "Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.", "slug": "plivo", "watchFor": "No OpenAPI spec" }, { "aheadOn": [ "Schema \u0026 documentation, 82 against 59", "Agent ergonomics, 67 against 57", "Security \u0026 auth, 67 against 45", "Transparency \u0026 trust, 82 against 70" ], "also": null, "goodFor": "The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.", "slug": "whatsapp-cloud-api", "watchFor": "A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists" } ], "job": { "capability": "messaging.whatsapp", "name": "Messaging whatsapp" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.json", "title": "AWS End User Messaging vs Plivo API", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-plivo.json", "title": "Bandwidth Messaging API + MCP vs Plivo API", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-plivo" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-plivo.json", "title": "Bird API + MCP vs Plivo API", "url": "https://www.anchorterminal.com/compare/bird-vs-plivo" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-plivo.json", "title": "ClickSend SMS API + MCP vs Plivo API", "url": "https://www.anchorterminal.com/compare/clicksend-vs-plivo" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-plivo.json", "title": "Infobip API + MCP vs Plivo API", "url": "https://www.anchorterminal.com/compare/infobip-vs-plivo" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-sendblue.json", "title": "Plivo API vs Sendblue", "url": "https://www.anchorterminal.com/compare/plivo-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-sinch.json", "title": "Plivo API vs Sinch Messaging APIs + MCP", "url": "https://www.anchorterminal.com/compare/plivo-vs-sinch" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-telnyx.json", "title": "Plivo API vs Telnyx API + MCP", "url": "https://www.anchorterminal.com/compare/plivo-vs-telnyx" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-twilio.json", "title": "Plivo API vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/plivo-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-vonage.json", "title": "Plivo API vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/plivo-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-plivo.json", "title": "360dialog WhatsApp API + MCP vs Plivo API", "url": "https://www.anchorterminal.com/compare/360dialog-vs-plivo" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api.json", "title": "360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.json", "title": "AWS End User Messaging vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api.json", "title": "Bird API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api.json", "title": "Infobip API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api.json", "title": "Sinch Messaging APIs + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/telnyx-vs-whatsapp-cloud-api.json", "title": "Telnyx API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/telnyx-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.json", "title": "Twilio API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.json", "title": "Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api.json", "title": "Bandwidth Messaging API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-whatsapp-cloud-api.json", "title": "ClickSend SMS API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/clicksend-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api.json", "title": "Sendblue vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api" } ], "scores": [ { "by": 2, "edge": "whatsapp-cloud-api", "key": "reliability", "name": "Reliability", "plivo": 78, "weight": 16, "whatsapp-cloud-api": 80 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 23, "edge": "whatsapp-cloud-api", "key": "schema", "name": "Schema \u0026 documentation", "plivo": 59, "weight": 13, "whatsapp-cloud-api": 82 }, { "by": 10, "edge": "whatsapp-cloud-api", "key": "ergonomics", "name": "Agent ergonomics", "plivo": 57, "weight": 13, "whatsapp-cloud-api": 67 }, { "by": 22, "edge": "whatsapp-cloud-api", "key": "security", "name": "Security \u0026 auth", "plivo": 45, "weight": 14, "whatsapp-cloud-api": 67 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "plivo": 40, "weight": 10, "whatsapp-cloud-api": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 44, "edge": "plivo", "key": "maintenance", "name": "Maintenance \u0026 community", "plivo": 78, "weight": 7, "whatsapp-cloud-api": 34 }, { "by": 12, "edge": "whatsapp-cloud-api", "key": "transparency", "name": "Transparency \u0026 trust", "plivo": 70, "weight": 7, "whatsapp-cloud-api": 82 } ], "summary": "WhatsApp Business Platform (Cloud API) scores 67.1 (B) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on maintenance \u0026 community. Both do messaging whatsapp.", "verdicts": { "plivo": "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.", "whatsapp-cloud-api": "The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api", "json": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.md", "slim": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.min.md" }, "markdown": "WhatsApp Business Platform (Cloud API) scores 67.1 (B) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on maintenance \u0026 community. Both do messaging whatsapp.\n\n- Plivo API: grade C, 60.3/100, rank #406 of 722. Markdown https://www.anchorterminal.com/tools/plivo.md · JSON https://www.anchorterminal.com/api/v1/tools/plivo.json\n- WhatsApp Business Platform (Cloud API): grade B, 67.1/100, rank #218 of 722. Markdown https://www.anchorterminal.com/tools/whatsapp-cloud-api.md · JSON https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json\n\n## Which one, for what\n\n### Plivo API (C)\n\nGood for: Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.\n\nAhead on:\n- Maintenance \u0026 community, 78 against 34\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No OpenAPI spec\n\n### WhatsApp Business Platform (Cloud API) (B)\n\nGood for: The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 59\n- Agent ergonomics, 67 against 57\n- Security \u0026 auth, 67 against 45\n- Transparency \u0026 trust, 82 against 70\n\nWatch for: A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists\n\n\n## Score by category\n\n| Category | Weight | Plivo API | WhatsApp Business Platform (Cloud API) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 80 | WhatsApp Business Platform (Cloud API) +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 82 | WhatsApp Business Platform (Cloud API) +23 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 67 | WhatsApp Business Platform (Cloud API) +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 67 | WhatsApp Business Platform (Cloud API) +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 34 | Plivo API +44 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 82 | WhatsApp Business Platform (Cloud API) +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.3 · C** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Plivo API | WhatsApp Business Platform (Cloud API) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Plivo | Meta Platforms, Inc. |\n| Hosted endpoint | `https://api.plivo.com/v1` | `https://graph.facebook.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| Price for messaging whatsapp | $0.0037 per message | not published |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-25 | 2026-08-11 |\n| Terms last updated | 2026-04-29 | couldn't be read |\n| Privacy policy last updated | 2026-05-27 | 2025-08-22 |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | 102 stars, 51k npm/wk, 69k PyPI/wk | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## Verdicts\n\n**Plivo API.** US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.\n\n**WhatsApp Business Platform (Cloud API).** The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform.\n\n## Before you call either\n\n### Plivo API\n\n1. Put the Auth ID in both the path and the Basic auth header, every request needs both\n2. Stay under 300 API requests per 5 seconds, a 429 carries no Retry-After\n3. Give each agent its own subaccount to isolate credentials and spend\n4. Use the docs MCP to find endpoints, then call the REST API directly to send\n\n### WhatsApp Business Platform (Cloud API)\n\n1. Check when the user last wrote. Free-form messages are accepted only within 24 hours of the user's last message. After that, send an approved template.\n2. Record the message id from each send and match it to `messages` webhook statuses. Many failures arrive only by webhook, and no idempotency key was found.\n3. On error 130429 or 131056 wait and retry. Meta's guidance for the per-recipient limit is 4^X seconds, with X rising by one per failure.\n4. Verify `X-Hub-Signature-256` with the app secret on every webhook, and deduplicate, because failed deliveries are retried for up to 7 days.\n5. Request `health_status` on the phone number before a campaign to see whether the app, business, account, number and template can send.\n\n## Questions\n\n### Which is better for AI agents, Plivo API or WhatsApp Business Platform (Cloud API)?\n\nWhatsApp Business Platform (Cloud API) scores 67.1 (B) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on maintenance \u0026 community.\n\n### Do Plivo API and WhatsApp Business Platform (Cloud API) need an API key?\n\nPlivo API needs an API key. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.\n\n### Can an agent call Plivo API and WhatsApp Business Platform (Cloud API) without installing anything?\n\nYes. Plivo API has a hosted endpoint at https://api.plivo.com/v1 and WhatsApp Business Platform (Cloud API) at https://graph.facebook.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"plivo\", \"b\": \"whatsapp-cloud-api\"}`. From a terminal: `anchor compare plivo whatsapp-cloud-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/plivo.json and https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json\n\n## Other comparisons with Plivo API or WhatsApp Business Platform (Cloud API)\n\n- [AWS End User Messaging vs Plivo API](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-plivo.md)\n- [Bandwidth Messaging API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bandwidth-vs-plivo.md)\n- [Bird API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bird-vs-plivo.md)\n- [ClickSend SMS API + MCP vs Plivo API](https://www.anchorterminal.com/compare/clicksend-vs-plivo.md)\n- [Infobip API + MCP vs Plivo API](https://www.anchorterminal.com/compare/infobip-vs-plivo.md)\n- [Plivo API vs Sendblue](https://www.anchorterminal.com/compare/plivo-vs-sendblue.md)\n- [Plivo API vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/plivo-vs-sinch.md)\n- [Plivo API vs Telnyx API + MCP](https://www.anchorterminal.com/compare/plivo-vs-telnyx.md)\n- [Plivo API vs Twilio API + MCP](https://www.anchorterminal.com/compare/plivo-vs-twilio.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Plivo API](https://www.anchorterminal.com/compare/360dialog-vs-plivo.md)\n- [360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api.md)\n- [AWS End User Messaging vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.md)\n- [Bird API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api.md)\n- [Infobip API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api.md)\n- [Sinch Messaging APIs + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api.md)\n- [Telnyx API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/telnyx-vs-whatsapp-cloud-api.md)\n- [Twilio API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.md)\n- [Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.md)\n- [Bandwidth Messaging API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api.md)\n- [ClickSend SMS API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/clicksend-vs-whatsapp-cloud-api.md)\n- [Sendblue vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Plivo API vs WhatsApp Business Platform (Cloud API)", "url": "" } ], "description": "WhatsApp Business Platform (Cloud API) scores 67.1 (B) on agent readiness against Plivo API's 60.3 (C), and leads in 5 of 7 scored categories. Plivo API leads on maintenance \u0026 community. Both do messaging whatsapp. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Plivo API C 60.3", "WhatsApp Business Platform (Cloud API) B 67.1", "scores" ], "h1": "Plivo API vs WhatsApp Business Platform (Cloud API)", "image": "https://www.anchorterminal.com/assets/og/compare-plivo-vs-whatsapp-cloud-api.png", "path": "/compare/plivo-vs-whatsapp-cloud-api", "published": "2026-10-01", "section": "tools", "title": "Plivo API vs WhatsApp Business Platform (Cloud API) for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }