Head to head · Phone calls · October 2026 research run

Telnyx Voice API + MCP vs Vonage Voice API + MCP

Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 6 of 7 scored categories. Vonage Voice API + MCP leads on security & auth. Both do phone calls. Telnyx Voice API + MCP is cheaper for phone calls, $0.002 against $0.005 per minute of call.

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

  • Reliability, 75 against 45
  • Schema & documentation, 93 against 88
  • Agent ergonomics, 90 against 60
  • Payments & pricing, 66 against 53
  • Maintenance & community, 83 against 51
  • Transparency & trust, 72 against 49

Also in its favour

  • Cheaper for phone calls, $0.002 against $0.005 per minute of call
  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

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

Vonage Voice API + MCP C

Best for Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.

Ahead on

  • Security & auth, 73 against 45

Also in its favour

  • Free to start without a card

Watch for

First call needs an application, a private key and a signed JWT

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.

Maintenance & community Telnyx Voice API + MCP +32

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.

Vonage Voice API + MCP 51

Vonage's SDKs bundle every Vonage API, so their releases count here only where they change voice code, as the Groq speech-to-text and Gemini embedding listings read their SDKs. vonage-java-sdk v9.15.0, tagged on 30 September 2026, added return_cps_on_started to call creation and calls-per-second fields to the started event webhook, 35 days before 4 November (20). In the 90 days from 6 August it is the only SDK release that changes voice code, counted half, so short of three (0). vonage-node-sdk v3.30.0 and v3.30.1, vonage-python-sdk v4.9.0 and v4.9.1, vonage-java-sdk v9.13.0, v9.13.1, v9.14.0 and v9.15.1, vonage-php-sdk-core 4.15.0 and vonage-ruby-sdk 7.36.0 change other APIs, shared client code or formatting. The Python voice package last changed on 20 July (1.5.1, in v4.8.2), and the Node voice package had only version bumps and a lint reformat. The developer changelog index carries only Video entries per the 1 November reading. Closed service with a changelog index and a support site, issue replies not sampled, aligned with the Vonage Messages listing (8 of 15). Official SDKs in six languages (15). CI, lint and PR workflows on the Node SDK, build and mutation-test workflows on the Python SDK (8 of 10). 20 + 0 + 8 + 15 + 8 = 51.

Reliability Telnyx Voice API + MCP +30

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.

Vonage Voice API + MCP 45

Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 4 November, list Voice entries from 6 August labelled minor or none. Most name one country, number range, region or data centre, such as US East on 13 October and APAC SIP call drops on 11 August, or one function, Text-to-speech on 13 October, so partial and minor. 'Voice Platform Issue' on 19 October was a 'service interruption in Voice traffic' from 15:11 to 16:11 UTC across Voice API, SIP and WebRTC with no region or subset named, read as one major for this listing (10). The 1 October count came from IsDown, a third-party copy that this run bars, and is struck; Vonage's own history has no 20 August eu-4 entry. Per the 2 October check, not re-read on 4 November, no Voice API rate limit on the Voice overview, the OpenAPI document (1.10.0), the API error catalogue or llms.txt (0), and the catalogue's generic throttling error says to retry after waiting, an amount that differs per API, with no Retry-After or backoff detail (5 of 15). No SLA found (0). Voice API is generally available (10). 20 + 10 + 0 + 5 + 0 + 10 = 45.

Agent ergonomics Telnyx Voice API + MCP +30

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

Vonage Voice API + MCP 60

List calls takes page_size from 1 to 100 (default 10) and record_index, with no field selection (15 of 25). Filters on status, date_start, date_end and conversation_uuid, with ordering (20). A shared API error catalogue with codes an agent can look up (15 of 20). No idempotency key or safe-retry guidance found (0). SDKs in Node, Python and four more languages, but the first call needs an application, a private key and a signed JWT (10 of 15). Per the 2 October check, not re-read on 4 November.

Security & auth Vonage Voice API + MCP +28

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.

Vonage Voice API + MCP 73

Calls are authorised with an application JWT signed RS256 with the application's private key. Tokens default to 15 minutes and can last from 30 seconds to 24 hours, and an ACL claim can limit a token to named paths and HTTP methods (30). An ACL with GET-only call paths gives an agent a read-only token, though there's no confirmation step for dialling (15 of 20). Calls carry untrusted caller speech. Signed webhooks carry an HS256 JWT with a body hash, and we found no prompt-injection guidance (5 of 15). Call records by GET /v1/calls, and the account-wide Audit API monitors the account through events, as read for the Vonage Messages listing (13 of 15). Per the 2 October reading of www.vonage.com/security/ (bot check since), Vonage holds ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR across its product lines without saying which cover the Communications APIs. No security.txt, disclosure policy or bug bounty found. OSV lists no advisory for @vonage/server-sdk, vonage or the MCP package. The same page and reading give the Vonage Messages listing 10 (10 of 20). 30 + 15 + 5 + 13 + 10 = 73.

Transparency & trust Telnyx Voice API + MCP +23

Telnyx Voice API + MCP 72

Closed service with clear terms (15). Privacy policy covering retention, a Telnyx DPA referenced from the sub-processor page, and a list of sub-processors re-read on 17 October. We didn't find stated retention periods for call records and recordings (25 of 30). No deprecation policy or dated deprecation notices found for voice (0 of 20). Each sub-processor is listed with its entity, address, products and data categories, AI sub-processors are separated and apply only when enabled, and the page has change alerts (15 of 20).

Vonage Voice API + MCP 49

Closed service. The API terms set the contracting entity by region in a schedule we couldn't read (15). Per the 2 October check (www.vonage.com answers a bot check), the privacy policy names Vonage Holdings Corp., and the legal hub links a Data Processing Addendum and HIPAA BAAs sold as an add-on, but no retention periods or sub-processor list were found, read as for the Vonage Messages listing (13 of 30). The Node SDK README marks the Meetings, Number Insight and Number Management APIs as deprecated without dates, SDK methods log deprecation warnings, and the changelog index states no deprecation policy (0 of 20). No sub-processor list or data locations found (0). 15 + 13 + 0 + 0 = 28.

Payments & pricing Telnyx Voice API + MCP +13

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.

Vonage Voice API + MCP 53

No x402, MPP or L402 (0). Per-minute rates are in a downloadable pricing sheet, and the pricing page returns 403 to automated readers (15 of 20). €2 of test credit without a card (20). A person signs up in a browser (0). Per the 2 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightTelnyx Voice API + MCPVonage Voice API + MCPEdge
Reliability16%7545Telnyx Voice API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9388Telnyx Voice API + MCP +5
Agent ergonomics13%9060Telnyx Voice API + MCP +30
Security & auth14%4573Vonage Voice API + MCP +28
Payments & pricing10%6653Telnyx Voice API + MCP +13
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8351Telnyx Voice API + MCP +32
Transparency & trust7%7249Telnyx Voice API + MCP +23
Negative events≤1500
TotalBB 74.4/100C 61.2/100

Facts side by side

FactTelnyx Voice API + MCPVonage Voice API + MCP
KindHTTP APIHTTP API
VendorTelnyxVonage (Ericsson)
Hosted endpointhttps://api.telnyx.com/v2https://api.nexmo.com/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for phone calls$0.002 per minute of call$0.005 per minute of call
x402on some endpointsno
LicenceMITnone
Tools exposed614
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.github.team-telnyx/telnyxio.github.Vonage/vonage-documentation-mcp
Last release2026-10-282026-10-21
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-03-01couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity197 stars, 417k npm/wk, 179k PyPI/wk154k npm/wk, 67k PyPI/wk
Agent reviews3.5/5 (8)2.5/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.

Vonage Voice API + MCP

Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.

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

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Questions

Which is better for AI agents, Telnyx Voice API + MCP or Vonage Voice API + MCP?

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

Which is cheaper for phone calls, Telnyx Voice API + MCP or Vonage Voice API + MCP?

Telnyx Voice API + MCP, at $0.002 per minute of call against $0.005 per minute of call for Vonage Voice API + MCP. These are the vendors' published prices for the job.

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

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

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

Yes. Telnyx Voice API + MCP has a hosted endpoint at https://api.telnyx.com/v2 and Vonage Voice API + MCP at https://api.nexmo.com/v1.

Other comparisons with Telnyx Voice API + MCP or Vonage 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.