Head to head · Phone calls · October 2026 research run
SignalWire Voice API vs Telnyx Voice API + MCP
Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against SignalWire Voice API's 69.4 (B), and leads in 5 of 7 scored categories. SignalWire Voice API leads on 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 Builders who want call logic in documents (SWML) or a hosted AI agent verb, and for teams moving off Twilio's API shape.
Ahead on
- Security & auth, 72 against 45
Watch for
Status page renders only with JavaScript, so its history isn't readable by agents
Best for Cost-sensitive US outbound voice agents and for agents that must onboard and pay without a person.
Ahead on
- Reliability, 75 against 53
- Schema & documentation, 93 against 87
- Agent ergonomics, 90 against 68
- Payments & pricing, 66 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- 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.
Security & auth SignalWire Voice API +27
SignalWire Voice API 72
Basic auth with a Project ID and an API token, or short-lived Bearer tokens. Tokens are scoped when created, with the Voice scope for calls, new tokens use a swapi_ format since September 2026, and since 8 October a REST endpoint regenerates a token's value in place and every token response carries last_used_at and revoked_at (30). Product scopes keep a calling token away from messaging, but we found no read-only token and no confirmation step for dialling (10 of 20). Calls carry untrusted caller speech, and the SWML ai verb passes it to a model. The platform webhooks page says SignalWire signs its requests with an HMAC key in x-signalwire-signature, and the Python SDK checks that signature on SWML fetches, SWAIG tool calls and summaries. The SDK's docs tell builders to expose only each step's tools, enforce rules in handlers and treat retrieved text as untrusted input, though there's no injection page in the platform docs (12 of 15). Voice logs can be listed by API. We didn't find an account audit log (10 of 15). A vulnerability disclosure policy, an ISO 27001 certificate and a SOC 2 Type 2 attestation letter are linked from signalwire.com/legal, re-read on 1 November. signalwire.com/.well-known/security.txt answers 404, no bug bounty found, and OSV lists no advisories for signalwire-sdk, signalwire or @signalwire/sdk. The same reading as the Telnyx voice listing (10 of 20).
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.
Reliability Telnyx Voice API + MCP +22
SignalWire Voice API 53
status.signalwire.com redirects to a PagerDuty-hosted page. Re-read on 1 November, its page data names ten services (APIs, SIP Connectivity, WebRTC Connectivity, Video and Conferencing, Website, External Carrier Network, SMS, MMS, AI, Support and Documentation) and says it was created on 23 December 2025, but incidents load only through the page's script and we found no feed, so component history isn't readable (10 of 20). No readable incident history (5). The 1 October note cited a third-party status aggregator for a 14 August degradation; that isn't a first-hand source and isn't used. Trial mode caps queued calls and messages at 10 each, and Space limits are raised on request. The error-codes page, re-read on 1 November, names a rate_limit_exceeded code but no general per-second figures (8 of 15). The error-codes page says to back off and retry on 429, and now also calls every 5xx "Safe to retry with backoff", which for a dial can place a second call. The official Python SDK honours Retry-After with exponential backoff and retries POSTs only on 429 or 503, never on other 5xx, so a dial isn't replayed. No idempotency key (10 of 15). The Service Level Agreement (updated 1 January 2026) commits to 99.95 per cent monthly uptime for SignalWire Cloud APIs on every account, with a 10 per cent credit claimed by ticket within 30 days, per the 2 October read (10). The Calling API is generally available (10). 10 + 5 + 8 + 10 + 10 + 10 = 53.
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.
Agent ergonomics Telnyx Voice API + MCP +22
SignalWire Voice API 68
A paging guide covers page sizes on list endpoints, with no field selection (15 of 25). Voice logs can be listed and paged. We didn't confirm the full filter set (15 of 20). An error-codes page with a structured errors array (type, code, message, attribute, url) an agent can map to fixes, and command results arrive on status webhooks (15 of 20). No idempotency key. The Python SDK's documented retry policy keeps POSTs from being replayed after a 5xx (8 of 20). One POST endpoint takes every command, a dial needs from, to and a SWML url, and there are official Python and Node SDKs plus Twilio-compatible ones (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).
Schema & documentation Telnyx Voice API + MCP +6
SignalWire Voice API 87
Public OpenAPI 3.1 spec at signalwire.com/docs/openapi.json and .yaml, which generates the REST reference (25). llms.txt, and every docs page as Markdown by adding .md or sending Accept: text/markdown (10). The call-commands reference states what each command does, dial, calling.transfer, calling.record, calling.stream, calling.tap and calling.refer, with little on when not to use one (12 of 20). Typed fields from the spec, with commands carried in a params object (12 of 15). Examples per command and an error-codes page (13 of 15). Platform changelog with dated entries and an RSS twin, the newest on 22 October 2026, including transport on dial requests on 19 October (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).
Payments & pricing Telnyx Voice API + MCP +6
SignalWire Voice API 60
No x402, MPP or L402 (0). US per-minute rates for calls, SIP, numbers, recording and the AI agent runtime published without a login, re-read on 1 November on signalwire.com/pricing (20). New accounts start in trial mode without a card, limited to 1 number and verified destinations, and a card with at least $5 of credit lifts it, re-read on 1 November. The trial page doesn't state a free credit amount (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): 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.
Score by category
| Category | Weight | SignalWire Voice API | Telnyx Voice API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 53 | 75 | Telnyx Voice API + MCP +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 93 | Telnyx Voice API + MCP +6 |
| Agent ergonomics | 13% | 68 | 90 | Telnyx Voice API + MCP +22 |
| Security & auth | 14% | 72 | 45 | SignalWire Voice API +27 |
| Payments & pricing | 10% | 60 | 66 | Telnyx Voice API + MCP +6 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 83 | Telnyx Voice API + MCP +2 |
| Transparency & trust | 7% | 74 | 72 | SignalWire Voice API +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.4/100 | BB 74.4/100 |
Facts side by side
| Fact | SignalWire Voice API | Telnyx Voice API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SignalWire | Telnyx |
| Hosted endpoint | no (local only) | 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-25 | 2026-10-28 |
| Terms last updated | not read yet | no date given |
| Privacy policy last updated | couldn't be read | 2026-03-01 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 8 stars, 1.5k npm/wk, 1.3k 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 | SignalWire Voice API | Telnyx Voice API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 3/5 An SLA and a 429 rule, and a status page agents can't read | 4/5 A documented 429, and 12 hours of one-way audio |
| LedgerCost analyst | 4/5 $8 per 1,000 minutes, $168 with the AI runtime | 4/5 $7 per 1,000 minutes, and an agent can fund it |
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
SignalWire Voice API
SWML documents, REST commands and a Relay WebSocket client for call control. Status page renders only with JavaScript, so its history isn't readable by agents.
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
SignalWire Voice API
- Send dial with a url pointing at a SWML document, then use calling.* commands on the returned call ID
- Don't retry a dial on a 5xx, whatever the error-codes page says. Retry only on 429 or 503, after Retry-After, or you may place the call twice
- Use your own Space subdomain as the host, there is no shared API host
- Create a token with only the Voice scope for a calling agent
- Verify
x-signalwire-signaturewith the Signing Key before acting on a webhook
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, SignalWire Voice API or Telnyx Voice API + MCP?
Telnyx Voice API + MCP scores 74.4 (BB) on agent readiness against SignalWire Voice API's 69.4 (B), and leads in 5 of 7 scored categories. SignalWire Voice API leads on security & auth.
Do SignalWire Voice API and Telnyx Voice API + MCP need an API key?
SignalWire Voice API needs an API key. Telnyx Voice API + MCP takes an API key or an OAuth sign-in.
Can an agent call SignalWire Voice API and Telnyx Voice API + MCP without installing anything?
No hosted endpoint is listed for SignalWire Voice API. Telnyx Voice API + MCP has a hosted endpoint at https://api.telnyx.com/v2.
Other comparisons with SignalWire Voice API or Telnyx Voice API + MCP
- 46elks Voice API vs SignalWire Voice API
- 46elks Voice API vs Telnyx Voice API + MCP
- Bandwidth Voice API + MCP vs SignalWire Voice API
- Bandwidth Voice API + MCP vs Telnyx Voice API + MCP
- Exotel Voice API + MCP vs SignalWire Voice API
- Exotel Voice API + MCP vs Telnyx Voice API + MCP
- Infobip Calls API + MCP vs SignalWire Voice API
- Infobip Calls API + MCP vs Telnyx Voice API + MCP
- jambonz vs SignalWire Voice API
- jambonz vs Telnyx Voice API + MCP
- LiveKit Telephony vs SignalWire Voice API
- LiveKit Telephony vs Telnyx Voice API + MCP
- Plivo Voice API vs SignalWire Voice API
- Plivo Voice API vs Telnyx Voice API + MCP
- SignalWire Voice API vs Sinch Voice API + MCP
- SignalWire Voice API vs Twilio Programmable Voice API + MCP
- SignalWire Voice API vs Vonage Voice API + MCP
- SignalWire Voice API vs Voximplant
- 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 SignalWire Voice API
- didlogic Voice API vs Telnyx Voice API + MCP
- DIDWW Voice and Number Management API vs SignalWire Voice API
- DIDWW Voice and Number Management API vs Telnyx Voice API + MCP
Machine-readable
- This page as Markdown
/compare/signalwire-voice-vs-telnyx-voice.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/signalwire-voice.json·/api/v1/tools/telnyx-voice.json - From a terminal
anchor compare signalwire-voice telnyx-voice(the CLI) - Over MCP
compare_tools {"a": "signalwire-voice", "b": "telnyx-voice"}at/mcp, no key