Head to head · Phone calls · October 2026 research run

Plivo Voice API vs Twilio Programmable Voice API + MCP

Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against Plivo Voice API's 66.3 (B), and leads in 5 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 75

Watch for

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

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

  • Schema & documentation, 92 against 59
  • Agent ergonomics, 80 against 70
  • Security & auth, 85 against 50
  • Maintenance & community, 85 against 78
  • Transparency & trust, 81 against 71

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine

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.

Security & auth Twilio Programmable Voice API + MCP +35

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.

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

Schema & documentation Twilio Programmable Voice API + MCP +33

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

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

Agent ergonomics Twilio Programmable Voice API + MCP +10

Plivo Voice API 70

List calls takes limit and offset, with no field selection (15 of 25). Call and recording lists filter by number, time and duration (20). HTTP errors plus documented hangup causes an agent can map to a fix (15 of 20). No idempotency key on call creation. Calls over the CPS limit are queued on the Voice API, and the only retry advice is to wait for active calls to end (5 of 20). Official SDKs in Node, Python and other languages, and a call needs from, to and answer_url (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 +10

Plivo Voice API 71

Closed service with clear terms at plivo.com/legal/tos (15). Privacy policy, encryption at rest and in transit, recordings kept 90 days free, and a sub-processor list. We didn't find a DPA or call-log retention periods (20 of 30). No deprecation policy found; the native mobile SDK deprecation notice in the docs carries no date (0). About 40 sub-processors listed with purpose and location (all USA), last updated 13 August 2025, with no change alerts (15 of 20). 15 + 20 + 0 + 15 = 50.

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

Maintenance & community Twilio Programmable Voice API + MCP +7

Plivo Voice API 78

plivo-cli v1.3.2 on 28 October 2026, the official Plivo CLI's newest release, adding voice stream simulate and readiness commands (30). In the 90 days from 6 August, 13 plivo-cli releases from v0.3.0 (28 August) to v1.3.2 (v1.3.1 was tagged but never released), plivo-go 7.61.0, plivo-java 5.51.0 and plivo-dotnet 5.53.0 (19 August, Caller Reputation parameters) and plivo-python v4.63.0 (25 September, an auto-pagination fix), well over three (20). The product changelog's newest entry is 6 January 2025. Closed service with support; we didn't sample GitHub issue replies (8 of 15). Official SDKs current in several languages (15). CI and dependency state not checked, and plivo-node hasn't released since 28 July (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.

Twilio Programmable Voice API + MCP 85

twilio-node 6.2.0 tagged on 2026-10-12, still the newest tag on 1 November, 20 days old (30). Releases 6.1.0, 6.1.1, 6.1.2 and 6.2.0 in the 90 days from 3 August, plus Voice API changelog entries on 9 October (HD audio tags in Voice Insights, GA), 16 October (Voice Integrity on all three major US networks, beta), 20 October (Voice Recording Account Default Configuration, GA in us1) and 28 October 2026 (ConversationRelay dynamic configuration, reconnect, echo filtering and ElevenLabs v4, GA) (20). Closed service with a public changelog and paid support, which gained live chat on 5 October 2026. The twilio-labs/mcp repo has had no commit since v0.7.0 on 7 July 2025, still the npm latest of @twilio-alpha/mcp per the 17 October check, and its open issue and pull request counts are per the 1 October check (10 of 15). Official SDKs current in seven languages (15). twilio-node needs Node 20 or later, so dependencies are current (10).

Reliability Plivo Voice API +5

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.

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.

Score by category

CategoryWeightPlivo Voice APITwilio Programmable Voice API + MCPEdge
Reliability16%8075Plivo Voice API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5992Twilio Programmable Voice API + MCP +33
Agent ergonomics13%7080Twilio Programmable Voice API + MCP +10
Security & auth14%5085Twilio Programmable Voice API + MCP +35
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7885Twilio Programmable Voice API + MCP +7
Transparency & trust7%7181Twilio Programmable Voice API + MCP +10
Negative events≤1500
TotalB 66.3/100A 79.9/100

Facts side by side

FactPlivo Voice APITwilio Programmable Voice API + MCP
KindHTTP APIHTTP API
VendorPlivoTwilio
Hosted endpointhttps://api.plivo.com/v1https://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-282026-10-12
Terms last updated2026-04-292026-07-16
Privacy policy last updated2026-05-272026-04-09
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesyes
Popularity102 stars, 51k npm/wk, 69k 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

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.

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

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

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, Plivo Voice API or Twilio Programmable Voice API + MCP?

Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against Plivo Voice API's 66.3 (B), and leads in 5 of 7 scored categories. Plivo Voice API leads on reliability.

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

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

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

Yes. Plivo Voice API has a hosted endpoint at https://api.plivo.com/v1 and Twilio Programmable Voice API + MCP at https://api.twilio.com/2010-04-01.

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