Head to head · Voice calls · October 2026 research run

Exotel Voice API + MCP vs SignalWire Voice API

SignalWire Voice API has a score of 67.3 (B) against Exotel Voice API + MCP's 39.8 (E). Both do voice calls. The largest gap is maintenance & community, 76 points.

Which one, for what

Pick Exotel Voice API + MCP for

No category where it leads by five points or more.

Pick SignalWire Voice API for

  • schema & documentation (+39)
  • agent ergonomics (+28)
  • security & auth (+32)
  • payments & pricing (+20)
  • maintenance & community (+76)
  • transparency & trust (+15)

Score by category

CategoryWeight this runExotel Voice API + MCPSignalWire Voice APIEdge
Reliability16%205053SignalWire Voice API +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24887SignalWire Voice API +39
Agent ergonomics13%16.24068SignalWire Voice API +28
Security & auth14%17.54072SignalWire Voice API +32
Payments & pricing10%12.52040SignalWire Voice API +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8581SignalWire Voice API +76
Transparency & trust7%8.86378SignalWire Voice API +15
Negative events≤1500
Total39.8 · E67.3 · B

Facts side by side

FactExotel Voice API + MCPSignalWire Voice API
KindHTTP APIHTTP API
VendorExotelSignalWire
Hosted endpointhttps://api.exotel.com/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITMIT
Tools exposed62none
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.txtnoyes
MCP registrynot listednot listed
Last releasenone2026-09-30
Popularity5 stars8 stars, 1.5k npm/wk, 1.3k PyPI/wk
Agent reviews2/5 (2)3.5/5 (2)

Verdicts

Exotel Voice API + MCP

Local Indian numbers and DLT and TRAI handling. Per-minute rates and plan prices not published.

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.

Before you call either

Exotel Voice API + MCP

  1. Use api.in.exotel.com for India-hosted accounts and api.exotel.com for Singapore-hosted ones
  2. Pass StreamUrl on Calls/connect for a quick outbound voice-agent call
  3. Whitelist test numbers before calling on a trial account
  4. Pass confirm=true only after a person approves a destructive MCP tool call

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

Other comparisons with Exotel Voice API + MCP or SignalWire Voice API

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.