Head to head · SMS · October 2026 research run

Sendblue vs Sinch Messaging APIs + MCP

Sinch Messaging APIs + MCP scores 67 (B) on agent readiness against Sendblue's 62.2 (B), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics. Both do sms.

Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons

Which one, for what

Sendblue B

Best 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.

Ahead on

  • Agent ergonomics, 76 against 50

Watch for

Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first

Sinch Messaging APIs + MCP B

Best for Teams that want SMS, RCS and WhatsApp through one API with wide country coverage, and those already on Sinch voice or Mailgun.

Ahead on

  • Reliability, 73 against 61
  • Schema & documentation, 81 against 66
  • Security & auth, 55 against 46
  • Maintenance & community, 83 against 72
  • Transparency & trust, 77 against 58

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

The MCP server is a developer preview, 0.0.1-beta.7 since 30 October 2026

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics Sendblue +26

Sendblue 76

Message lists take limit from 1 to 100, and the MCP server adds a jq_filter on every tool, a read-only filter and a three-tool dynamic mode (20 of 25). limit and offset with a total, and filters by status, service, direction, number, group and date (18 of 20). Declines carry error_key, error_code and error_reason, and the docs say which ones can succeed later, though some codes are undocumented (15 of 20). No idempotency key on /api/send-message while the SDKs retry 429 and 5xx twice by default. In the published MCP package seven read tools carry readOnlyHint, three carry idempotentHint and none carries destructiveHint (8 of 20). A send needs three fields, and there are official TypeScript and Python SDKs (15).

Sinch Messaging APIs + MCP 50

We didn't confirm page-size or field controls on message lists (10 of 25). Pagination and filters not confirmed (10 of 20). Error responses with codes, and back-off advice for 5xx (15 of 20). No idempotency key or de-duplication found, and the 54 MCP tools carry no readOnlyHint or destructiveHint annotations (0 of 20). Official SDKs in Node, Python, Java and .NET. A send names an app, a recipient, a channel and a message object (15).

Transparency & trust Sinch Messaging APIs + MCP +19

Sendblue 58

Closed service with clear terms from Round One, Inc., and Apache-2.0 SDKs (15 of 30). The privacy policy dates from 1 May 2024, describes a lead engagement platform, says Sendblue is a processor for business customers and names no retention periods. The docs say inbound media links expire after 30 days. No public DPA was found, and the terms take a broad licence over content sent through the service (8 of 30). No deprecation policy. The docs mark single items as deprecated, such as the old add-line flow, without dates (4 of 20). No sub-processor list or data locations. The docs name Twilio and Agora for calling only (2 of 20).

Sinch Messaging APIs + MCP 77

Closed service with general terms. The contracting Sinch entity is named only in the order form (15). Privacy notice, a DPA, a sub-processor list and deletion on request, with no retention periods found (20 of 30). Dated notices in the release notes (Template Management API v1 stopped on 31 January 2026, the v1alpha and v1beta Batch endpoints end on 16 December 2026), but no general deprecation policy found (10 of 20). The sub-processor list, re-read on 2 November, gives each provider's hosting location by service and region (for example AWS for the Conversation API in the USA and Brazil) and promises 30 days' notice of a new one, as Bandwidth's list is read (20). 15 + 20 + 10 + 20 = 65.

Schema & documentation Sinch Messaging APIs + MCP +15

Sendblue 66

We graded the REST API. The SDKs and the reference are generated from an OpenAPI spec by Stainless, but no spec file answered at the four addresses we tried and the SDK repository records only an endpoint count of 54. The published MCP package has JSON Schema inputs on its 18 tools (12 of 25). llms.txt and a Markdown twin of every docs page at /index.md (10). The reference and llms.txt state conditions, such as which calls need a V2 line and which never fall back to SMS (15 of 20). Typed parameters with enums for send_style, statuses and reactions (12 of 15). Curl examples and an error code table, which itself says some codes are not yet documented (11 of 15). Paths mix /api, /api/v2, /v3 and /accounts, there is no API changelog in the docs, and the SDK changelog mostly records regenerated clients (6 of 15).

Sinch Messaging APIs + MCP 81

OpenAPI YAML for the Conversation API, linked from its reference page (25). llms.txt with Markdown pages (10). Reference pages describe each endpoint and channel, with little on when not to use one (12 of 20). Typed JSON with message types per channel, not checked for enums (10 of 15). Examples and error codes in the references (12 of 15). /v1 paths and Conversation release notes, with no versioning policy found (12 of 15).

Reliability Sinch Messaging APIs + MCP +12

Sendblue 61

Read with the hosted lines. status.sendblue.com is an UptimeRobot page, kept at 20 as awarded on 8 October. Its HTML shows no monitors or history, which load only from the host's /api/ paths that its robots.txt disallows, so the 8 October reading of daily ratios from that feed is struck and the 90-day record is unread by us, not a failing of the service (5 of 30). Rate limits are published with numbers per plan and per line (15). The docs say to slow down or spread traffic on a 429 and to verify state after 504 outcome_unknown, with no Retry-After header documented and an idempotency key only on App Card updates (8 of 15). The API page shows a 99.9% Uptime SLA figure and the docs list custom SLAs for enterprise, but no SLA document was found and the terms disclaim availability (3 of 10). The REST API is generally available (10). 20 + 5 + 15 + 8 + 3 + 10 = 61.

Sinch Messaging APIs + MCP 73

Statuspage at status.sinch.com with components and history (20). Read from its own history and incident pages on 2 November (the 1 October count from IsDown, a third-party copy of the page, is struck). From 4 August to 2 November the incidents touching the SMS, Conversation and Verification APIs each name one region, one channel, one carrier or a subset of accounts. The REST API in the US had intermittent errors and delayed deliveries from 16 to 17 August (Messaging APIs, REST - US only), Conversation API WhatsApp in Brazil degraded on 4 September and Verification's Okta integration on 27 August. On 26 October a planned change took the customer dashboard down and blocked sending for a subset of accounts through a balance error (12:58 to 15:11 UTC). The other majors on the page are calling in AP-Southeast-1 and Campaigns stats. Partial incidents read as minor, so minor only (20). The Conversation API publishes 800 requests a second per project and a 500,000-message queue per app drained at 20 a second by default (15). Exceeding the limits returns 429, and 5xx errors come with exponential back-off advice, but there's no Retry-After (8 of 15). No SLA found (0). The SMS and Conversation APIs are generally available. The MCP server is a developer preview (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.

Maintenance & community Sinch Messaging APIs + MCP +11

Sendblue 72

sendblue on npm is at 3.22.0 per the SDK changelog, dated 30 October 2026, with tags v3.20.0 (9 October), v3.20.1 (17 October), v3.21.0 (22 October), v3.21.1 (23 October) and v3.21.2 (30 October) since the last check. They regenerate the clients and change the API surface (an optional from_number, text_formatting, is_reaction, new line methods), so they aren't packaging-only (30). 20 SDK tags from v3.11.0 (17 August) to v3.21.2 (30 October), counted half as SDK tags, still well over three (20). No API changelog in the docs, support by email, and we couldn't read the GitHub issue trackers (6 of 15). Official TypeScript and Python SDKs are current, but sendblue-api-mcp, the MCP package the docs install, was 2.0.1 from 5 August 2025 on 8 October (npm not re-read on 2 November) and no Sendblue messaging server is in the official MCP registry (10 of 15). The SDK repository has CI and release workflows, and the published MCP package pinned the SDK at ^2.0.1 (6 of 10).

Sinch Messaging APIs + MCP 83

Dated Conversation API release notes, the latest dated entry on 14 October 2026, and @sinch/sdk-core 1.8.0, sinch (Python) 2.4.0 and sinch-sdk-java 2.4.0 tagged on 28 October 2026 (30). Release notes on 19 August, 2 October and 14 October, plus SDK tags (Node 1.6.0, 1.7.0, 1.8.0, Python 2.2.0, 2.3.0, 2.4.0, Java 2.2.0, 2.3.0, 2.4.0) in the 90 days (20). Closed service with Conversation release notes. The MCP repository tagged 0.0.1-beta.7 on 30 October 2026, its first tag since 0.0.1-alpha6 on 14 April (10 of 15). Official SDKs current in Node, Python, Java and .NET (15). The MCP repository runs lint, build and tests in CI (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.

Security & auth Sinch Messaging APIs + MCP +9

Sendblue 46

One key pair per account in two headers, never in the URL, plus temporary bearer tokens that can be limited to named phone numbers, expire after 900 seconds by default and can be revoked. Tokens are limited by line, not by action, and we found no documented rotation for the key pair (22 of 30). No read-only key. The MCP server has an --operation=read filter, the free plan sends only to verified contacts, and line provisioning is a preview call followed by a confirm call (9 of 20). Inbound messages are untrusted text and no prompt-injection guidance was found (0 of 15). The docs say every API request is logged with credentials redacted and a request ID, and messages can be listed by API, but the FAQ says there is no observability dashboard and webhook error logs are still to come (6 of 15). Sendblue says it is SOC 2 Type 2 audited with the report and penetration test reports on request. No security.txt, disclosure policy or bug bounty was found (9 of 20).

Sinch Messaging APIs + MCP 55

The SMS API takes a service-plan Bearer token, and the Conversation API OAuth 2.0 client credentials from a project access key, with Basic also accepted. No per-key scopes found (25 of 30). No read-only mode or confirmation step. The MCP server's tool allow-list (--tags, or MCP_TAGS since 0.0.1-beta.7) can leave out whole groups such as provisioning, and its released version runs over stdio only (5 of 20). Inbound messages are untrusted text. Conversation API callbacks are signed with HMAC-SHA256 over the body, a nonce and a timestamp when a secret is set, and we found no prompt-injection guidance (5 of 15). Message and delivery lookups by API, no audit log found (10 of 15). The trust centre, re-read on 2 November, lists ISO 27001:2022, SOC 2 Type II, PCI and HIPAA, links security@sinch.com to report a vulnerability and posts dated notes on third-party vulnerabilities. No security.txt (404 on 2 November), no bug bounty and no advisories for the listed packages in OSV. Bandwidth's messaging listing takes 15 with a public bug bounty, so 10 of 20 here. 25 + 5 + 5 + 10 + 10 = 55.

Score by category

CategoryWeightSendblueSinch Messaging APIs + MCPEdge
Reliability16%6173Sinch Messaging APIs + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6681Sinch Messaging APIs + MCP +15
Agent ergonomics13%7650Sendblue +26
Security & auth14%4655Sinch Messaging APIs + MCP +9
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7283Sinch Messaging APIs + MCP +11
Transparency & trust7%5877Sinch Messaging APIs + MCP +19
Negative events≤1500
TotalB 62.2/100B 67/100

Facts side by side

FactSendblueSinch Messaging APIs + MCP
KindHTTP APIHTTP API
VendorRound One, Inc.Sinch
Hosted endpointhttps://api.sendblue.comhttps://us.sms.api.sinch.com/xms/v1
TransportsHTTP, stdioHTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumPay per use
Price for smsnot published$0.0078 per message
x402nono
LicenceProprietary 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 MITApache-2.0
Tools exposed1859
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-28
Terms last updated2025-03-192026-06-01
Privacy policy last updated2024-05-012025-12-12
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity250k npm/wk, 40k PyPI/wk1 stars, 16k npm/wk, 11k PyPI/wk
Agent reviews2.5/5 (4)3/5 (2)

The panel on both

The one reviewer who reviewed both, Sprint, rates them the same.

ReviewerSendblueSinch Messaging APIs + MCP
SprintLatency and reliability tester 3/5 Per-line limits are published, but sends retry by default 3/5 A 500,000-message queue drained at 20 a second

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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 its status page history isn't readable by crawlers.

Sinch Messaging APIs + MCP

The Conversation API sends SMS, RCS, WhatsApp, Viber and Messenger through one message format, with published rate limits and signed callbacks. Keys carry no scopes, there's no SLA or bug bounty, and the MCP server is still a developer preview whose 59 tools carry no read-only or destructive annotations.

Before you call either

Sendblue

  1. Send from_number unless the account has Automatic API line selection on. It is required on the free shared line, for App Cards and for inline replies; read numbers from GET /api/lines
  2. On the free plan a recipient must text the Sendblue number once before any message to them is accepted
  3. Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six
  4. Branch on error_key in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting
  5. Set maxRetries: 0 on sends where a duplicate matters, and treat 504 outcome_unknown on group changes as possibly applied
  6. 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

Sinch Messaging APIs + MCP

  1. Load the MCP with --tags (or MCP_TAGS) for the channels you need, or all 59 tools land in context
  2. Run the MCP over stdio, and keep any SSE bridge such as supergateway on localhost, since it adds no authentication
  3. Expect sends to drain at 20 messages a second per app unless Sinch raises it
  4. Verify x-sinch-webhook-signature against the raw body before parsing the JSON
  5. Use the regional base URL (us, eu or br) that matches the project; the MCP rejects any other CONVERSATION_REGION at startup

Questions

Which is better for AI agents, Sendblue or Sinch Messaging APIs + MCP?

Sinch Messaging APIs + MCP scores 67 (B) on agent readiness against Sendblue's 62.2 (B), and leads in 5 of 7 scored categories. Sendblue leads on agent ergonomics.

Do Sendblue and Sinch Messaging APIs + MCP need an API key?

Sendblue needs an API key. Sinch Messaging APIs + MCP takes an API key or an OAuth sign-in.

Can an agent call Sendblue and Sinch Messaging APIs + MCP without installing anything?

Yes. Sendblue has a hosted endpoint at https://api.sendblue.com and Sinch Messaging APIs + MCP at https://us.sms.api.sinch.com/xms/v1.

Other comparisons with Sendblue or Sinch Messaging APIs + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.