Head to head · Phone calls · October 2026 research run

SignalWire Voice API vs Twilio Programmable Voice API + MCP

Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against SignalWire Voice API's 69.4 (B), and leads in 6 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Twilio Programmable Voice API + MCP A

Best for Teams that want the widest number coverage and a managed speech layer (ConversationRelay) behind one vendor, or a published SLA.

Ahead on

  • Reliability, 75 against 53
  • Schema & documentation, 92 against 87
  • Agent ergonomics, 80 against 68
  • Security & auth, 85 against 72
  • Transparency & trust, 81 against 74

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

US outbound at $0.014 a minute, plus $0.0044 for Media Streams or $0.07 for ConversationRelay

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 Twilio Programmable Voice API + MCP +22

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.

Twilio Programmable Voice API + MCP 75

Status page at status.twilio.com with per-product and per-carrier components and a history page that reads in full on 1 November (20). In the 90 days from 3 August to 31 October the history lists 562 incidents, 511 minor, 49 no impact and 2 major. Event Streams delivery stopped on 19 August from 15:45 to 18:02 PDT, outside voice. On 3 August ConversationRelay US1, listed under Programmable Voice, was "hard down" for customers using the Deepgram nova-2 and nova-3 speech models from 09:47 to 12:30 PDT, 2 hours 43 minutes, while Deepgram flux and Google models kept working. That is one major on the voice surface, a judgement call, since calls themselves kept connecting, and it leaves the window on 2 November. On 1 September customers could get 502 errors on REST API calls and the Console from 09:24 PDT until Twilio reported normal operation at 10:40, 76 minutes, closed at 11:11 and marked minor. Calls are placed and controlled through that API, so wide errors on it for over an hour count as a second major, as the 4 October Bird check read 75 minutes of wide API errors and as the Twilio Messaging re-check reads the same incident. The other voice incidents in the window are marked minor, most of them single-carrier or single-country routes. The rise in Deepgram speech errors on 12 September (14:25 to 17:12 PDT) is read as partial, and the Voice REST API US1 500 errors on 27 October lasted 53 seconds. Two majors fall between the one-major and several-majors lines (5). A reading that counts only call placement would give 10. Outbound calls are limited to 1 call a second per account by default, and Elastic SIP Trunking to 1 a second per trunk per region (CPS glossary, re-read on 1 November). Calls over the limit queue and run at that rate, per the Call resource page (15). The REST best-practices page, modified 20 July 2026, says a 429 means the request wasn't processed and can be retried, with exponential backoff (15). The Twilio APIs SLA, last updated 9 April 2026, commits 99.95 per cent to paying customers and 99.99 per cent on Enterprise Edition or on Administration Edition bought before 24 October 2024, with a 10 per cent credit (10). Programmable Voice is generally available (10). 20+5+15+15+10+10 = 75.

Security & auth Twilio Programmable Voice API + MCP +13

SignalWire Voice API 72

Basic auth with a Project ID and an API token, or short-lived Bearer tokens. Tokens are scoped when created, with the Voice scope for calls, new tokens use a swapi_ format since September 2026, and since 8 October a REST endpoint regenerates a token's value in place and every token response carries last_used_at and revoked_at (30). Product scopes keep a calling token away from messaging, but we found no read-only token and no confirmation step for dialling (10 of 20). Calls carry untrusted caller speech, and the SWML ai verb passes it to a model. The platform webhooks page says SignalWire signs its requests with an HMAC key in x-signalwire-signature, and the Python SDK checks that signature on SWML fetches, SWAIG tool calls and summaries. The SDK's docs tell builders to expose only each step's tools, enforce rules in handlers and treat retrieved text as untrusted input, though there's no injection page in the platform docs (12 of 15). Voice logs can be listed by API. We didn't find an account audit log (10 of 15). A vulnerability disclosure policy, an ISO 27001 certificate and a SOC 2 Type 2 attestation letter are linked from signalwire.com/legal, re-read on 1 November. signalwire.com/.well-known/security.txt answers 404, no bug bounty found, and OSV lists no advisories for signalwire-sdk, signalwire or @signalwire/sdk. The same reading as the Telnyx voice listing (10 of 20).

Twilio Programmable Voice API + MCP 85

API keys come as standard, main or restricted. Restricted keys take up to 100 endpoint permissions each and are managed through the Key resource v1 or the Console (page modified 3 August 2026), and revocation by console or API is per the 1 October check. No documented option to send a secret in a query string (30). Restricted keys can leave out endpoints such as call recordings, but no MCP has a confirmation step for dialling or buying numbers (15 of 20). Calls carry untrusted caller speech. Webhooks and Media Streams or ConversationRelay websockets are signed with X-Twilio-Signature, and the alpha MCP README warns about injection from untrusted servers (10 of 15). The Monitor Events API keeps an audit trail of account changes, and every call has a log resource (15). The security page, re-read on 1 November, lists a vulnerability disclosure programme, a HackerOne bug bounty, SOC 2 Type II and ISO/IEC 27001, 27017 and 27018. No security.txt (twilio.com/.well-known/security.txt returns 404 on 1 November). twilio-node has no SECURITY.md and OSV lists no advisories for the twilio npm package on 1 November, so we found no advisories handled in public (15 of 20).

Agent ergonomics Twilio Programmable Voice API + MCP +12

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

Twilio Programmable Voice API + MCP 80

List resources take PageSize (up to 1,000) and PageToken and return next_page_uri, with no field selection (15 of 25). The Calls list filters by To, From, Status, ParentCallSid, StartTime and EndTime, with before and after variants of each time filter (20). Numbered error codes with causes and fixes an agent can act on (20). No idempotency key on call creation. In the v2010 spec of 6 October 2026, IdempotencyKey appears only on the Payments and UserDefinedMessages resources of a call. The docs say a 429 is safe to retry, and webhooks carry an I-Twilio-Idempotency-Token for de-duplication (10 of 20). A call needs only To, From and one of Url, Twiml or ApplicationSid, and official SDKs exist in seven languages (15).

Transparency & trust Twilio Programmable Voice API + MCP +7

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

Twilio Programmable Voice API + MCP 81

Closed service with clear terms, last updated 16 July 2026, re-read on 1 November. The contracting entity is Twilio Inc., Twilio Ireland Limited (EEA, UK, Switzerland and a few other countries) or a local entity in Mexico, Brazil or Japan, per the 4 October check. SDKs are MIT (15). Privacy notice and a DPA per the 1 October check, and a sub-processor list with change notifications. Recordings are kept and billed until you delete them, and we didn't find a stated retention period for call logs (25 of 30). Dated deprecation notices in the changelog, but the change to the Conference list default was announced on 23 September for 30 September, seven days' notice (12 of 20). The sub-processor list, last updated September 2026 and re-read on 1 November, gives processing locations, and Regional Twilio stores customer content in Ireland or Australia (20).

Schema & documentation Twilio Programmable Voice API + MCP +5

SignalWire Voice API 87

Public OpenAPI 3.1 spec at signalwire.com/docs/openapi.json and .yaml, which generates the REST reference (25). llms.txt, and every docs page as Markdown by adding .md or sending Accept: text/markdown (10). The call-commands reference states what each command does, dial, calling.transfer, calling.record, calling.stream, calling.tap and calling.refer, with little on when not to use one (12 of 20). Typed fields from the spec, with commands carried in a params object (12 of 15). Examples per command and an error-codes page (13 of 15). Platform changelog with dated entries and an RSS twin, the newest on 22 October 2026, including transport on dial requests on 19 October (15).

Twilio Programmable Voice API + MCP 92

Public OpenAPI specs in the twilio-oai repository, including twilio_api_v2010 for calls, last regenerated on 6 October 2026 (25). llms.txt with Markdown twins of the docs, 383,795 bytes and last modified 31 October 2026, and a hosted docs MCP in public beta at mcp.twilio.com/docs that searches over 1,800 endpoints (10). The API reference and TwiML pages say when to use Stream for raw audio and ConversationRelay for text only (15 of 20). Typed parameters with enums from the spec, though calls take form-encoded fields (12 of 15). Code samples in every SDK language and a numbered error and warning dictionary (15). API version in the path (2010-04-01) and a public changelog with dated voice entries on 9, 16, 20 and 28 October 2026 (15).

Score by category

CategoryWeightSignalWire Voice APITwilio Programmable Voice API + MCPEdge
Reliability16%5375Twilio Programmable Voice API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8792Twilio Programmable Voice API + MCP +5
Agent ergonomics13%6880Twilio Programmable Voice API + MCP +12
Security & auth14%7285Twilio Programmable Voice API + MCP +13
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8185Twilio Programmable Voice API + MCP +4
Transparency & trust7%7481Twilio Programmable Voice API + MCP +7
Negative events≤1500
TotalB 69.4/100A 79.9/100

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
Price for phone callsnot published$0.0025 per minute of call
x402nono
LicenceMITMIT
Tools exposednone2
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-252026-10-12
Terms last updatednot read yet2026-07-16
Privacy policy last updatedcouldn't be read2026-04-09
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
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)

The panel on both

One of the 2 reviewers who reviewed both rates Twilio Programmable Voice API + MCP 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.

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

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, set interruptible for barge-in, and keep a second speech provider configured
  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

Questions

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

Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against SignalWire Voice API's 69.4 (B), and leads in 6 of 7 scored categories.

Do SignalWire Voice API and Twilio Programmable Voice API + MCP need an API key?

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

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

No hosted endpoint is listed for SignalWire Voice API. Twilio Programmable Voice API + MCP has a hosted endpoint at https://api.twilio.com/2010-04-01.

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.