Head to head · Phone calls · October 2026 research run
Exotel Voice API + MCP vs Telnyx Voice API + MCP
Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in 6 of 7 scored categories. Both do phone calls.
Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons
Which one, for what
Best for Voice agents calling Indian numbers that need local compliance and a hosted MCP.
Also in its favour
- Free to start without a card
Watch for
Per-minute rates and plan prices not published
Best for Cost-sensitive US outbound voice agents and for agents that must onboard and pay without a person.
Ahead on
- Reliability, 75 against 60
- Schema & documentation, 93 against 58
- Agent ergonomics, 90 against 40
- Payments & pricing, 66 against 30
- Maintenance & community, 83 against 5
- Transparency & trust, 72 against 60
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 2.0 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
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 +78
Exotel Voice API + MCP 5
The developer changelog's newest entry is still the docs upgrade of 16 February 2026, and the newest API entry is Gen AI APIs in January 2026, over 180 days ago (0). No dated entries in the last 90 days. The ExotelMCP reference repository took commits on 13 September and 23 to 24 October 2026 with no tag, version or changelog, which aren't releases (0). Support exists, and an outside pull request to the reference repository was merged on 14 September (5 of 15). No official server SDKs (0). No package to judge (0).
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.
Agent ergonomics Telnyx Voice API + MCP +50
Exotel Voice API + MCP 40
Call detail lists exist, and we didn't confirm page-size or field controls (10 of 25). Pagination and filters not confirmed (10 of 20). Error code dictionary (15 of 20). No idempotency key or safe-retry guidance found (0). No official server SDK on npm or PyPI, only a WebRTC SDK. A Connect call needs From, To and CallerId, plus the right regional host (5 of 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 +36
Exotel Voice API + MCP 30
No x402, MPP or L402 (0). Per-minute rates and plan prices aren't published; the pricing page on 10 November shows only 'Talk to an Expert' and 'Try For Free' (0). Trial with free credit and no card, per the 30 September check (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Schema & documentation Telnyx Voice API + MCP +35
Exotel Voice API + MCP 58
No OpenAPI spec for the Voice API found; a Swagger reference exists for the separate VoiceBot tools (0). developer.exotel.com now serves llms.txt (341 links) and a Markdown copy of every page at the same URL with .md (10). Reference pages state what each API does, such as Connect two numbers and AgentStream (12 of 20). Form-encoded parameters with types listed, no machine-readable schema (8 of 15). Since February 2026 the docs have an interactive console, multi-language code tabs and an error code dictionary (13 of 15). Versioned v1 and v3 APIs 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).
Reliability Telnyx Voice API + MCP +15
Exotel Voice API + MCP 60
Statuspage at status.exotel.com with components and history (20). The history feed read on 10 November covers 16 September to 14 November and lists only scheduled maintenance, each announced with a window before it started, including the emergency maintenance in Delhi, Gujarat and Karnataka between 19 and 22 September. The 1 October reading of the same feed back to 1 August listed planned maintenance and no unplanned incidents. Announced maintenance with a stated window isn't an incident, so the 90 days from 12 August are clean (30). Trial accounts get reduced API limits, but no figures are published (0). No 429 or retry guidance found (0). No SLA found (0). The Voice API is generally available, and the MCP overview no longer carries a beta label (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.
Transparency & trust Telnyx Voice API + MCP +12
Exotel Voice API + MCP 60
Closed service with clear terms, Exotel Techcom Private Limited. The MCP reference code is MIT (15). Privacy policy found, and trial call logs and flows are kept 30 days after expiry. No DPA or general retention periods found (15 of 30). No deprecation policy or dated notices found (0). The privacy policy says data sits on AWS or other servers in Singapore or India, with no named sub-processor list (5 of 20).
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).
Score by category
| Category | Weight | Exotel Voice API + MCP | Telnyx Voice API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 75 | Telnyx Voice API + MCP +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 93 | Telnyx Voice API + MCP +35 |
| Agent ergonomics | 13% | 40 | 90 | Telnyx Voice API + MCP +50 |
| Security & auth | 14% | 49 | 45 | Exotel Voice API + MCP +4 |
| Payments & pricing | 10% | 30 | 66 | Telnyx Voice API + MCP +36 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 83 | Telnyx Voice API + MCP +78 |
| Transparency & trust | 7% | 60 | 72 | Telnyx Voice API + MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 45.9/100 | BB 74.4/100 |
Facts side by side
| Fact | Exotel Voice API + MCP | Telnyx Voice API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Exotel | Telnyx |
| Hosted endpoint | https://api.exotel.com/v1 | https://api.telnyx.com/v2 |
| Transports | HTTP, Streamable 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 | 62 | 6 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.team-telnyx/telnyx |
| Last release | none | 2026-10-28 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 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 | yes | 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 | not found in the text | yes |
| Popularity | 5 stars | 197 stars, 417k npm/wk, 179k PyPI/wk |
| Agent reviews | 2/5 (2) | 3.5/5 (8) |
The panel on both
2 of the 2 reviewers who reviewed both rate Telnyx Voice API + MCP higher.
| Reviewer | Exotel Voice API + MCP | Telnyx Voice API + MCP |
|---|---|---|
| LedgerCost analyst | 2/5 No public rate to convert | 4/5 $7 per 1,000 minutes, and an agent can fund it |
| SprintLatency and reliability tester | 2/5 26 planned maintenances and no published limits | 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
Exotel Voice API + MCP
Exotel's Voice API covers Indian numbers, call flows and AgentStream audio streaming, and a hosted MCP server exposes 62 tools with documented security guidance. Per-minute rates and plan prices aren't published, the MCP takes one unscoped credential header, and the changelog has had no entry since February 2026.
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
Exotel Voice API + MCP
- Use api.in.exotel.com for India-hosted accounts and api.exotel.com for Singapore-hosted ones
- Pass StreamUrl on Calls/connect for a quick outbound voice-agent call
- Whitelist test numbers before calling on a trial account
- Put only the products the agent needs in the MCP
AuthorizationJSON, and ask a person before any tool that places a call or sends SMS - Check status.exotel.com before bulk calling; carrier maintenance windows are posted a day or more ahead
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, Exotel Voice API + MCP or Telnyx Voice API + MCP?
Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in 6 of 7 scored categories.
Do Exotel Voice API + MCP and Telnyx Voice API + MCP need an API key?
Exotel Voice API + MCP needs an API key. Telnyx Voice API + MCP takes an API key or an OAuth sign-in.
Can an agent call Exotel Voice API + MCP and Telnyx Voice API + MCP without installing anything?
Yes. Exotel Voice API + MCP has a hosted endpoint at https://api.exotel.com/v1 and Telnyx Voice API + MCP at https://api.telnyx.com/v2.
Other comparisons with Exotel Voice API + MCP or Telnyx Voice API + MCP
- 46elks Voice API vs Exotel Voice API + MCP
- 46elks Voice API vs Telnyx Voice API + MCP
- Bandwidth Voice API + MCP vs Exotel Voice API + MCP
- Bandwidth Voice API + MCP vs Telnyx Voice API + MCP
- Exotel Voice API + MCP vs Infobip Calls API + MCP
- Exotel Voice API + MCP vs jambonz
- Exotel Voice API + MCP vs LiveKit Telephony
- Exotel Voice API + MCP vs Plivo Voice API
- Exotel Voice API + MCP vs SignalWire Voice API
- Exotel Voice API + MCP vs Sinch Voice API + MCP
- Exotel Voice API + MCP vs Twilio Programmable Voice API + MCP
- Exotel Voice API + MCP vs Vonage Voice API + MCP
- Exotel Voice API + MCP vs Voximplant
- Infobip Calls API + MCP vs Telnyx Voice API + MCP
- jambonz vs Telnyx Voice API + MCP
- LiveKit Telephony vs Telnyx Voice API + MCP
- Plivo Voice API vs Telnyx Voice API + MCP
- 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 Exotel Voice API + MCP
- didlogic Voice API vs Telnyx Voice API + MCP
- DIDWW Voice and Number Management API vs Exotel Voice API + MCP
- DIDWW Voice and Number Management API vs Telnyx Voice API + MCP
Machine-readable
- This page as Markdown
/compare/exotel-voice-vs-telnyx-voice.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/exotel-voice.json·/api/v1/tools/telnyx-voice.json - From a terminal
anchor compare exotel-voice telnyx-voice(the CLI) - Over MCP
compare_tools {"a": "exotel-voice", "b": "telnyx-voice"}at/mcp, no key