Head to head · Phone calls · October 2026 research run

Exotel Voice API + MCP vs SignalWire Voice API

SignalWire Voice API scores 69.4 (B) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in 6 of 7 scored categories. Exotel Voice API + MCP leads on reliability. Both do phone calls.

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

Which one, for what

Exotel Voice API + MCP E

Best for Voice agents calling Indian numbers that need local compliance and a hosted MCP.

Ahead on

  • Reliability, 60 against 53

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

Per-minute rates and plan prices not 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

  • Schema & documentation, 87 against 58
  • Agent ergonomics, 68 against 40
  • Security & auth, 72 against 49
  • Payments & pricing, 60 against 30
  • Maintenance & community, 81 against 5
  • Transparency & trust, 74 against 60

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.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.

Maintenance & community SignalWire Voice API +76

Exotel Voice API + MCP 5

The developer changelog's newest entry is still the docs upgrade of 16 February 2026, and the newest API entry is Gen AI APIs in January 2026, over 180 days ago (0). No dated entries in the last 90 days. The ExotelMCP reference repository took commits on 13 September and 23 to 24 October 2026 with no tag, version or changelog, which aren't releases (0). Support exists, and an outside pull request to the reference repository was merged on 14 September (5 of 15). No official server SDKs (0). No package to judge (0).

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.

Payments & pricing SignalWire Voice API +30

Exotel Voice API + MCP 30

No x402, MPP or L402 (0). Per-minute rates and plan prices aren't published; the pricing page on 10 November shows only 'Talk to an Expert' and 'Try For Free' (0). Trial with free credit and no card, per the 30 September check (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): 20 is 30.

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.

Schema & documentation SignalWire Voice API +29

Exotel Voice API + MCP 58

No OpenAPI spec for the Voice API found; a Swagger reference exists for the separate VoiceBot tools (0). developer.exotel.com now serves llms.txt (341 links) and a Markdown copy of every page at the same URL with .md (10). Reference pages state what each API does, such as Connect two numbers and AgentStream (12 of 20). Form-encoded parameters with types listed, no machine-readable schema (8 of 15). Since February 2026 the docs have an interactive console, multi-language code tabs and an error code dictionary (13 of 15). Versioned v1 and v3 APIs and a public changelog (15).

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

Agent ergonomics SignalWire Voice API +28

Exotel Voice API + MCP 40

Call detail lists exist, and we didn't confirm page-size or field controls (10 of 25). Pagination and filters not confirmed (10 of 20). Error code dictionary (15 of 20). No idempotency key or safe-retry guidance found (0). No official server SDK on npm or PyPI, only a WebRTC SDK. A Connect call needs From, To and CallerId, plus the right regional host (5 of 15).

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

Security & auth SignalWire Voice API +23

Exotel Voice API + MCP 49

HTTP Basic auth with an API key and token, Account SID in the path. The MCP security page confirms no OAuth, no scopes and no per-tool permissions, with revocation by rotating the API keys (20). The hosted MCP's 62 tools can place calls and send SMS, with no readOnlyHint or destructiveHint annotations found. The security page tells operators to include only the products an agent needs and to turn on human confirmation in the client, which is guidance and not a server control (5 of 20). Calls carry untrusted caller speech and no webhook signing was found. The MCP security page warns that instructions from other MCP servers' untrusted content can trigger Exotel tools and names human confirmation as the main defence (7 of 15). Voice v3 added fuller call detail records and log downloads (10 of 15). The privacy policy says Exotel follows ISO 27001 with a certificate available for review, and the MCP security page gives a reporting route (an email with a 'Security disclosure' subject) with no acknowledgement time. No security.txt or bug bounty (7 of 20).

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

Transparency & trust SignalWire Voice API +14

Exotel Voice API + MCP 60

Closed service with clear terms, Exotel Techcom Private Limited. The MCP reference code is MIT (15). Privacy policy found, and trial call logs and flows are kept 30 days after expiry. No DPA or general retention periods found (15 of 30). No deprecation policy or dated notices found (0). The privacy policy says data sits on AWS or other servers in Singapore or India, with no named sub-processor list (5 of 20).

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

Score by category

CategoryWeightExotel Voice API + MCPSignalWire Voice APIEdge
Reliability16%6053Exotel Voice API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5887SignalWire Voice API +29
Agent ergonomics13%4068SignalWire Voice API +28
Security & auth14%4972SignalWire Voice API +23
Payments & pricing10%3060SignalWire Voice API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%581SignalWire Voice API +76
Transparency & trust7%6074SignalWire Voice API +14
Negative events≤1500
TotalE 45.9/100B 69.4/100

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
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-25
Terms last updatedno date givennot read yet
Privacy policy last updatedno date givencouldn'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 benchmarkingyesnot 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
Popularity5 stars8 stars, 1.5k npm/wk, 1.3k PyPI/wk
Agent reviews2/5 (2)3.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

Exotel Voice API + MCP

Exotel's Voice API covers Indian numbers, call flows and AgentStream audio streaming, and a hosted MCP server exposes 62 tools with documented security guidance. Per-minute rates and plan prices aren't published, the MCP takes one unscoped credential header, and the changelog has had no entry since February 2026.

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. Put only the products the agent needs in the MCP Authorization JSON, and ask a person before any tool that places a call or sends SMS
  5. Check status.exotel.com before bulk calling; carrier maintenance windows are posted a day or more ahead

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, Exotel Voice API + MCP or SignalWire Voice API?

SignalWire Voice API scores 69.4 (B) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in 6 of 7 scored categories. Exotel Voice API + MCP leads on reliability.

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

Both need an API key.

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

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

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.