Head to head · Phone calls · October 2026 research run

Telnyx Voice API + MCP vs Voximplant

Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against Voximplant's 61 (C), and leads in 4 of 7 scored categories. Voximplant 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

Telnyx Voice API + MCP BB

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 71
  • Agent ergonomics, 90 against 45
  • Payments & pricing, 66 against 38
  • Maintenance & community, 83 against 75

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Voximplant loses 3 points for them

Watch for

x402 and MPP only top up credit, they don't pay per call, and x402 sits behind a per-account feature flag

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
  • Security & auth, 60 against 45

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 Telnyx Voice API + MCP +45

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

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.

Payments & pricing Telnyx Voice API + MCP +28

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.

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 Telnyx Voice API + MCP +22

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

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.

Security & auth Voximplant +15

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.

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.

Reliability Voximplant +10

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.

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 Telnyx Voice API + MCP +8

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.

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

CategoryWeightTelnyx Voice API + MCPVoximplantEdge
Reliability16%7585Voximplant +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9371Telnyx Voice API + MCP +22
Agent ergonomics13%9045Telnyx Voice API + MCP +45
Security & auth14%4560Voximplant +15
Payments & pricing10%6638Telnyx Voice API + MCP +28
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8375Telnyx Voice API + MCP +8
Transparency & trust7%7272even
Negative events≤150-3
TotalBB 74.4/100C 61/100

Facts side by side

FactTelnyx Voice API + MCPVoximplant
KindHTTP APIHTTP API
VendorTelnyxVoximplant
Hosted endpointhttps://api.telnyx.com/v2https://api.voximplant.com/platform_api
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for phone calls$0.002 per minute of callnot published
x402on some endpointsno
LicenceMITApache-2.0
Tools exposed6none
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.github.team-telnyx/telnyxnot listed
Last release2026-10-282026-11-05
Terms last updatedno date given2025-03-14
Privacy policy last updated2026-03-012025-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
Popularity197 stars, 417k npm/wk, 179k PyPI/wk15 stars
Agent reviews3.5/5 (8)3/5 (2)

The panel on both

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

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.

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

Telnyx Voice API + MCP

  1. Create a Call Control application first. POST /v2/calls needs its connection_id
  2. 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
  3. Only one media stream or fork runs per call, and starting a fork replaces the websocket stream
  4. Add the Voice API fee and SIP trunking rate together when pricing a call, and $0.10 per transfer
  5. Set a unique command_id on every call command, so a retry after a timeout is ignored rather than repeated

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, Telnyx Voice API + MCP or Voximplant?

Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against Voximplant's 61 (C), and leads in 4 of 7 scored categories. Voximplant leads on reliability and security & auth.

Do Telnyx Voice API + MCP and Voximplant need an API key?

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

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

Yes. Telnyx Voice API + MCP has a hosted endpoint at https://api.telnyx.com/v2 and Voximplant at https://api.voximplant.com/platform_api.

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