Head to head · Phone calls · October 2026 research run

Twilio Programmable Voice API + MCP vs Voximplant

Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against Voximplant's 61 (C), and leads in 6 of 7 scored categories. Voximplant 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

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 71
  • Agent ergonomics, 80 against 45
  • Security & auth, 85 against 60
  • Payments & pricing, 60 against 38
  • Maintenance & community, 85 against 75
  • Transparency & trust, 81 against 72

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Voximplant loses 3 points for them

Watch for

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

Voximplant C

Best for Teams that want speech-to-speech models on the phone without running a media server, and are happy to write call logic in VoxEngine JavaScript.

Ahead on

  • Reliability, 85 against 75

Watch for

Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks)

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.

Agent ergonomics Twilio Programmable Voice API + MCP +35

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

Voximplant 45

List methods such as call history take count and offset, and we didn't confirm field controls (10 of 25). Filters not confirmed (10 of 20). The error catalogue names every code with a message, though errors arrive with HTTP 200 and an error object (15 of 20). No idempotency key or safe-retry guidance found (0). Official clients in Node.js, Python, PHP, Java, Go and .NET, but a first call needs an uploaded VoxEngine scenario and a rule before StartScenarios (10 of 15). 10 + 10 + 15 + 0 + 10 = 45.

Security & auth Twilio Programmable Voice API + MCP +25

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

Voximplant 60

Service accounts sign RS256 JWTs that live up to 1 hour, and each service account gets one or more roles. That earns 30, less 10 because the basics page, per the 30 September check, documents an account ID and API key in the query string as an option (20). Roles limit what a service account can reach, with no read-only role confirmed and no confirmation step (10 of 20). Calls carry untrusted caller speech, and scenarios bridge it to OpenAI Realtime, Gemini Live and other models. No prompt-injection guidance found (0 of 15). GetAuditLog and call history are documented Management API methods (15 of 15). A valid security.txt (Expires 21 October 2027) points to a reasonable disclosure policy and a bug bounty policy that pays rewards set per report, and the site states ISO/IEC 27001:2022 certification with a linked certificate we didn't open. No SOC 2 and no advisories handled in public found. Level with twilio-voice's 15 (a disclosure programme, a bounty, ISO 27001) and below infobip-calls' 17, which adds SOC 2 Type 2 (15 of 20). 20 + 10 + 0 + 15 + 15 = 60.

Payments & pricing Twilio Programmable Voice API + MCP +22

Twilio Programmable Voice API + MCP 60

No x402, MPP or L402 on the pricing page or the docs MCP page (0). US per-minute rates for calls, numbers, Media Streams, ConversationRelay, recording and SIP published without a login, re-read on 1 November (20). Free trial without a card, with free units including 75 voice minutes for 30 days, per the trial doc modified 25 September 2026. The US voice pricing page still describes the trial as $15 of credit to buy a phone number and try Voice (20). A person has to sign up in a browser and verify 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.

Voximplant 38

Per the 1 October check, not re-read on 11 November. No x402, MPP or L402 (0). Per-country per-minute rates, number fees, streaming and connector prices published without a login (20). Signup for a developer account is free, but the pricing page states no trial credit or card policy (5 of 20). A person signs up in a browser (0). 0 + 20 + 5 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Schema & documentation Twilio Programmable Voice API + MCP +21

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

Voximplant 71

The docs' llms.txt, read on 11 November, links the Management API's OpenAPI 3.1 file at docs.voximplant.ai/openapi.json and openapi.yaml under "OpenAPI Specification". The file itself is per the 1 October reading, not re-read on 11 November (25). llms.txt with Markdown copies of every page (10). Reference pages describe each Management API method and VoxEngine class, with little on when not to use one (12 of 20). Method pages give each parameter's type, whether it's required, and example values (12 of 15). An error catalogue with every code the API returns, and request examples in several languages on each method page (12 of 15). No public changelog found and no version in the API path (0 of 15). 25 + 10 + 12 + 12 + 12 + 0 = 71.

Reliability Voximplant +10

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.

Voximplant 85

Statuspage at status.voximplant.com with components and history (20). The history feed, read on 11 November, runs from 20 October. Every Platform incident in it is scoped to one region or carrier (Russia PSTN on 20 and 29 October and 5 and 9 November, US SIP for 43 minutes on 21 October, Kazakhstan PSTN on 22 October, Europe PSTN and SIP on 29 October), and Kit, website and announced maintenance entries are left out. The 13 August to 19 October part of the window wasn't re-read, so the line keeps its recorded minor-only award (20). Per the 30 September check, not re-read on 11 November, limits published with numbers, 50 call attempts, 10 unanswered calls and 3 active HTTP requests per session, 1,000 users per account (15). The StartScenarios method page says the method returns 429 Too Many Requests past 200 concurrent HTTP requests until the number of active requests is reduced, and the Management API error catalogue lists RATE_LIMIT_EXCEED (340) and RETRY_LATER (416, "Repeat after N seconds", a stated wait). No idempotency keys or safe-retry guidance found (10, the value backoff or a stated wait takes). A Service Level Agreement, effective 15 September 2023, sets 99.95% uptime with service credits (10). The platform is generally available (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Maintenance & community Twilio Programmable Voice API + MCP +10

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

Voximplant 75

The Node.js client 5.2.0 and the Python client 2.13.0 were released on 5 November 2026, 6 days before 11 November (30). Since 13 August the Node.js client released 4.11.0 (26 August), 5.0.0 (7 October), 5.1.0 (26 October) and 5.2.0, and the Python client 2.10.0 (26 August), 2.11.0 (22 October), 2.12.0 (26 October) and 2.13.0, five release dates in all (20). No public changelog, and support exists (5 of 15). Official clients for the Management API in six languages, the Node.js and Python ones current (15). Package health not checked beyond the release tags (5 of 10, the earlier partial kept). 30 + 20 + 5 + 15 + 5 = 75.

Score by category

CategoryWeightTwilio Programmable Voice API + MCPVoximplantEdge
Reliability16%7585Voximplant +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9271Twilio Programmable Voice API + MCP +21
Agent ergonomics13%8045Twilio Programmable Voice API + MCP +35
Security & auth14%8560Twilio Programmable Voice API + MCP +25
Payments & pricing10%6038Twilio Programmable Voice API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8575Twilio Programmable Voice API + MCP +10
Transparency & trust7%8172Twilio Programmable Voice API + MCP +9
Negative events≤150-3
TotalA 79.9/100C 61/100

Facts side by side

FactTwilio Programmable Voice API + MCPVoximplant
KindHTTP APIHTTP API
VendorTwilioVoximplant
Hosted endpointhttps://api.twilio.com/2010-04-01https://api.voximplant.com/platform_api
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for phone calls$0.0025 per minute of callnot published
x402nono
LicenceMITApache-2.0
Tools exposed2none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-122026-11-05
Terms last updated2026-07-162025-03-14
Privacy policy last updated2026-04-092025-06-01
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 textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularity111 stars, 7.2M npm/wk, 4.8M PyPI/wk15 stars
Agent reviews3.1/5 (8)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate 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

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.

Voximplant

Voximplant runs call logic in VoxEngine JavaScript next to the media, with connectors for the main speech-to-speech models at $0.004 a minute and a published 99.95% uptime SLA. The Management API documents query-string keys as an option, there's no public changelog, and the Python client's 2.11.0 minor release reordered positional parameters without notice.

Before you call either

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

Voximplant

  1. Upload a VoxEngine scenario and a rule first, then start it with StartScenarios and pass the number in script_custom_data
  2. Pass arguments to the Python client by keyword, since 2.11.0 reordered positional parameters
  3. Use a service-account JWT rather than api_key in the URL
  4. Give the service account only the roles the agent needs, such as Scenarios
  5. Check the error object in every HTTP 200 response, since Management API errors don't use HTTP status codes

Questions

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

Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against Voximplant's 61 (C), and leads in 6 of 7 scored categories. Voximplant leads on reliability.

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

Both take an API key or an OAuth sign-in.

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

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

Other comparisons with Twilio Programmable Voice API + MCP or Voximplant

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.