Head to head · Phone calls · October 2026 research run

Plivo Voice API vs SignalWire Voice API

SignalWire Voice API scores 69.4 (B) on agent readiness against Plivo Voice API's 66.3 (B), and leads in 4 of 7 scored categories. Plivo Voice API 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

Plivo Voice API B

Best for Cost-sensitive voice agents built on Pipecat, LiveKit, Vapi or Retell, and for India traffic.

Ahead on

  • Reliability, 80 against 53

Also in its favour

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

Watch for

1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account

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 59
  • Security & auth, 72 against 50

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.

Schema & documentation SignalWire Voice API +28

Plivo Voice API 59

No OpenAPI spec found (0). llms.txt at plivo.com/docs/llms.txt (10). Reference pages state what each endpoint and XML element does, with little on when not to use one (12 of 20). Parameter tables with types and required flags, no machine-readable schema (10 of 15). Examples in each SDK language, and hangup causes such as 5030, 5180 and 5190 are documented, though there's no full error catalogue in one place (12 of 15). Versioned v1 path 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).

Reliability Plivo Voice API +27

Plivo Voice API 80

Statuspage at status.plivo.com with components and a readable history feed (20). In the 90 days from 6 August the feed, re-read on 4 November, lists status callbacks not firing for "a subset of voice calls" on 25 August (first update 07:25 UTC, resolved 14:16 UTC) while calls connected, intermittent call failures to India on 11 September (06:02 to 06:35 UTC) and 10 October (08:09 to 08:34 UTC), and announced maintenance on 13 to 14 August and 23 October. Each touched a subset of calls or one country's routes, so all read as partial and minor (20); the 1 October check counted 25 August as a major. Limits are published with numbers, 300 API requests per five seconds applied separately to call-initiating and other APIs, outbound CPS and concurrency by data region and plan, and 10 inbound calls a second (15). 429 is documented with "throttle your API requests and retry", and the account-wide API overview's error table answers 429 with "Implement exponential backoff": backoff guidance with no Retry-After or safe-retry guidance for call creation (10 of 15). Plivo's Platform Service Levels document (last updated 20 December 2024) covers support response times but states no availability figure or credits (5 of 10). Voice API is generally available (10). 20 + 20 + 15 + 10 + 5 + 10 = 80.

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.

Security & auth SignalWire Voice API +22

Plivo Voice API 50

HTTP Basic auth with an Auth ID and Auth Token per account or subaccount. No per-key scopes found (20). Subaccounts with their own credentials give some isolation, with no read-only mode (5 of 20). Calls carry untrusted caller speech. Webhooks are signed, and we found no prompt-injection guidance (5 of 15). Call detail records and recordings by API, no customer-facing audit log found (10 of 15). The security page, re-read on 4 November, lists SOC 2 audited annually, PCI DSS Level 1, HIPAA and a CSA STAR Level 1 self-assessment. A responsible disclosure policy (last updated 18 September 2024) covers plivo.com and Plivo's products and sends reports to security@plivo.com; the 1 October check missed it. No security.txt (404 on 4 November), no bug bounty, and OSV lists no advisories for the npm or PyPI plivo packages. Read as signalwire-voice (a disclosure policy and SOC 2, no bounty) (10 of 20). 20 + 5 + 5 + 10 + 10 = 50.

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

Score by category

CategoryWeightPlivo Voice APISignalWire Voice APIEdge
Reliability16%8053Plivo Voice API +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5987SignalWire Voice API +28
Agent ergonomics13%7068Plivo Voice API +2
Security & auth14%5072SignalWire Voice API +22
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7881SignalWire Voice API +3
Transparency & trust7%7174SignalWire Voice API +3
Negative events≤1500
TotalB 66.3/100B 69.4/100

Facts side by side

FactPlivo Voice APISignalWire Voice API
KindHTTP APIHTTP API
VendorPlivoSignalWire
Hosted endpointhttps://api.plivo.com/v1no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITMIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-10-25
Terms last updated2026-04-29not read yet
Privacy policy last updated2026-05-27couldn'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 waiveryesnot read yet
Popularity102 stars, 51k npm/wk, 69k PyPI/wk8 stars, 1.5k npm/wk, 1.3k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Plivo Voice API

US outbound at $0.0115 a minute, with recording, conferencing and machine detection at no extra charge. 1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account.

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

Plivo Voice API

  1. Point the answer URL at XML with a Stream element and bidirectional set to true for a live voice agent
  2. Check concurrency before dialling out in bulk. Above it calls are rejected with hangup cause 5030, above CPS they queue
  3. Don't rely on the status callback alone to learn a call ended. Poll the call if the webhook doesn't arrive
  4. Validate webhook signatures before acting on call events

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, Plivo Voice API or SignalWire Voice API?

SignalWire Voice API scores 69.4 (B) on agent readiness against Plivo Voice API's 66.3 (B), and leads in 4 of 7 scored categories. Plivo Voice API leads on reliability.

Do Plivo Voice API and SignalWire Voice API need an API key?

Both need an API key.

Can an agent call Plivo Voice API and SignalWire Voice API without installing anything?

Plivo Voice API has a hosted endpoint at https://api.plivo.com/v1. No hosted endpoint is listed for SignalWire Voice API.

Other comparisons with Plivo Voice API 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.