Head to head · Phone calls · October 2026 research run

SignalWire Voice API vs Vonage Voice API + MCP

SignalWire Voice API scores 69.4 (B) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. 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

  • Reliability, 53 against 45
  • Agent ergonomics, 68 against 60
  • Payments & pricing, 60 against 53
  • Maintenance & community, 81 against 51
  • Transparency & trust, 74 against 49

Also in its favour

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

Watch for

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

Vonage Voice API + MCP C

Best for Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine
  • Free to start without a card

Watch for

First call needs an application, a private key and a signed JWT

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.

Maintenance & community SignalWire Voice API +30

SignalWire Voice API 81

signalwire-python 3.7.5 tagged on 25 October 2026, after 3.6.0 (5 October), 3.7.0 (12 October) and 3.7.1 to 3.7.4, and signalwire-js 4.0.0-rc.5 on 14 October. Changelog entries on 19 and 22 October (30). 13 Python SDK releases from 3.4.0 on 25 August to 3.7.5, plus JS release candidates, and dated changelog entries most weeks (20). Closed service with an active changelog and community support. We didn't sample issue replies (8 of 15). Official Python and Node SDKs current (15). The Python SDK runs test, multi-OS, nightly and docs-audit workflows and Renovate for dependencies. We couldn't see run results (8 of 10). The SDK changelog since 3.5.1 has no removals or breaking changes. 3.7.0 changes how new search indexes embed text and keeps existing indexes working, with an option for the old behaviour. 30 + 20 + 8 + 15 + 8 = 81.

Vonage Voice API + MCP 51

Vonage's SDKs bundle every Vonage API, so their releases count here only where they change voice code, as the Groq speech-to-text and Gemini embedding listings read their SDKs. vonage-java-sdk v9.15.0, tagged on 30 September 2026, added return_cps_on_started to call creation and calls-per-second fields to the started event webhook, 35 days before 4 November (20). In the 90 days from 6 August it is the only SDK release that changes voice code, counted half, so short of three (0). vonage-node-sdk v3.30.0 and v3.30.1, vonage-python-sdk v4.9.0 and v4.9.1, vonage-java-sdk v9.13.0, v9.13.1, v9.14.0 and v9.15.1, vonage-php-sdk-core 4.15.0 and vonage-ruby-sdk 7.36.0 change other APIs, shared client code or formatting. The Python voice package last changed on 20 July (1.5.1, in v4.8.2), and the Node voice package had only version bumps and a lint reformat. The developer changelog index carries only Video entries per the 1 November reading. Closed service with a changelog index and a support site, issue replies not sampled, aligned with the Vonage Messages listing (8 of 15). Official SDKs in six languages (15). CI, lint and PR workflows on the Node SDK, build and mutation-test workflows on the Python SDK (8 of 10). 20 + 0 + 8 + 15 + 8 = 51.

Transparency & trust SignalWire Voice API +25

SignalWire Voice API 74

Closed service under the SignalWire Cloud Agreement (15). Privacy policy, a Data Processing Addendum and a cloud sub-processor list are published. We didn't find retention periods for call records or recordings (20 of 30). Dated deprecation notice for the token format, old tokens keep working (15 of 20). The sub-processor PDF names five cloud providers with countries (AWS in the US, Bahrain and South Africa, DigitalOcean in seven countries, Google in the US, Microsoft in four, Vultr in Australia), but service-specific sub-processors are listed without purposes or locations and the PDF carries no date (15 of 20).

Vonage Voice API + MCP 49

Closed service. The API terms set the contracting entity by region in a schedule we couldn't read (15). Per the 2 October check (www.vonage.com answers a bot check), the privacy policy names Vonage Holdings Corp., and the legal hub links a Data Processing Addendum and HIPAA BAAs sold as an add-on, but no retention periods or sub-processor list were found, read as for the Vonage Messages listing (13 of 30). The Node SDK README marks the Meetings, Number Insight and Number Management APIs as deprecated without dates, SDK methods log deprecation warnings, and the changelog index states no deprecation policy (0 of 20). No sub-processor list or data locations found (0). 15 + 13 + 0 + 0 = 28.

Reliability SignalWire Voice API +8

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.

Vonage Voice API + MCP 45

Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 4 November, list Voice entries from 6 August labelled minor or none. Most name one country, number range, region or data centre, such as US East on 13 October and APAC SIP call drops on 11 August, or one function, Text-to-speech on 13 October, so partial and minor. 'Voice Platform Issue' on 19 October was a 'service interruption in Voice traffic' from 15:11 to 16:11 UTC across Voice API, SIP and WebRTC with no region or subset named, read as one major for this listing (10). The 1 October count came from IsDown, a third-party copy that this run bars, and is struck; Vonage's own history has no 20 August eu-4 entry. Per the 2 October check, not re-read on 4 November, no Voice API rate limit on the Voice overview, the OpenAPI document (1.10.0), the API error catalogue or llms.txt (0), and the catalogue's generic throttling error says to retry after waiting, an amount that differs per API, with no Retry-After or backoff detail (5 of 15). No SLA found (0). Voice API is generally available (10). 20 + 10 + 0 + 5 + 0 + 10 = 45.

Agent ergonomics SignalWire Voice API +8

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

Vonage Voice API + MCP 60

List calls takes page_size from 1 to 100 (default 10) and record_index, with no field selection (15 of 25). Filters on status, date_start, date_end and conversation_uuid, with ordering (20). A shared API error catalogue with codes an agent can look up (15 of 20). No idempotency key or safe-retry guidance found (0). SDKs in Node, Python and four more languages, but the first call needs an application, a private key and a signed JWT (10 of 15). Per the 2 October check, not re-read on 4 November.

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.

Vonage Voice API + MCP 53

No x402, MPP or L402 (0). Per-minute rates are in a downloadable pricing sheet, and the pricing page returns 403 to automated readers (15 of 20). €2 of test credit without a card (20). A person signs up in a browser (0). Per the 2 October check, not re-read on 4 November. 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 APIVonage Voice API + MCPEdge
Reliability16%5345SignalWire Voice API +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8788Vonage Voice API + MCP +1
Agent ergonomics13%6860SignalWire Voice API +8
Security & auth14%7273Vonage Voice API + MCP +1
Payments & pricing10%6053SignalWire Voice API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8151SignalWire Voice API +30
Transparency & trust7%7449SignalWire Voice API +25
Negative events≤1500
TotalB 69.4/100C 61.2/100

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
Price for phone callsnot published$0.005 per minute of call
x402nono
LicenceMITnone
Tools exposednone14
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last release2026-10-252026-10-21
Terms last updatednot read yetcouldn't be read
Privacy policy last updatedcouldn't be readcouldn't be read
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularity8 stars, 1.5k npm/wk, 1.3k PyPI/wk154k npm/wk, 67k PyPI/wk
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate 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.

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

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

Questions

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

SignalWire Voice API scores 69.4 (B) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 5 of 7 scored categories.

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

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

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

No hosted endpoint is listed for SignalWire Voice API. Vonage Voice API + MCP has a hosted endpoint at https://api.nexmo.com/v1.

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.