{ "data": { "a": { "slug": "twilio", "name": "Twilio API + MCP", "vendor": "Twilio", "vendorUrl": "https://www.twilio.com", "kind": "http-api", "category": "messaging", "summary": "Programmable Messaging (SMS, MMS, WhatsApp, RCS) and Verify over REST.", "url": "https://www.anchorterminal.com/tools/twilio", "markdownUrl": "https://www.anchorterminal.com/tools/twilio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/twilio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/twilio.json", "repo": "https://github.com/twilio-labs/mcp", "license": "MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.twilio.com/2010-04-01", "packages": [ { "registry": "npm", "name": "twilio" }, { "registry": "pypi", "name": "twilio" }, { "registry": "npm", "name": "@twilio-alpha/mcp" } ], "auth": "mixed", "authNotes": "HTTP Basic auth with the Account SID and Auth Token, or an API key SID and secret (recommended). The hosted docs MCP needs no credentials. The local alpha MCP takes `ACCOUNT_SID/API_KEY:API_SECRET` as a command-line argument, so it shows up in process lists.", "pricing": "usage", "pricingNotes": "Pay as you go, no monthly fee. US SMS $0.0083 a segment outbound or inbound on long code, toll-free or short code, plus outbound carrier fees of $0.0035 (AT\u0026T), $0.0045 (T-Mobile) or $0.005 (Verizon) a message and inbound carrier fees of $0.0035 (AT\u0026T) or $0.0025 (T-Mobile). US MMS $0.022 outbound, $0.0165 inbound on long code. Long code numbers $1.15 a month, toll-free $2.15. UK SMS $0.056. Failed messages $0.001 each. WhatsApp $0.005 a message Twilio fee plus Meta's template fees. Verify $0.05 a successful verification plus channel fees. Trial lasts 30 days with free units (100 SMS), no card (https://www.twilio.com/en-us/sms/pricing/us).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).", "endpoints": [] }, "toolCount": 2, "popularity": { "githubStars": 111, "npmWeekly": 7213599, "pypiWeekly": 4834611, "asOf": "2026-09-30" }, "docsUrl": "https://www.twilio.com/docs/messaging", "llmsTxt": "https://www.twilio.com/docs/llms.txt", "openapi": "https://raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_api_v2010.json", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.whatsapp", "messaging.rcs", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "mcp", "llms-txt", "openapi", "typescript", "python", "webhooks", "whatsapp", "sms", "enterprise" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 80.4, "grade": "A", "agentReady": true, "rank": 8, "ranked": true, "rankOf": 629, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 85, "payments": 40, "reliability": 90, "schema": 92, "security": 85, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-04" }, "negative": 0, "verdict": "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.", "bestFor": "Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.", "strengths": [ "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login", "Restricted API keys with up to 100 endpoint permissions each", "Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits", "Public OpenAPI specs, llms.txt with Markdown twins and a numbered error dictionary", "twilio-node released three times in the last 90 days, most recently 6.1.2 on 2026-09-28" ], "weaknesses": [ "US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate", "A US long code sends 1 message a second per Twilio's scaling guide, with the excess queued for up to 10 hours", "No idempotency key on message creation", "The MCP that can send is an alpha last published on 2025-07-07, and it takes the API secret as a command-line argument", "No security.txt on twilio.com" ], "agentNotes": [ "Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key", "Set `ValidityPeriod` on time-sensitive sends, or a queued message can go out up to 10 hours late", "Check the Messages list for the original before retrying a send that timed out, there's no idempotency key", "On a trial account, send only to verified numbers in the sign-up country using Twilio's message templates, custom bodies aren't available until you upgrade", "Validate `X-Twilio-Signature` on every inbound webhook" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 80.4 } ], "editorialScores": { "ergonomics": 80, "maintenance": 85, "payments": 40, "reliability": 90, "schema": 92, "security": 85, "transparency": 72 }, "provenanceScore": 90 }, "connect": { "http": "curl -X POST \"https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/Messages.json\" \\\n -u \"$TWILIO_API_KEY:$TWILIO_API_SECRET\" \\\n --data-urlencode \"To=+15558675310\" --data-urlencode \"From=+15017122661\" \\\n --data-urlencode \"Body=Hello from Twilio\"", "claudeCode": "claude mcp add --transport http twilio-docs https://mcp.twilio.com/docs", "config": { "mcpServers": { "twilio": { "args": [ "-y", "@twilio-alpha/mcp", "${TWILIO_ACCOUNT_SID}/${TWILIO_API_KEY}:${TWILIO_API_SECRET}", "--services", "twilio_api_v2010" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/twilio" }, "sameCompany": [ "twilio-voice", "stytch-connected-apps", "sendgrid" ], "area": "communication", "unitPrices": [ { "item": "SMS outbound, US", "unit": "message", "usd": 0.0083, "note": "per segment, plus carrier fees of $0.0035 to $0.005" }, { "item": "SMS outbound, UK", "unit": "message", "usd": 0.056 }, { "item": "MMS outbound, US", "unit": "message", "usd": 0.022 }, { "item": "WhatsApp Twilio fee", "unit": "message", "usd": 0.005, "note": "inbound or outbound, Meta template fees extra" }, { "item": "WhatsApp utility or authentication template, US (Meta fee)", "unit": "message", "usd": 0.0034, "note": "passed through by Twilio" } ], "provenance": { "legalEntity": "Twilio Inc.", "domain": "twilio.com", "domainRegistered": "2007-10-26", "endpointOnVendorDomain": true, "terms": "https://www.twilio.com/en-us/legal/tos", "privacy": "https://www.twilio.com/en-us/legal/privacy", "statusPage": "https://status.twilio.com", "changelog": "https://www.twilio.com/en-us/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The terms also name Twilio Ireland Limited for customers outside the US." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/twilio.json", "live": { "slug": "twilio", "probe": { "target": "https://api.twilio.com/2010-04-01", "method": "get", "lastAt": "2026-10-08T19:09:00.849783821Z", "lastOk": true, "lastStatus": 200, "lastMs": 7, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 7, "p95ms24h": 42, "samples24h": 272, "samples30d": 2135, "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": 217, "ok": 217 } ] }, "vendorStatus": { "page": "https://status.twilio.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-08T19:07:02.870286364Z" }, "versions": [ { "registry": "github", "name": "twilio-labs/mcp", "version": "0.0.3", "released": "2025-03-25", "seenAt": "2026-10-08T16:33:00.228185076Z" }, { "registry": "npm", "name": "@twilio-alpha/mcp", "version": "0.7.0", "seenAt": "2026-10-08T16:32:57.95329658Z" }, { "registry": "npm", "name": "twilio", "version": "6.1.2", "seenAt": "2026-10-08T16:32:57.775702397Z" }, { "registry": "pypi", "name": "twilio", "version": "9.11.2", "released": "2026-09-28", "seenAt": "2026-10-08T16:32:57.834304266Z" } ], "githubStars": 112, "npmWeekly": 7856972, "pypiWeekly": 5075511, "securityTxt": { "url": "https://twilio.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:55.980991134Z" }, "llmsTxt": { "url": "https://www.twilio.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:59.059896821Z" }, "domain": { "domain": "twilio.com", "registered": "2007-10-26", "source": "https://rdap.verisign.com/com/v1/domain/twilio.com", "checkedAt": "2026-10-04T13:05:12.523190086Z" }, "pages": [ { "url": "https://www.twilio.com/en-us/sms/pricing/us", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:31:14.129427371Z", "changedAt": "2026-10-06T16:17:22.587177289Z", "fingerprint": "0d4f7123336a" } ], "updatedAt": "2026-10-08T19:09:00.849783821Z" } }, "answer": "Twilio API + MCP scores 80.4 (A) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories.", "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": 201, "ranked": true, "rankOf": 629, "categoryRank": 4, "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:09:02.278184818Z", "lastOk": true, "lastStatus": 400, "lastMs": 124, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 111, "p95ms24h": 124, "samples24h": 19, "samples30d": 19, "days": [ { "date": "2026-10-08", "probes": 19, "ok": 19 } ] }, "vendorStatus": { "page": "https://metastatus.com/whatsapp-business-api", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T17:51:19.274515472Z" }, "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:09:02.278184818Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Twilio", "b": "Meta Platforms, Inc.", "name": "Vendor" }, { "a": "https://api.twilio.com/2010-04-01", "b": "https://graph.facebook.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.0034 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": "2", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-28", "b": "2026-08-11", "name": "Last release" }, { "a": "2026-07-16", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-04-09", "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": "111 stars, 7.2M npm/wk, 4.8M PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Twilio API + MCP scores 80.4 (A) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Twilio API + MCP or WhatsApp Business Platform (Cloud API)?" }, { "answer": "Twilio API + MCP takes an API key or an OAuth sign-in. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.", "question": "Do Twilio API + MCP and WhatsApp Business Platform (Cloud API) need an API key?" }, { "answer": "Yes. Twilio API + MCP has a hosted endpoint at https://api.twilio.com/2010-04-01 and WhatsApp Business Platform (Cloud API) at https://graph.facebook.com.", "question": "Can an agent call Twilio API + MCP and WhatsApp Business Platform (Cloud API) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 90 against 80", "Schema \u0026 documentation, 92 against 82", "Agent ergonomics, 80 against 67", "Security \u0026 auth, 85 against 67", "Maintenance \u0026 community, 85 against 34" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Free to start without a card" ], "goodFor": "Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.", "slug": "twilio", "watchFor": "US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate" }, { "aheadOn": null, "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/bandwidth-vs-twilio.json", "title": "Bandwidth Messaging API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-twilio.json", "title": "Bird API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/bird-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-twilio.json", "title": "ClickSend SMS API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/clicksend-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-twilio.json", "title": "Infobip API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-vs-twilio" }, { "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/sinch-vs-twilio.json", "title": "Sinch Messaging APIs + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/sinch-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/telnyx-vs-twilio.json", "title": "Telnyx API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/telnyx-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/twilio-vs-vonage.json", "title": "Twilio API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/twilio-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-twilio.json", "title": "360dialog WhatsApp API + MCP vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-twilio" }, { "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/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/plivo-vs-whatsapp-cloud-api.json", "title": "Plivo API vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/plivo-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/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" } ], "scores": [ { "by": 10, "edge": "twilio", "key": "reliability", "name": "Reliability", "twilio": 90, "weight": 16, "whatsapp-cloud-api": 80 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "twilio", "key": "schema", "name": "Schema \u0026 documentation", "twilio": 92, "weight": 13, "whatsapp-cloud-api": 82 }, { "by": 13, "edge": "twilio", "key": "ergonomics", "name": "Agent ergonomics", "twilio": 80, "weight": 13, "whatsapp-cloud-api": 67 }, { "by": 18, "edge": "twilio", "key": "security", "name": "Security \u0026 auth", "twilio": 85, "weight": 14, "whatsapp-cloud-api": 67 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "twilio": 40, "weight": 10, "whatsapp-cloud-api": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 51, "edge": "twilio", "key": "maintenance", "name": "Maintenance \u0026 community", "twilio": 85, "weight": 7, "whatsapp-cloud-api": 34 }, { "by": 1, "edge": "whatsapp-cloud-api", "key": "transparency", "name": "Transparency \u0026 trust", "twilio": 81, "weight": 7, "whatsapp-cloud-api": 82 } ], "summary": "Twilio API + MCP scores 80.4 (A) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories. Both do messaging whatsapp.", "verdicts": { "twilio": "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.", "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/twilio-vs-whatsapp-cloud-api", "json": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.md", "slim": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.min.md" }, "markdown": "Twilio API + MCP scores 80.4 (A) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories. Both do messaging whatsapp.\n\n- Twilio API + MCP: grade A, 80.4/100, rank #8 of 629. Markdown https://www.anchorterminal.com/tools/twilio.md · JSON https://www.anchorterminal.com/api/v1/tools/twilio.json\n- WhatsApp Business Platform (Cloud API): grade B, 67.1/100, rank #201 of 629. 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### Twilio API + MCP (A)\n\nGood for: Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.\n\nAhead on:\n- Reliability, 90 against 80\n- Schema \u0026 documentation, 92 against 82\n- Agent ergonomics, 80 against 67\n- Security \u0026 auth, 85 against 67\n- Maintenance \u0026 community, 85 against 34\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate\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\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 | Twilio API + MCP | WhatsApp Business Platform (Cloud API) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 90 | 80 | Twilio API + MCP +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 82 | Twilio API + MCP +10 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 67 | Twilio API + MCP +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 85 | 67 | Twilio API + MCP +18 |\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) | 85 | 34 | Twilio API + MCP +51 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 82 | WhatsApp Business Platform (Cloud API) +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **80.4 · A** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Twilio API + MCP | WhatsApp Business Platform (Cloud API) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Twilio | Meta Platforms, Inc. |\n| Hosted endpoint | `https://api.twilio.com/2010-04-01` | `https://graph.facebook.com` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| Price for messaging whatsapp | $0.0034 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| Tools exposed | 2 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-28 | 2026-08-11 |\n| Terms last updated | 2026-07-16 | couldn't be read |\n| Privacy policy last updated | 2026-04-09 | 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 | 111 stars, 7.2M npm/wk, 4.8M PyPI/wk | none |\n| Agent reviews | 3.5/5 (8) | none |\n\n## Verdicts\n\n**Twilio API + MCP.** Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.\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### Twilio API + MCP\n\n1. Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key\n2. Set `ValidityPeriod` on time-sensitive sends, or a queued message can go out up to 10 hours late\n3. Check the Messages list for the original before retrying a send that timed out, there's no idempotency key\n4. On a trial account, send only to verified numbers in the sign-up country using Twilio's message templates, custom bodies aren't available until you upgrade\n5. Validate `X-Twilio-Signature` on every inbound webhook\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, Twilio API + MCP or WhatsApp Business Platform (Cloud API)?\n\nTwilio API + MCP scores 80.4 (A) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories.\n\n### Do Twilio API + MCP and WhatsApp Business Platform (Cloud API) need an API key?\n\nTwilio API + MCP takes an API key or an OAuth sign-in. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.\n\n### Can an agent call Twilio API + MCP and WhatsApp Business Platform (Cloud API) without installing anything?\n\nYes. Twilio API + MCP has a hosted endpoint at https://api.twilio.com/2010-04-01 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/twilio-vs-whatsapp-cloud-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"twilio\", \"b\": \"whatsapp-cloud-api\"}`. From a terminal: `anchor compare twilio whatsapp-cloud-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/twilio.json and https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json\n\n## Other comparisons with Twilio API + MCP or WhatsApp Business Platform (Cloud API)\n\n- [Bandwidth Messaging API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-twilio.md)\n- [Bird API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bird-vs-twilio.md)\n- [ClickSend SMS API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-twilio.md)\n- [Infobip API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/infobip-vs-twilio.md)\n- [Plivo API vs Twilio API + MCP](https://www.anchorterminal.com/compare/plivo-vs-twilio.md)\n- [Sinch Messaging APIs + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/sinch-vs-twilio.md)\n- [Telnyx API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-twilio.md)\n- [Twilio API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/twilio-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-twilio.md)\n- [360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/360dialog-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- [Plivo API vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/plivo-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- [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", "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": "Twilio API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "" } ], "description": "Twilio API + MCP scores 80.4 (A) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories. Both do messaging whatsapp. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Twilio API + MCP A 80.4", "WhatsApp Business Platform (Cloud API) B 67.1", "scores" ], "h1": "Twilio API + MCP vs WhatsApp Business Platform (Cloud API)", "image": "https://www.anchorterminal.com/assets/og/compare-twilio-vs-whatsapp-cloud-api.png", "path": "/compare/twilio-vs-whatsapp-cloud-api", "published": "2026-10-01", "section": "tools", "title": "Twilio API + MCP vs WhatsApp Business Platform (Cloud API)", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api" }, "tokens": { "markdown": 2500, "slim": 780 }, "version": 1 }