{ "data": { "a": { "slug": "sendblue", "name": "Sendblue", "vendor": "Round One, Inc.", "vendorUrl": "https://www.sendblue.com", "kind": "http-api", "category": "messaging", "summary": "Sendblue is a hosted API from Round One, Inc. for sending and receiving iMessage, RCS, SMS and MMS from dedicated or shared phone numbers. Agents use a REST API, TypeScript and Python SDKs, a CLI and an MCP server.", "url": "https://www.anchorterminal.com/tools/sendblue", "markdownUrl": "https://www.anchorterminal.com/tools/sendblue.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sendblue.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sendblue.json", "repo": "https://github.com/sendblue-api/sendblue-ts", "license": "Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.sendblue.com", "packages": [ { "registry": "npm", "name": "sendblue" }, { "registry": "pypi", "name": "sendblue" }, { "registry": "npm", "name": "sendblue-api-mcp" }, { "registry": "npm", "name": "@sendblue/cli" } ], "auth": "api-key", "authNotes": "Every request carries the account's key pair in the `sb-api-key-id` and `sb-api-secret-key` headers, and requests from a browser are refused. The keys come from the dashboard or from `sendblue show-keys` after the CLI creates the account, which needs a person to text a one-time code or enter an email code. `POST /v3/auth/tokens` mints a temporary bearer token, account-wide or limited to named phone numbers, valid for 900 seconds by default and revocable. The MCP server reads `SENDBLUE_API_API_KEY` and `SENDBLUE_API_API_SECRET` from the environment. Agency subaccounts with their own keys need approval from support.", "pricing": "freemium", "pricingNotes": "Flat price per line with no per-message fee. The Free Sandbox is $0 with no card, on a shared number with up to 10 verified contacts. The AI Agent plan is $100 a month per dedicated line and is inbound-first. Proactive outbound messaging is on the Enterprise or Blue Ocean plan, priced through sales. The terms add 3 per cent for card payments and $60 per line to port a number out (https://www.sendblue.com/pricing, checked 2026-10-08).", "priceSummary": "$100 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, either `llms.txt`, the pricing page or the terms (checked 2026-10-08).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": null, "npmWeekly": 249505, "pypiWeekly": 39912, "asOf": "2026-10-08" }, "docsUrl": "https://docs.sendblue.com", "llmsTxt": "https://docs.sendblue.com/llms.txt", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.rcs", "messaging.inbound", "messaging.verify" ], "tags": [ "hosted", "imessage", "sms", "rcs", "mcp", "cli", "llms-txt", "typescript", "python", "webhooks", "no-card", "status-page" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 61.7, "grade": "C", "agentReady": false, "rank": 358, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 72, "payments": 40, "reliability": 71, "schema": 66, "security": 46, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.", "bestFor": "An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.", "strengths": [ "One request to `/api/send-message` sends iMessage and can fall back to RCS or SMS, with no per-message fee on any plan", "The CLI creates a free account, a shared line and API keys from a terminal, with no card, once a person texts a one-time code", "Temporary bearer tokens from `/v3/auth/tokens` can be limited to named phone numbers, expire after 900 seconds by default and can be revoked", "Every docs page has a Markdown twin at `/index.md`, and `llms.txt` summarises each page with its limits and conditions", "Rate limits are published with numbers for each plan, and declined sends return an `error_key` an agent can branch on" ], "weaknesses": [ "Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first", "No OpenAPI file was found at any public address, although the SDKs and the reference are generated from one", "The docs install `sendblue-api-mcp`, last published on 5 August 2025 with 18 tools. The API now has 54 configured endpoints", "`/api/send-message` takes no idempotency key, and the SDKs retry 429 and 5xx responses twice by default", "No public DPA, sub-processor list, retention period, deprecation policy or security.txt was found" ], "agentNotes": [ "Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails", "On the free plan a recipient must text the Sendblue number once before any message to them is accepted", "Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six", "Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting", "Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied", "Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.7 } ], "editorialScores": { "ergonomics": 76, "maintenance": 72, "payments": 40, "reliability": 71, "schema": 66, "security": 46, "transparency": 29 }, "provenanceScore": 86 }, "connect": { "install": "npm install sendblue", "http": "curl -X POST https://api.sendblue.com/api/send-message \\\n -H \"sb-api-key-id: $SENDBLUE_API_KEY_ID\" -H \"sb-api-secret-key: $SENDBLUE_API_KEY_SECRET\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"number\":\"+19998887777\",\"from_number\":\"+18887776666\",\"content\":\"Hello from Sendblue!\"}'", "claudeCode": "claude mcp add sendblue_api --env SENDBLUE_API_API_KEY=your-api-key --env SENDBLUE_API_API_SECRET=your-api-secret -- npx -y sendblue-api-mcp --client=claude-code --tools=all", "config": { "mcpServers": { "sendblue_api": { "args": [ "-y", "sendblue-api-mcp", "--tools=all" ], "command": "npx", "env": { "SENDBLUE_API_API_KEY": "your-api-key", "SENDBLUE_API_API_SECRET": "your-api-secret" } } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/sendblue" }, "area": "communication", "unitPrices": [ { "item": "AI Agent plan, dedicated line", "unit": "month", "usd": 100, "note": "Per line, inbound-first, no per-message fee. Outbound plans are priced through sales" } ], "provenance": { "legalEntity": "Round One, Inc.", "domain": "sendblue.com", "domainRegistered": "2011-06-25", "endpointOnVendorDomain": true, "terms": "https://www.sendblue.com/terms-of-service", "privacy": "https://www.sendblue.com/privacy-policy", "statusPage": "https://status.sendblue.com", "changelog": "https://github.com/sendblue-api/sendblue-ts/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms of service (effective 19 March 2025) and the privacy policy (effective 1 May 2024) both name Round One, Inc. as Sendblue. The site footer gives 344 West End Avenue, New York NY 10024.", "The terms cover registering for and using the services, so they govern API use. The privacy policy covers the website and the services and says Sendblue is a processor for its business customers.", "The API answers at api.sendblue.com, and the SDKs default to api.sendblue.co, a second domain the vendor uses.", "`/.well-known/security.txt` returns 404 on www.sendblue.com, docs.sendblue.com and api.sendblue.com.", "There is no API changelog in the docs. The changelog link is the TypeScript SDK's, whose recent entries mostly read as regenerated clients.", "RDAP for sendblue.com gives a registration date of 2011-06-25." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sendblue.json", "live": { "slug": "sendblue", "probe": { "target": "https://api.sendblue.com", "method": "get", "lastAt": "2026-10-08T21:12:21.131570615Z", "lastOk": true, "lastStatus": 200, "lastMs": 731, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 772, "p95ms24h": 921, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.sendblue.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:09.808226694Z" }, "updatedAt": "2026-10-08T21:12:21.131570615Z" } }, "answer": "Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency \u0026 trust.", "b": { "slug": "vonage", "name": "Vonage Messages API + MCP", "vendor": "Vonage (Ericsson)", "vendorUrl": "https://www.vonage.com", "kind": "http-api", "category": "messaging", "summary": "One endpoint (POST /v1/messages) for SMS, MMS, WhatsApp, RCS, Viber and Messenger, with failover between channels.", "url": "https://www.anchorterminal.com/tools/vonage", "markdownUrl": "https://www.anchorterminal.com/tools/vonage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vonage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vonage.json", "repo": "https://github.com/Vonage-Community/vonage-mcp-server-api-bindings", "license": "Apache-2.0", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://api.nexmo.com/v1", "packages": [ { "registry": "npm", "name": "@vonage/server-sdk" }, { "registry": "pypi", "name": "vonage" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings" } ], "auth": "mixed", "authNotes": "Messages API takes a Vonage Application JWT (RS256, signed with the application's private key) or Basic auth with the API key and secret. Basic auth doesn't deliver to application-level webhooks. Inbound webhooks carry an HS256 JWT to verify. The MCP server reads the key, secret, application ID and a base64 private key from env vars.", "pricing": "usage", "pricingNotes": "Pay as you go per message. Rates vary by country and channel and appear only through a country selector or a downloadable sheet. WhatsApp adds a Vonage platform fee to Meta's template fees. New accounts get €2 of test credit and no card is needed (https://www.vonage.com/communications-apis/messages/pricing/).", "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": 15, "popularity": { "githubStars": null, "npmWeekly": 154249, "pypiWeekly": 67062, "asOf": "2026-09-30" }, "docsUrl": "https://developer.vonage.com/en/messages/overview", "llmsTxt": "https://developer.vonage.com/llms.txt", "openapi": "https://developer.vonage.com/api/v1/developer/api/file/messages?format=json", "registryName": "io.github.Vonage/vonage-documentation-mcp", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.whatsapp", "messaging.rcs", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "mcp", "openapi", "llms-txt", "typescript", "python", "webhooks", "whatsapp", "sms", "enterprise" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 66.8, "grade": "B", "agentReady": false, "rank": 227, "ranked": true, "rankOf": 722, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.", "bestFor": "Agents that need several chat channels behind one call with SMS failover.", "strengths": [ "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS", "OpenAPI 3.0.3 spec for the Messages API (version 1.19.1), and SDK releases in Node and Python through September 2026", "75 requests a second per API key, with Retry-After and X-RateLimit headers on 429", "Application JWTs with ACL claims that limit paths and methods", "ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR listed on the security page, and an Audit API for account events" ], "weaknesses": [ "No idempotency key, and channel rejections arrive only by status webhook after a 202", "The sending MCP lives in the Vonage-Community GitHub organisation, last released on 2026-05-26, with no tool annotations", "SMS, WhatsApp and RCS prices sit behind a country selector, and the terms body doesn't render without a browser", "No SLA, security.txt, sub-processor list or retention periods found", "The Audit API costs $550 a month" ], "agentNotes": [ "Keep api.nexmo.com as the host, don't rewrite it to vonage.com", "Use the Messages API, not the legacy SMS API", "Treat a 202 as accepted only, and wait for the status webhook before assuming delivery", "Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks", "Verify the webhook JWT and its payload_hash against the raw body" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.8 } ], "editorialScores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 28 }, "provenanceScore": 69 }, "connect": { "http": "curl https://api.nexmo.com/v1/messages -u \"$VONAGE_API_KEY:$VONAGE_API_SECRET\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"message_type\":\"text\",\"channel\":\"sms\",\"to\":\"447700900000\",\"from\":\"Vonage\",\"text\":\"Hello from Vonage\"}'", "claudeCode": "claude mcp add --transport http vonage-docs https://documentation-mcp.vonage.dev/mcp", "config": { "mcpServers": { "vonage": { "args": [ "-y", "@vonage/vonage-mcp-server-api-bindings" ], "command": "npx", "env": { "VONAGE_API_KEY": "${VONAGE_API_KEY}", "VONAGE_API_SECRET": "${VONAGE_API_SECRET}", "VONAGE_APPLICATION_ID": "${VONAGE_APPLICATION_ID}", "VONAGE_PRIVATE_KEY64": "${VONAGE_PRIVATE_KEY64}", "VONAGE_VIRTUAL_NUMBER": "${VONAGE_VIRTUAL_NUMBER}" } } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/vonage" }, "sameCompany": [ "vonage-voice" ], "area": "communication", "provenance": { "legalEntity": "Vonage Holdings Corp.", "domain": "vonage.com", "domainRegistered": "2000-12-12", "domainNote": "The API endpoints sit on the legacy nexmo.com domain, from Nexmo's acquisition in 2016.", "endpointOnVendorDomain": false, "terms": "https://www.vonage.com/legal/communications-apis/terms-of-use/", "privacy": "https://www.vonage.com/legal/privacy-policy/", "statusPage": "https://vonageapi.statuspage.io", "changelog": "https://developer.vonage.com/en/changelogs", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The privacy notice names Vonage Holdings Corp. as controller where one entity applies. The API terms set the contracting entity by customer region in Schedule 1, which we couldn't read because vonage.com returned 403 to automated requests." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage.json", "live": { "slug": "vonage", "probe": { "target": "https://api.nexmo.com/v1", "method": "get", "lastAt": "2026-10-08T21:12:25.592330603Z", "lastOk": true, "lastStatus": 404, "lastMs": 44, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 60, "samples24h": 271, "samples30d": 2157, "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": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-08T21:06:29.895460909Z" }, "versions": [ { "registry": "github", "name": "Vonage-Community/vonage-mcp-server-api-bindings", "version": "v1.5.0", "released": "2026-05-21", "seenAt": "2026-10-08T16:34:38.629372145Z" }, { "registry": "mcp-registry", "name": "io.github.Vonage/vonage-documentation-mcp", "version": "1.0.0", "seenAt": "2026-10-08T02:42:52.272076636Z" }, { "registry": "npm", "name": "@vonage/server-sdk", "version": "3.30.1", "seenAt": "2026-10-08T16:34:34.591582249Z" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings", "version": "1.5.1", "seenAt": "2026-10-08T16:34:36.752056116Z" }, { "registry": "pypi", "name": "vonage", "version": "4.9.0", "released": "2026-09-16", "seenAt": "2026-10-08T16:34:36.643960692Z" } ], "githubStars": 3, "npmWeekly": 151884, "pypiWeekly": 63193, "securityTxt": { "url": "https://vonage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:38.377472768Z" }, "llmsTxt": { "url": "https://developer.vonage.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:01:01.755882378Z" }, "domain": { "domain": "vonage.com", "registered": "2000-12-12", "source": "https://rdap.verisign.com/com/v1/domain/vonage.com", "checkedAt": "2026-10-04T13:04:15.703583171Z" }, "pages": [ { "url": "https://www.vonage.com/communications-apis/messages/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:31:27.125076816Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "78c0a0681698" } ], "updatedAt": "2026-10-08T21:12:25.592330603Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Round One, Inc.", "b": "Vonage (Ericsson)", "name": "Vendor" }, { "a": "https://api.sendblue.com", "b": "https://api.nexmo.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP, stdio, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT", "b": "Apache-2.0", "name": "Licence" }, { "a": "18", "b": "15", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.Vonage/vonage-documentation-mcp", "name": "MCP registry" }, { "a": "2026-10-07", "b": "2026-09-16", "name": "Last release" }, { "a": "2025-03-19", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2024-05-01", "b": "couldn't be read", "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": "250k npm/wk, 40k PyPI/wk", "b": "154k npm/wk, 67k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency \u0026 trust.", "question": "Which is better for AI agents, Sendblue or Vonage Messages API + MCP?" }, { "answer": "Sendblue needs an API key. Vonage Messages API + MCP takes an API key or an OAuth sign-in.", "question": "Do Sendblue and Vonage Messages API + MCP need an API key?" }, { "answer": "Yes. Sendblue has a hosted endpoint at https://api.sendblue.com and Vonage Messages API + MCP at https://api.nexmo.com/v1.", "question": "Can an agent call Sendblue and Vonage Messages API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 76 against 50", "Transparency \u0026 trust, 58 against 49" ], "also": null, "goodFor": "An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.", "slug": "sendblue", "watchFor": "Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first" }, { "aheadOn": [ "Reliability, 77 against 71", "Schema \u0026 documentation, 90 against 66", "Security \u0026 auth, 73 against 46", "Maintenance \u0026 community, 80 against 72" ], "also": null, "goodFor": "Agents that need several chat channels behind one call with SMS failover.", "slug": "vonage", "watchFor": "No idempotency key, and channel rejections arrive only by status webhook after a 202" } ], "job": { "capability": "messaging.sms", "name": "Messaging sms" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.json", "title": "AWS End User Messaging vs Sendblue", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.json", "title": "AWS End User Messaging vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-sendblue.json", "title": "Bandwidth Messaging API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage.json", "title": "Bandwidth Messaging API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-sendblue.json", "title": "Bird API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/bird-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-vonage.json", "title": "Bird API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/bird-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-sendblue.json", "title": "ClickSend SMS API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/clicksend-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-vonage.json", "title": "ClickSend SMS API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/clicksend-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-sendblue.json", "title": "Infobip API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/infobip-vs-sendblue" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-vonage.json", "title": "Infobip API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-vs-vonage" }, { "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-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/sendblue-vs-sinch.json", "title": "Sendblue vs Sinch Messaging APIs + MCP", "url": "https://www.anchorterminal.com/compare/sendblue-vs-sinch" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-telnyx.json", "title": "Sendblue vs Telnyx API + MCP", "url": "https://www.anchorterminal.com/compare/sendblue-vs-telnyx" }, { "json": "https://www.anchorterminal.com/compare/sendblue-vs-twilio.json", "title": "Sendblue vs Twilio API + MCP", "url": "https://www.anchorterminal.com/compare/sendblue-vs-twilio" }, { "json": "https://www.anchorterminal.com/compare/sinch-vs-vonage.json", "title": "Sinch Messaging APIs + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/sinch-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/telnyx-vs-vonage.json", "title": "Telnyx API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/telnyx-vs-vonage" }, { "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-vonage.json", "title": "360dialog WhatsApp API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-vonage" }, { "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/360dialog-vs-sendblue.json", "title": "360dialog WhatsApp API + MCP vs Sendblue", "url": "https://www.anchorterminal.com/compare/360dialog-vs-sendblue" }, { "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": 6, "edge": "vonage", "key": "reliability", "name": "Reliability", "sendblue": 71, "vonage": 77, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 24, "edge": "vonage", "key": "schema", "name": "Schema \u0026 documentation", "sendblue": 66, "vonage": 90, "weight": 13 }, { "by": 26, "edge": "sendblue", "key": "ergonomics", "name": "Agent ergonomics", "sendblue": 76, "vonage": 50, "weight": 13 }, { "by": 27, "edge": "vonage", "key": "security", "name": "Security \u0026 auth", "sendblue": 46, "vonage": 73, "weight": 14 }, { "by": 3, "edge": "sendblue", "key": "payments", "name": "Payments \u0026 pricing", "sendblue": 40, "vonage": 37, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "vonage", "key": "maintenance", "name": "Maintenance \u0026 community", "sendblue": 72, "vonage": 80, "weight": 7 }, { "by": 9, "edge": "sendblue", "key": "transparency", "name": "Transparency \u0026 trust", "sendblue": 58, "vonage": 49, "weight": 7 } ], "summary": "Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency \u0026 trust. Both do messaging sms.", "verdicts": { "sendblue": "Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.", "vonage": "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/sendblue-vs-vonage", "json": "https://www.anchorterminal.com/compare/sendblue-vs-vonage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/sendblue-vs-vonage.md", "slim": "https://www.anchorterminal.com/compare/sendblue-vs-vonage.min.md" }, "markdown": "Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency \u0026 trust. Both do messaging sms.\n\n- Sendblue: grade C, 61.7/100, rank #358 of 722. Markdown https://www.anchorterminal.com/tools/sendblue.md · JSON https://www.anchorterminal.com/api/v1/tools/sendblue.json\n- Vonage Messages API + MCP: grade B, 66.8/100, rank #227 of 722. Markdown https://www.anchorterminal.com/tools/vonage.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage.json\n\n## Which one, for what\n\n### Sendblue (C)\n\nGood for: An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.\n\nAhead on:\n- Agent ergonomics, 76 against 50\n- Transparency \u0026 trust, 58 against 49\n\nWatch for: Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first\n\n### Vonage Messages API + MCP (B)\n\nGood for: Agents that need several chat channels behind one call with SMS failover.\n\nAhead on:\n- Reliability, 77 against 71\n- Schema \u0026 documentation, 90 against 66\n- Security \u0026 auth, 73 against 46\n- Maintenance \u0026 community, 80 against 72\n\nWatch for: No idempotency key, and channel rejections arrive only by status webhook after a 202\n\n\n## Score by category\n\n| Category | Weight | Sendblue | Vonage Messages API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 77 | Vonage Messages API + MCP +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 90 | Vonage Messages API + MCP +24 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 50 | Sendblue +26 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 73 | Vonage Messages API + MCP +27 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 37 | Sendblue +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 72 | 80 | Vonage Messages API + MCP +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 49 | Sendblue +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.7 · C** | **66.8 · B** | |\n\n## Facts side by side\n\n| Fact | Sendblue | Vonage Messages API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Round One, Inc. | Vonage (Ericsson) |\n| Hosted endpoint | `https://api.sendblue.com` | `https://api.nexmo.com/v1` |\n| Transports | HTTP, stdio | HTTP, stdio, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT | Apache-2.0 |\n| Tools exposed | 18 | 15 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |\n| Last release | 2026-10-07 | 2026-09-16 |\n| Terms last updated | 2025-03-19 | couldn't be read |\n| Privacy policy last updated | 2024-05-01 | couldn't be read |\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 | 250k npm/wk, 40k PyPI/wk | 154k npm/wk, 67k PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**Sendblue.** Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.\n\n**Vonage Messages API + MCP.** POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.\n\n## Before you call either\n\n### Sendblue\n\n1. Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails\n2. On the free plan a recipient must text the Sendblue number once before any message to them is accepted\n3. Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six\n4. Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting\n5. Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied\n6. Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context\n\n### Vonage Messages API + MCP\n\n1. Keep api.nexmo.com as the host, don't rewrite it to vonage.com\n2. Use the Messages API, not the legacy SMS API\n3. Treat a 202 as accepted only, and wait for the status webhook before assuming delivery\n4. Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks\n5. Verify the webhook JWT and its payload_hash against the raw body\n\n## Questions\n\n### Which is better for AI agents, Sendblue or Vonage Messages API + MCP?\n\nVonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency \u0026 trust.\n\n### Do Sendblue and Vonage Messages API + MCP need an API key?\n\nSendblue needs an API key. Vonage Messages API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Sendblue and Vonage Messages API + MCP without installing anything?\n\nYes. Sendblue has a hosted endpoint at https://api.sendblue.com and Vonage Messages API + MCP at https://api.nexmo.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/sendblue-vs-vonage.json, and with the fewest tokens: https://www.anchorterminal.com/compare/sendblue-vs-vonage.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"sendblue\", \"b\": \"vonage\"}`. From a terminal: `anchor compare sendblue vonage`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sendblue.json and https://www.anchorterminal.com/api/v1/tools/vonage.json\n\n## Other comparisons with Sendblue or Vonage Messages API + MCP\n\n- [AWS End User Messaging vs Sendblue](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.md)\n- [AWS End User Messaging vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.md)\n- [Bandwidth Messaging API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bandwidth-vs-sendblue.md)\n- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md)\n- [Bird API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bird-vs-sendblue.md)\n- [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md)\n- [ClickSend SMS API + MCP vs Sendblue](https://www.anchorterminal.com/compare/clicksend-vs-sendblue.md)\n- [ClickSend SMS API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md)\n- [Infobip API + MCP vs Sendblue](https://www.anchorterminal.com/compare/infobip-vs-sendblue.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)\n- [Plivo API vs Sendblue](https://www.anchorterminal.com/compare/plivo-vs-sendblue.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md)\n- [Sendblue vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/sendblue-vs-sinch.md)\n- [Sendblue vs Telnyx API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-telnyx.md)\n- [Sendblue vs Twilio API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-twilio.md)\n- [Sinch Messaging APIs + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sinch-vs-vonage.md)\n- [Telnyx API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-vonage.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 Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.md)\n- [Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.md)\n- [360dialog WhatsApp API + MCP vs Sendblue](https://www.anchorterminal.com/compare/360dialog-vs-sendblue.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": "Sendblue vs Vonage Messages API + MCP", "url": "" } ], "description": "Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency \u0026 trust. Both do messaging sms. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Sendblue C 61.7", "Vonage Messages API + MCP B 66.8", "scores" ], "h1": "Sendblue vs Vonage Messages API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-sendblue-vs-vonage.png", "path": "/compare/sendblue-vs-vonage", "published": "2026-10-01", "section": "tools", "title": "Sendblue vs Vonage Messages API + MCP for AI agents, C 61.7 vs B 66.8", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/sendblue-vs-vonage" }, "tokens": { "markdown": 2450, "slim": 780 }, "version": 1 }