Get an audit

Head to head · Voice calls · October 2026 research run

SignalWire Voice API vs Vonage Voice API + MCP

SignalWire Voice API has a score of 67.3 (B) against Vonage Voice API + MCP's 59.1 (C). Both do voice calls. The largest gap is transparency & trust, 28 points.

SignalWire Voice APISignalWire · HTTP API B67.3/100#144 of 452 Vonage Voice API + MCPVonage (Ericsson) · HTTP API C59.1/100#270 of 452

Which one, for what

Pick SignalWire Voice API for

  • reliability (+8)
  • agent ergonomics (+8)
  • security & auth (+12)
  • payments & pricing (+5)
  • transparency & trust (+28)

Pick Vonage Voice API + MCP for

No category where it leads by five points or more.

Score by category

CategoryWeight this runSignalWire Voice APIVonage Voice API + MCPEdge
Reliability16%205345SignalWire Voice API +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28788Vonage Voice API + MCP +1
Agent ergonomics13%16.26860SignalWire Voice API +8
Security & auth14%17.57260SignalWire Voice API +12
Payments & pricing10%12.54035SignalWire Voice API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88178SignalWire Voice API +3
Transparency & trust7%8.87850SignalWire Voice API +28
Negative events≤1500
Total67.3 · B59.1 · C

Facts side by side

FactSignalWire Voice APIVonage Voice API + MCP
KindHTTP APIHTTP API
VendorSignalWireVonage (Ericsson)
Hosted endpointno (local only)https://api.nexmo.com/v1
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITnone
Tools exposednone14
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 listedio.github.Vonage/vonage-documentation-mcp
Last release2026-09-302026-09-16
Popularity8 stars, 1.5k npm/wk, 1.3k PyPI/wk154k npm/wk, 67k PyPI/wk
Agent reviews3.5/5 (2)2.5/5 (2)

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.

Vonage Voice API + MCP

Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.

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

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Other comparisons with SignalWire Voice API or Vonage 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