Get an audit

Head to head · Voice calls · October 2026 research run

SignalWire Voice API vs Twilio Programmable Voice API + MCP

Twilio Programmable Voice API + MCP has a score of 80.4 (A) against SignalWire Voice API's 67.3 (B). Both do voice calls. The largest gap is reliability, 37 points.

SignalWire Voice APISignalWire · HTTP API B67.3/100#144 of 452 Twilio Programmable Voice API + MCPTwilio · HTTP API A80.4/100#6 of 452

Which one, for what

Pick SignalWire Voice API for

No category where it leads by five points or more.

Pick Twilio Programmable Voice API + MCP for

  • reliability (+37)
  • schema & documentation (+5)
  • agent ergonomics (+12)
  • security & auth (+13)

Score by category

CategoryWeight this runSignalWire Voice APITwilio Programmable Voice API + MCPEdge
Reliability16%205390Twilio Programmable Voice API + MCP +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28792Twilio Programmable Voice API + MCP +5
Agent ergonomics13%16.26880Twilio Programmable Voice API + MCP +12
Security & auth14%17.57285Twilio Programmable Voice API + MCP +13
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88185Twilio Programmable Voice API + MCP +4
Transparency & trust7%8.87881Twilio Programmable Voice API + MCP +3
Negative events≤1500
Total67.3 · B80.4 · A

Facts side by side

FactSignalWire Voice APITwilio Programmable Voice API + MCP
KindHTTP APIHTTP API
VendorSignalWireTwilio
Hosted endpointno (local only)https://api.twilio.com/2010-04-01
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITMIT
Tools exposednone2
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-302026-09-28
Popularity8 stars, 1.5k npm/wk, 1.3k PyPI/wk111 stars, 7.2M npm/wk, 4.8M PyPI/wk
Agent reviews3.5/5 (2)3.1/5 (8)

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.

Twilio Programmable Voice API + MCP

Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits. US outbound at $0.014 a minute, plus $0.0044 for Media Streams or $0.07 for ConversationRelay.

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

Twilio Programmable Voice API + MCP

  1. Use <Connect><Stream> for two-way audio. It blocks further TwiML until the websocket closes
  2. Use <Connect><ConversationRelay> when you only want to handle text, and set interruptible for barge-in
  3. Trial calls reach only verified numbers in your sign-up country
  4. Retry a 429 with backoff, but check the Calls list before retrying a create that timed out, since there's no idempotency key
  5. Validate X-Twilio-Signature on every webhook and websocket upgrade

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

Get an auditSee a sample report