Head to head · Phone calls · October 2026 research run
Plivo Voice API vs Telnyx Voice API + MCP
Telnyx Voice API + MCP scores 74.4 (BB) 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 and security & auth. Both do phone calls.
Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons
Which one, for what
Best for Cost-sensitive voice agents built on Pipecat, LiveKit, Vapi or Retell, and for India traffic.
Ahead on
- Reliability, 80 against 75
- Security & auth, 50 against 45
Also in its favour
- 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
Best for Cost-sensitive US outbound voice agents and for agents that must onboard and pay without a person.
Ahead on
- Schema & documentation, 93 against 59
- Agent ergonomics, 90 against 70
- Payments & pricing, 66 against 60
- Maintenance & community, 83 against 78
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
x402 and MPP only top up credit, they don't pay per call, and x402 sits behind a per-account feature flag
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 Telnyx Voice API + MCP +34
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).
Telnyx Voice API + MCP 93
Public OpenAPI 3 spec in the team-telnyx/openapi repository, synced from Telnyx's internal repository on 16 October 2026 (25). llms.txt on both developers.telnyx.com and telnyx.com, with Markdown doc pages and machine-readable pricing (10). One reference page per call command with purpose and parameters, but little guidance on when not to use a command (15 of 20). Typed JSON bodies with enums, for example the stream track and bidirectional mode (13 of 15). Request examples per command and a page of API error codes (15). Versioned /v2 path and public release notes (15).
Agent ergonomics Telnyx Voice API + MCP +20
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).
Telnyx Voice API + MCP 90
List endpoints take page size and number, with no field selection (15 of 25). Filters and pagination on list endpoints (20). JSON errors with a code, title and detail, and a documented code list (20). Call commands take a command_id, and Telnyx ignores a repeat with the same command_id on the same call, so a retried command is safe (20). Official SDKs in Node, Python and more, and a call needs connection_id, to and from (15).
Payments & pricing Telnyx Voice API + MCP +6
Plivo Voice API 60
No x402, MPP or L402 (0). US per-minute, number, recording and transcription prices published without a login (20). $10 trial credit without a card, per the pricing page cited in the listing (20). A person signs up in a browser and verifies a phone number (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Telnyx Voice API + MCP 66
x402 exists on Telnyx's own API at /v2/x402/credit_account (USDC on Base), with MPP at /v2/machine-payments/account-credit, but both top up account credit rather than pay per call. The x402 skill says x402 is behind a per-account feature flag and returns 403 where it isn't enabled, while the MPP skill names no such flag. Per-payment limits are stated only in 422 errors (25 of 40). Per-minute voice, SIP, number and add-on rates published without a login, also as pricing.md (20). No free credit, a new account starts at zero (0). An agent can sign up through /v2/bot_challenge and /v2/bot_signup, collect the email link, mint a key at /v2/api_keys and fund the account by MPP with Tempo USDC, or x402 where enabled, with no browser (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 40 is 60 at 30 each, so 65 is 66.
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.
Telnyx Voice API + MCP 75
Status page at status.telnyx.com (run on incident.io) with a readable incident feed and history (20). Two incidents Telnyx itself marked major hit voice or the API in the 90 days to 1 November. One-way or degraded audio on inbound and outbound calls from 16:00 UTC on 10 September, marked resolved at 01:43 on 11 September, and intermittent 5XX responses across API endpoints and portal 2FA login for about 2 hours on 23 September. Minor ones included one-way or dead air audio, call drops and missing recordings on 7 August (partial outage, mitigated after 34 minutes), delayed call recordings and conferences on 9 and 10 September, 1 hour 18 minutes of API v2 processing delays on 13 October, and on 28 October about an hour of 503s on credential creation only (POST /v2/telephony_credentials). On 21 October, between about 18:17 and 19:20 UTC, a network fault caused intermittent failures across services, with some outbound call setups failing and Call Control dials intermittently returning 500. Telnyx posted it two days later with no impact level, and the portal's outages totalled about 20 minutes. Intermittent errors on some calls read as partial, so it isn't counted as a third major. Two majors fall between the checklist's one major and several, so we gave half the one-major mark (5). Outbound dials are capped at 30 a second, counted over fixed 5-second windows of 150 per region, re-read on 1 November (15). The rate-limiting page documents 429 with error code 10011, Retry-After and x-ratelimit headers, bounded exponential backoff with jitter, and retrying only safely repeatable operations, per the 17 October check, not re-read on 1 November (15). A machine-readable SLA at telnyx.com/ai/sla.json states 99.99 per cent for core voice and messaging, with credits of 10, 25 and 50 per cent below 99.99, 99.9 and 99.0. pricing.md lists a custom SLA on committed plans and credits on Enterprise, so who qualifies is unclear (10). Voice API is generally available (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.
Security & auth Plivo Voice API +5
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.
Telnyx Voice API + MCP 45
Bearer API keys created and revoked in the portal, with an optional expiry date and a documented rotation procedure, re-read on 1 November. We found no per-key scopes. The hosted MCP can also be authorised through the Telnyx portal for Claude connectors (20). No read-only key mode found. The hosted MCP's invoke_api_endpoint carries destructiveHint true but can still dial calls or buy numbers with no confirmation step on Telnyx's side (0 of 20). Calls carry untrusted caller speech. Call Control webhooks are signed, and we found no prompt-injection guidance (5 of 15). Call records and call events by API. We didn't find an account audit log (10 of 15). SOC 2 Type II and ISO 27001 per Telnyx's compliance file. telnyx-node's SECURITY.md, re-read on 1 November, sends SDK reports to Stainless and Telnyx service issues to support@telnyx.com. security.txt returned 404 at both locations on 1 November, and no bug bounty found (10 of 20). 20 + 0 + 5 + 10 + 10 = 45.
Maintenance & community Telnyx Voice API + MCP +5
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.
Telnyx Voice API + MCP 83
telnyx-node v7.29.0 tagged on 2026-10-28, after v7.27.0 and v7.28.0 on 21 and 22 October (30). 17 telnyx-node releases in the 90 days to 1 November, from v7.13.0 on 4 August to v7.29.0 (20). Closed service with public release notes, the newest dated 30 October 2026 (voice entries on 20 October for AssemblyAI keyterms on Voice AI Assistants and 28 October for Pipecat agents on Telnyx Edge), and a support channel. We couldn't read GitHub issue replies (8 of 15). Current official SDKs, and the MCP is in the official registry as io.github.team-telnyx/telnyx, though the newest registry version is still 6.29.3 of March 2026 (15). Release automation runs in CI (10). 30 + 20 + 8 + 15 + 10 = 83.
Score by category
| Category | Weight | Plivo Voice API | Telnyx Voice API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 75 | Plivo Voice API +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 93 | Telnyx Voice API + MCP +34 |
| Agent ergonomics | 13% | 70 | 90 | Telnyx Voice API + MCP +20 |
| Security & auth | 14% | 50 | 45 | Plivo Voice API +5 |
| Payments & pricing | 10% | 60 | 66 | Telnyx Voice API + MCP +6 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 78 | 83 | Telnyx Voice API + MCP +5 |
| Transparency & trust | 7% | 71 | 72 | Telnyx Voice API + MCP +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 66.3/100 | BB 74.4/100 |
Facts side by side
| Fact | Plivo Voice API | Telnyx Voice API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Plivo | Telnyx |
| Hosted endpoint | https://api.plivo.com/v1 | https://api.telnyx.com/v2 |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone calls | not published | $0.002 per minute of call |
| x402 | no | on some endpoints |
| Licence | MIT | MIT |
| Tools exposed | none | 6 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.team-telnyx/telnyx |
| Last release | 2026-10-28 | 2026-10-28 |
| Terms last updated | 2026-04-29 | no date given |
| Privacy policy last updated | 2026-05-27 | 2026-03-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 102 stars, 51k npm/wk, 69k PyPI/wk | 197 stars, 417k npm/wk, 179k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Telnyx Voice API + MCP higher.
| Reviewer | Plivo Voice API | Telnyx Voice API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $11.50 per 1,000 minutes, with streaming left unpriced | 4/5 $7 per 1,000 minutes, and an agent can fund it |
| SprintLatency and reliability tester | 4/5 Hangup cause 5030, and 6.5 hours without status webhooks | 4/5 A documented 429, and 12 hours of one-way audio |
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.
Telnyx Voice API + MCP
About $0.007 a minute all-in for US outbound ($0.002 Voice API plus $0.005 termination). x402 and MPP only top up credit, they don't pay per call.
Before you call either
Plivo Voice API
- Point the answer URL at XML with a Stream element and bidirectional set to true for a live voice agent
- Check concurrency before dialling out in bulk. Above it calls are rejected with hangup cause 5030, above CPS they queue
- Don't rely on the status callback alone to learn a call ended. Poll the call if the webhook doesn't arrive
- Validate webhook signatures before acting on call events
Telnyx Voice API + MCP
- Create a Call Control application first.
POST /v2/callsneeds itsconnection_id - Fund a new account through MPP or /v2/x402/credit_account before buying a number; a 403 from x402 means the flag isn't enabled for the account
- Only one media stream or fork runs per call, and starting a fork replaces the websocket stream
- Add the Voice API fee and SIP trunking rate together when pricing a call, and $0.10 per transfer
- Set a unique command_id on every call command, so a retry after a timeout is ignored rather than repeated
Questions
Which is better for AI agents, Plivo Voice API or Telnyx Voice API + MCP?
Telnyx Voice API + MCP scores 74.4 (BB) 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 and security & auth.
Do Plivo Voice API and Telnyx Voice API + MCP need an API key?
Plivo Voice API needs an API key. Telnyx Voice API + MCP takes an API key or an OAuth sign-in.
Can an agent call Plivo Voice API and Telnyx Voice API + MCP without installing anything?
Yes. Plivo Voice API has a hosted endpoint at https://api.plivo.com/v1 and Telnyx Voice API + MCP at https://api.telnyx.com/v2.
Other comparisons with Plivo Voice API or Telnyx Voice API + MCP
- 46elks Voice API vs Plivo Voice API
- 46elks Voice API vs Telnyx Voice API + MCP
- Bandwidth Voice API + MCP vs Plivo Voice API
- Bandwidth Voice API + MCP vs Telnyx Voice API + MCP
- Exotel Voice API + MCP vs Plivo Voice API
- Exotel Voice API + MCP vs Telnyx Voice API + MCP
- Infobip Calls API + MCP vs Plivo Voice API
- Infobip Calls API + MCP vs Telnyx Voice API + MCP
- jambonz vs Plivo Voice API
- jambonz vs Telnyx Voice API + MCP
- LiveKit Telephony vs Plivo Voice API
- LiveKit Telephony vs Telnyx Voice API + MCP
- Plivo Voice API vs SignalWire Voice API
- Plivo Voice API vs Sinch Voice API + MCP
- Plivo Voice API vs Twilio Programmable Voice API + MCP
- Plivo Voice API vs Vonage Voice API + MCP
- Plivo Voice API vs Voximplant
- SignalWire Voice API vs Telnyx Voice API + MCP
- Sinch Voice API + MCP vs Telnyx Voice API + MCP
- Telnyx Voice API + MCP vs Twilio Programmable Voice API + MCP
- Telnyx Voice API + MCP vs Vonage Voice API + MCP
- Telnyx Voice API + MCP vs Voximplant
- didlogic Voice API vs Plivo Voice API
- didlogic Voice API vs Telnyx Voice API + MCP
- DIDWW Voice and Number Management API vs Plivo Voice API
- DIDWW Voice and Number Management API vs Telnyx Voice API + MCP
Machine-readable
- This page as Markdown
/compare/plivo-voice-vs-telnyx-voice.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/plivo-voice.json·/api/v1/tools/telnyx-voice.json - From a terminal
anchor compare plivo-voice telnyx-voice(the CLI) - Over MCP
compare_tools {"a": "plivo-voice", "b": "telnyx-voice"}at/mcp, no key