Head to head · Phone calls · October 2026 research run

SignalWire Voice API vs Sinch Voice API + MCP

SignalWire Voice API and Sinch Voice API + MCP score within a point of each other on agent readiness, 69.4 (B) and 68.5 (B). Sinch Voice API + MCP leads on reliability and agent ergonomics. Both do phone calls.

Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons

Which one, for what

SignalWire Voice API B

Best for Builders who want call logic in documents (SWML) or a hosted AI agent verb, and for teams moving off Twilio's API shape.

Ahead on

  • Security & auth, 72 against 55
  • Payments & pricing, 60 against 53

Also in its favour

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

Watch for

Status page renders only with JavaScript, so its history isn't readable by agents

Sinch Voice API + MCP B

Best for Teams already on Sinch messaging, or voice agents that want a managed STT and TTS relay with barge-in without running their own speech stack.

Ahead on

  • Reliability, 60 against 53
  • Agent ergonomics, 81 against 68

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

Voice API v2, the listed surface, is labelled preview, and Sinch tells projects that must be generally available to use v1

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.

Security & auth SignalWire Voice API +17

SignalWire Voice API 72

Basic auth with a Project ID and an API token, or short-lived Bearer tokens. Tokens are scoped when created, with the Voice scope for calls, new tokens use a swapi_ format since September 2026, and since 8 October a REST endpoint regenerates a token's value in place and every token response carries last_used_at and revoked_at (30). Product scopes keep a calling token away from messaging, but we found no read-only token and no confirmation step for dialling (10 of 20). Calls carry untrusted caller speech, and the SWML ai verb passes it to a model. The platform webhooks page says SignalWire signs its requests with an HMAC key in x-signalwire-signature, and the Python SDK checks that signature on SWML fetches, SWAIG tool calls and summaries. The SDK's docs tell builders to expose only each step's tools, enforce rules in handlers and treat retrieved text as untrusted input, though there's no injection page in the platform docs (12 of 15). Voice logs can be listed by API. We didn't find an account audit log (10 of 15). A vulnerability disclosure policy, an ISO 27001 certificate and a SOC 2 Type 2 attestation letter are linked from signalwire.com/legal, re-read on 1 November. signalwire.com/.well-known/security.txt answers 404, no bug bounty found, and OSV lists no advisories for signalwire-sdk, signalwire or @signalwire/sdk. The same reading as the Telnyx voice listing (10 of 20).

Sinch Voice API + MCP 55

Voice v2 takes a project access key over Basic auth or as an OAuth 2.0 token. v1 uses an application key and secret with signed requests recommended. We found no per-key scopes (25 of 30). No read-only mode or confirmation step. The official MCP server's tool allow-list (--tags, or MCP_TAGS since 0.0.1-beta.7, 30 October) can leave out whole groups, and its released version runs over stdio only, as the Sinch messaging listing reads it (5 of 20). Calls carry untrusted caller speech. Callbacks are signed in v1 and v2, and we found no prompt-injection guidance (5 of 15). Call lookup and call lists by API, no audit log found (10 of 15). The trust centre lists ISO 27001:2022 and SOC 2 Type 2 reports, PCI and HIPAA, and Sinch's security contact for reports. No security.txt (404 on 2 November), no bug bounty and no advisories for @sinch/sdk-core, @sinch/mcp or sinch in OSV (10 of 20, as the Sinch messaging listing). 25 + 5 + 5 + 10 + 10 = 55.

Agent ergonomics Sinch Voice API + MCP +13

SignalWire Voice API 68

A paging guide covers page sizes on list endpoints, with no field selection (15 of 25). Voice logs can be listed and paged. We didn't confirm the full filter set (15 of 20). An error-codes page with a structured errors array (type, code, message, attribute, url) an agent can map to fixes, and command results arrive on status webhooks (15 of 20). No idempotency key. The Python SDK's documented retry policy keeps POSTs from being replayed after a 5xx (8 of 20). One POST endpoint takes every command, a dial needs from, to and a SWML url, and there are official Python and Node SDKs plus Twilio-compatible ones (15).

Sinch Voice API + MCP 81

v2 lists take page_size, with no field selection (15 of 25). The v2 call list pages by link and filters by from, to, call type, time range, result and reason (18 of 20). v1 error reference with codes, and v2 errors carry a type and instance per the SDKs (15 of 20). v2 call, batch and service writes take an Idempotency-Key that returns the cached response for repeats within 10 minutes, and the webhook guide says to deduplicate on ce-id and ce-source (18 of 20). Official SDKs in Node, Python, Java and .NET, but a v2 dial is a nested commands document rather than a few fields (15). 15 + 18 + 15 + 18 + 15 = 81.

Reliability Sinch Voice API + MCP +7

SignalWire Voice API 53

status.signalwire.com redirects to a PagerDuty-hosted page. Re-read on 1 November, its page data names ten services (APIs, SIP Connectivity, WebRTC Connectivity, Video and Conferencing, Website, External Carrier Network, SMS, MMS, AI, Support and Documentation) and says it was created on 23 December 2025, but incidents load only through the page's script and we found no feed, so component history isn't readable (10 of 20). No readable incident history (5). The 1 October note cited a third-party status aggregator for a 14 August degradation; that isn't a first-hand source and isn't used. Trial mode caps queued calls and messages at 10 each, and Space limits are raised on request. The error-codes page, re-read on 1 November, names a rate_limit_exceeded code but no general per-second figures (8 of 15). The error-codes page says to back off and retry on 429, and now also calls every 5xx "Safe to retry with backoff", which for a dial can place a second call. The official Python SDK honours Retry-After with exponential backoff and retries POSTs only on 429 or 503, never on other 5xx, so a dial isn't replayed. No idempotency key (10 of 15). The Service Level Agreement (updated 1 January 2026) commits to 99.95 per cent monthly uptime for SignalWire Cloud APIs on every account, with a 10 per cent credit claimed by ticket within 30 days, per the 2 October read (10). The Calling API is generally available (10). 10 + 5 + 8 + 10 + 10 + 10 = 53.

Sinch Voice API + MCP 60

Statuspage at status.sinch.com with Voice 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 calling incidents each name one region, one channel or a subset of calls. Calling in AP-Southeast-1 degraded from 04:50 to 07:23 UTC on 22 September (labelled critical, one region), PSTN outbound calls saw failed attempts from 05:51 to 09:05 UTC on 2 October (one channel, no region named, posted with no impact level), and Elastic SIP Trunking in US East had non-completed calls for 8 minutes on 9 September. On 26 October a planned change took the customer dashboard down and blocked traffic for a subset of accounts. Partial incidents read as minor, so minor only (20). No account rate limits published for voice. Batch calls take a maxCps setting (1 to 1,000 calls a second), which is a requested pace, not a published limit (0 of 15). The v2 OpenAPI file, readable on 2 November, documents a 429 answer with a Retry-After header on 15 of 17 operations, and an Idempotency-Key header (16 to 128 characters) whose repeats within 10 minutes return the cached response (15). No SLA found (0). Voice API v1 is generally available, but the v2 overview, llms.txt ("recommended for new builds/preview") and the pricing page (Voice Relay and Streams in Public Preview) label v2, the listed surface, as preview, and tell projects that must be GA to use v1. Mixed surfaces take part of the line, as gemini-api's 5 (5 of 10). 20 + 20 + 0 + 15 + 0 + 5 = 60.

Payments & pricing SignalWire Voice API +7

SignalWire Voice API 60

No x402, MPP or L402 (0). US per-minute rates for calls, SIP, numbers, recording and the AI agent runtime published without a login, re-read on 1 November on signalwire.com/pricing (20). New accounts start in trial mode without a card, limited to 1 number and verified destinations, and a card with at least $5 of credit lifts it, re-read on 1 November. The trial page doesn't state a free credit amount (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Sinch Voice API + MCP 53

No x402, MPP or L402 (0). The voice pricing page, re-read on 2 November, gives domestic outbound from $0.01 a minute with a downloadable Voice API price list, and only illustrative inbound, SIP, recording and number prices (15 of 20). Test credits and a test number on signup, with a payment method needed only to upgrade (20). A person signs up in a browser (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightSignalWire Voice APISinch Voice API + MCPEdge
Reliability16%5360Sinch Voice API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8785SignalWire Voice API +2
Agent ergonomics13%6881Sinch Voice API + MCP +13
Security & auth14%7255SignalWire Voice API +17
Payments & pricing10%6053SignalWire Voice API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8179SignalWire Voice API +2
Transparency & trust7%7473SignalWire Voice API +1
Negative events≤1500
TotalB 69.4/100B 68.5/100

Facts side by side

FactSignalWire Voice APISinch Voice API + MCP
KindHTTP APIHTTP API
VendorSignalWireSinch
Hosted endpointno (local only)https://voice.api.sinch.com/v2
TransportsHTTPHTTP, stdio
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-252026-10-28
Terms last updatednot read yet2026-06-01
Privacy policy last updatedcouldn't be read2025-12-12
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity8 stars, 1.5k npm/wk, 1.3k PyPI/wk1 stars, 16k npm/wk, 11k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates SignalWire Voice API higher.

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

SignalWire Voice API

SWML documents, REST commands and a Relay WebSocket client for call control. Status page renders only with JavaScript, so its history isn't readable by agents.

Sinch Voice API + MCP

Voice API v2 adds bidirectional PCM streams, a text relay with barge-in, an OpenAPI file and Idempotency-Key on writes, but Sinch labels it preview and points GA projects to v1. No account rate limits or SLA are published, and v1 release notes stop in 2022.

Before you call either

SignalWire Voice API

  1. Send dial with a url pointing at a SWML document, then use calling.* commands on the returned call ID
  2. Don't retry a dial on a 5xx, whatever the error-codes page says. Retry only on 429 or 503, after Retry-After, or you may place the call twice
  3. Use your own Space subdomain as the host, there is no shared API host
  4. Create a token with only the Voice scope for a calling agent
  5. Verify x-signalwire-signature with the Signing Key before acting on a webhook

Sinch Voice API + MCP

  1. Start new work on Voice API v2 at voice.api.sinch.com, and check the preview label before relying on it in production
  2. Send an Idempotency-Key (a UUID v4) on v2 call, batch and service writes, and reuse it when you retry within 10 minutes
  3. On a 429, wait for the Retry-After seconds before retrying
  4. Trial accounts dial verified numbers only, one call at a time, so verify the test handset first
  5. Verify the webhook signature and deduplicate on ce-id and ce-source, since fallback delivery can repeat events

Questions

Which is better for AI agents, SignalWire Voice API or Sinch Voice API + MCP?

SignalWire Voice API and Sinch Voice API + MCP score within a point of each other on agent readiness, 69.4 (B) and 68.5 (B). Sinch Voice API + MCP leads on reliability and agent ergonomics.

Do SignalWire Voice API and Sinch Voice API + MCP need an API key?

SignalWire Voice API needs an API key. Sinch Voice API + MCP takes an API key or an OAuth sign-in.

Can an agent call SignalWire Voice API and Sinch Voice API + MCP without installing anything?

No hosted endpoint is listed for SignalWire Voice API. Sinch Voice API + MCP has a hosted endpoint at https://voice.api.sinch.com/v2.

Other comparisons with SignalWire Voice API or Sinch Voice API + 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.