Head to head · Phone calls · October 2026 research run

Bandwidth Voice API + MCP vs SignalWire Voice API

Bandwidth Voice API + MCP scores 71.7 (BB) on agent readiness against SignalWire Voice API's 69.4 (B), and leads in 3 of 7 scored categories. SignalWire Voice API leads on payments & pricing. Both do phone calls.

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

Which one, for what

Bandwidth Voice API + MCP BB

Best for US and Canada outbound voice agents that need capacity from day one and a carrier-owned network.

Ahead on

  • Reliability, 73 against 53

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Runs on your own machine
  • Free to start without a card

Watch for

Number rental and SIP trunking prices aren't published

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

  • 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

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.

Reliability Bandwidth Voice API + MCP +20

Bandwidth Voice API + MCP 73

Statuspage at status.bandwidth.com with datacentre, market and calling components (20). Read from its own history pages 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 most voice incidents name one datacentre, one country, one local market or a subset of calls. They include LAX outbound calls through that datacentre (10 to 12 August), a subset of JFK voice traffic (14 August), a subset of inbound calls from the Lumen network (7 October), a subset of US toll-free outbound calls (15 to 20 October), France, Japan and single rate centres. Partial incidents read as minor. On 1 September, from 12:15 to 13:29 EDT (74 minutes), outbound calls received an unexpected 404 and failed to connect. The incident page names one affected component, Outbound Calling (SIP) - United States, with inbound and non-US calling unaffected, so it is one direction in one country and read as partial, as hubspot-mcp's regional incident ("many customers in North America") and the toll-free incident here (bland-ai's 14 October outage, which hit every call inbound and outbound, is the major comparison). The 22 October US Voice Traffic major says some customers saw reduced inbound traffic for a carrier's off-network condition, so partial. Minor incidents only (20). Defaults published, 5 calls a second and 100 active sessions, with an outbound queue of 5 minutes of CPS (1,500 calls at 5 CPS), re-read on 2 November (15). 429 is documented with two distinct messages for rate and concurrency, with no Retry-After or backoff guidance (8 of 15). No SLA found (0). The Voice API is generally available. The MCP server is beta (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.

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.

Payments & pricing SignalWire Voice API +7

Bandwidth Voice API + MCP 53

No x402, MPP or L402 (0). US per-minute voice, text-to-speech, recording, transcription and streaming prices are public, re-read on 2 November, but number rental and SIP trunking are quoted by sales (15 of 20). Build trial with 3,000 credits, a US number and no card, re-read on 2 November (20). A trial can be started with band account register, but a person verifies the phone number and creates API credentials, as the Bandwidth messaging listing reads it (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.

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.

Score by category

CategoryWeightBandwidth Voice API + MCPSignalWire Voice APIEdge
Reliability16%7353Bandwidth Voice API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8887Bandwidth Voice API + MCP +1
Agent ergonomics13%6568SignalWire Voice API +3
Security & auth14%7072SignalWire Voice API +2
Payments & pricing10%5360SignalWire Voice API +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7881SignalWire Voice API +3
Transparency & trust7%7574Bandwidth Voice API + MCP +1
Negative events≤1500
TotalBB 71.7/100B 69.4/100

Facts side by side

FactBandwidth Voice API + MCPSignalWire Voice API
KindHTTP APIHTTP API
VendorBandwidthSignalWire
Hosted endpointhttps://voice.bandwidth.com/api/v2no (local only)
TransportsHTTP, stdio, Streamable HTTPHTTP
AuthOAuthAPI key
PricingPay per usePay per use
x402nono
LicencenoneMIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-162026-10-25
Terms last updated2025-09-11not read yet
Privacy policy last updated2026-08-25couldn't be read
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity2 stars, 13k npm/wk, 39k PyPI/wk8 stars, 1.5k npm/wk, 1.3k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates SignalWire Voice API higher, the other way from the total score.

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

Bandwidth Voice API + MCP

5 calls a second and 100 active sessions by default, with excess calls queued, a no-card Build trial and a sub-processor list with locations. Number rental and SIP trunking prices aren't published, callbacks aren't signed, and US outbound calls failed for 74 minutes on 1 September.

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

Bandwidth Voice API + MCP

  1. Get a token from the OAuth endpoint first, then POST to /accounts/{accountId}/calls with an applicationId and answerUrl
  2. Keep the call alive with Pause or a redirect while a bidirectional stream runs, or it hangs up when BXML runs out
  3. Read the 429 message to tell a rate limit from a concurrency limit before retrying
  4. Load the MCP server with BW_MCP_PROFILE=voice to keep the tool list short

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

Questions

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

Bandwidth Voice API + MCP scores 71.7 (BB) on agent readiness against SignalWire Voice API's 69.4 (B), and leads in 3 of 7 scored categories. SignalWire Voice API leads on payments & pricing.

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

Bandwidth Voice API + MCP uses an OAuth sign-in. SignalWire Voice API needs an API key.

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

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

Other comparisons with Bandwidth 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.