TL;DR
- Twilio is the practical default when the team already uses its call-control and messaging ecosystem. US local voice is $0.014/minute outbound and $0.0085 inbound; SMS is $0.0083/segment before carrier fees.
- Telnyx is the stronger price-led shortlist choice for an engineer-owned US workload. Its Voice API rate is $0.002/minute plus SIP transport, and local SMS starts at $0.004/part plus carrier fees.
- Vonage fits teams already using NCCO call flows or its wider communications APIs. Use its country/account rate basis; a competitor's comparison price is not a reliable substitute for your configured Vonage rate.
- Count numbers, call legs, SMS parts, media streaming and registration separately. None of these APIs' ordinary phone rates buys a complete conversational agent by itself.
What these APIs supply
A phone-and-SMS API lets software provision a number, place or receive a call, send a message and collect events about what happened. Your application decides whom to contact, what to say and what the result means. A speech service and model turn the audio into an agent conversation; call-control and messaging APIs are the communication layer beneath it.
That distinction matters commercially. A low phone-minute rate does not include every speech, model, storage or integration service. Nor does a successful API response mean the recipient received the message or the application completed the task.
This shortlist compares Twilio, Telnyx and Vonage, retaining the original scope. It is for buyers whose developers own the communication workflow, rather than a sales manager seeking a finished dialer or a no-code receptionist. For a phone-and-email identity bundle, the buying object is different again.
The three choices
1. Twilio: best default for an existing Twilio application
Twilio's programmable voice provides call control and Media Streams for bringing audio into your application's voice stack. Bidirectional streaming lets that application send audio back into the call. ConversationRelay is a separate option that handles speech conversion while your application supplies conversational logic. Media Streams, ConversationRelay.
For an agent buyer, this provides a clear architecture: retain the call ID, connect the voice application, process the outcome and use messaging for the agreed follow-up. The infrastructure does not determine CRM matching or whether a booking action succeeded; those remain application responsibilities.
US local voice is $0.014/minute outbound and $0.0085 inbound, with a local number at $1.15/month. Media Streams is currently $0.0044/minute. Recording is $0.0025/minute and the first storage tier $0.0005 per stored minute/month. US voice rates.
Local SMS is $0.0083/segment in either direction, plus carrier fees. The unit is the transmitted segment, not the complete text a user sees on their phone. US SMS rates.
Choose Twilio when existing code, integrations or operational knowledge make it easier to run. It is less compelling if the only requirement is the lowest published US transport component and a new team can implement either provider equally well. A modest usage-price premium can still be worthwhile when it avoids a migration or reduces engineering work.
2. Telnyx: best price-led option for a composed voice stack
Telnyx supplies programmable call control, media streaming and messaging as separately priced primitives. Its streaming interface supports bringing call audio to your application, so it is suitable for an agent whose model and speech stack your engineers operate. Media streaming.
The important voice-price detail is $0.002/minute for the API plus the SIP rate. Its public US example uses $0.005 outbound transport and $0.0032 inbound transport, giving $0.007 outbound and $0.0052 inbound combined bases. It also lists Media Streaming at $0.0035/minute, recording at $0.002/minute and recording storage at zero. A call transfer invocation is separately priced at $0.10. Voice API pricing.
Local numbers start at $1/month, with another $0.10/month to add SMS/MMS capability. The relevant starting number component for this guide's two-channel workflow is therefore $1.10. Country and number type can change the purchase. Number pricing.
Local SMS starts at $0.004/part plus the carrier charge. The current commercial page's carrier table is the basis here; older support examples contain different carrier figures. Messaging pricing.
Choose Telnyx for a new engineer-owned workload where the composition and lower listed US transport components fit. It is not a $0.002 all-in voice-agent service, and an application using streaming, transfers, recording or speech needs to budget the selected primitives. The small number saving is not a reason by itself to rewrite a functioning Twilio application.
3. Vonage: best for an existing NCCO and communications stack
Vonage's Voice API uses NCCO actions to control calls: connect a destination, collect input, play speech or audio, record and track events. A WebSocket endpoint can carry live audio to and from a voice application. That makes it a genuine agent infrastructure option rather than a human-phone-only product. NCCO reference.
Its Numbers API supports searching, buying and configuring number inventory. Numbers are a country- and capability-specific purchase; the developer should select a line that supports the required incoming calls and messages rather than assume every number supplies both. Numbers API.
Vonage publishes pay-per-use voice pricing with per-second billing and country/account-based rate presentation. Its SMS pricing page likewise uses country selection and points to customer-specific rates. The current public pages do not establish a complete fixed US total for the exact configuration used below, so this comparison uses a pricing formula rather than importing a dollar rate from another provider's marketing table. Voice price basis, SMS price basis.
Choose Vonage when its call-flow model, existing application or wider channel agreements fit your organisation. That is a sufficient practical reason to shortlist it without inventing a universal lowest-price claim. It is a weaker starting point for a buyer whose only decision criterion is an immediately reproducible public US bill; Twilio and Telnyx make that comparison more direct.
Comparable US buying units
Public US-dollar bases checked on 30 September 2026:
| Unit | Twilio | Telnyx | Vonage |
|---|---|---|---|
| Ordinary local number | $1.15/month | From $1/month; SMS capability adds $0.10 | Country/type/account basis |
| Outbound US call minute | $0.014 | $0.002 API + $0.005 example transport = $0.007 | Destination/account rate; per-second voice billing |
| Inbound US local minute | $0.0085 | $0.002 API + $0.0032 example transport = $0.0052 | Number/account rate |
| US local SMS base | $0.0083/segment | $0.004/part | Country/account messaging rate |
| Carrier message charges | Additional, destination and direction dependent | Additional, destination and direction dependent | Pass-through fees in addition to usage |
| Chosen voice integration | Media Streams $0.0044/minute | Media Streaming $0.0035/minute | WebSocket call endpoint; price from selected configuration |
The Telnyx transport example is a supported US basis, not a claim that every international destination uses the same rate. Vonage's formula remains useful because the workflow and billable quantities are known even when the exact account rate is not.
Registration and number identity
For US application SMS over local long-code numbers, the providers document a brand and campaign registration process. The sender is the business using the messaging programme, not the language model. Number provisioning and an approved messaging route are separate steps.
Twilio's Low Volume Standard brand registration is $4.50, campaign vetting $15 and a qualifying Low Volume Mixed campaign $1.50/month. The campaign choice should reflect the actual use case; larger standard campaigns have a different basis. Twilio registration fees.
Telnyx lists the same $4.50 brand application and $15 campaign-review fees, with $1.50/month for Low Volume Mixed and $10/month for standard-volume campaigns. Its campaign fees are initially billed for three months, then monthly. That changes launch cash even when the monthly allocation matches. Telnyx registration fees.
Vonage lists $4.50 brand registration, $15 per campaign vetting event, and $1.50/month Low Volume Mixed or $10 for standard use cases. Standard brand vetting and other applicable verification can add costs. Vonage registration fees.
For a multi-client agent service, keep each client's sender identity and approved programme distinct. One cheap phone number is not a substitute for representing the actual sender. For a buyer, the practical implication is to include registration work in launch planning and to use a callback number that remains owned by the workflow.
A worked US workload
Assume one US local number used for opted-in transactional follow-up:
- 100 outbound calls of three minutes: 300 outbound minutes.
- Fifty inbound callbacks of two minutes: 100 inbound minutes.
- 1,000 outgoing texts: 800 one-part and 200 two-part, producing 1,200 outbound SMS parts.
- 200 incoming replies, each one part: 200 inbound SMS parts.
- All 400 call minutes use the selected media stream and recording; keep one month's recordings.
- A qualifying Low Volume Mixed campaign, with one successful initial review.
Assume outbound recipients are 50% AT&T, 25% T-Mobile and 25% Verizon. Current commercial tables give an outbound carrier-weighted rate of $0.004/part for this mix. For simplicity, the incoming replies are all from Verizon, with no carrier charge in the selected tables. These are declared workload assumptions, not a universal US carrier average.
| Monthly component | Twilio | Telnyx |
|---|---|---|
| Number with messaging capability | $1.15 | $1.10 |
| Outbound voice | 300 × $0.014 = $4.20 | 300 × $0.007 = $2.10 |
| Inbound voice | 100 × $0.0085 = $0.85 | 100 × $0.0052 = $0.52 |
| Outbound SMS including assumed carrier mix | 1,200 × ($0.0083 + $0.004) = $14.76 | 1,200 × ($0.004 + $0.004) = $9.60 |
| Inbound SMS | 200 × $0.0083 = $1.66 | 200 × $0.004 = $0.80 |
| Media stream | 400 × $0.0044 = $1.76 | 400 × $0.0035 = $1.40 |
| Recording | 400 × $0.0025 = $1 | 400 × $0.002 = $0.80 |
| One month's recording storage | 400 × $0.0005 = $0.20 | $0 published recording-storage charge |
| Campaign monthly allocation | $1.50 | $1.50 |
| Communication component total | $27.08 | $17.82 |
Sources for the selected units: Twilio voice, Twilio SMS, Telnyx voice, Telnyx SMS, Telnyx numbers.
Now add a deliberately assumed $0.06 per conversation minute for the external speech/model stack, or $24, and $10/month of application hosting. This is an editorial budget allowance, not a vendor bundle. The operating-component totals become $61.08 for Twilio and $51.82 for Telnyx, before taxes, implementation, transfer legs and any other selected services.
Launch registration adds $19.50 for one brand application and campaign review in this example. That brings the illustrated first-month Twilio components to $80.58. Telnyx's initial three-month campaign payment adds another $3 beyond the one month already counted, making its illustrated first-month components $74.32. Extra reviews or a different brand/campaign basis change that cash requirement.
For Vonage, use the same quantities:
number + 300 × outbound voice rate + 100 × inbound voice rate + 1,200 × outgoing SMS-and-carrier rate + 200 × incoming rate + configured streaming/recording/storage + campaign + external stack/hosting.
The formula prices the actual task using the selected account's rates. Its documented registration basis can be added once the brand type is chosen. Vonage's strongest buying case is the value of retaining a suitable existing application.
At this workload, Telnyx's illustrated monthly advantage is $9.26. At $75/hour of engineering time, that buys 7.41 minutes. An additional four-hour migration costing $300 would take about 32.4 months to recover from that usage difference alone. Ten times the same traffic mix makes the rate difference much more relevant, but number and campaign charges should not simply be multiplied if the design still uses one number and one campaign.
How countries and messages change the bill
An SMS is not always one billable unit. GSM-7 supports 160 characters in a single segment and 153 per concatenated segment. Unicode messaging can use 70 for a single segment or 67 per concatenated segment. A short emoji or typographic character can therefore change encoding and increase parts. SMS character and segment limits.
In the example, shortening the 200 two-part texts to one part saves 200 transmitted parts: $2.46 on the assumed Twilio route or $1.60 on Telnyx. The same message is still visible to the recipient as one conversation item, which is why counting application sends understates the bill.
Local numbers and destinations are different countries in the pricing model. A US number calling a UK mobile needs the applicable UK-mobile destination rate. It does not use the US outbound example merely because the sender owns a US number. An international number may also require a different capability or registration basis.
Handoffs can create additional legs. If fifty calls transfer for four further minutes, budget 200 destination-leg minutes and the chosen transfer mechanism. Telnyx's listed $0.10 invocation would add $5 for fifty invocations, before the additional leg costs. That is separate from the original AI conversation minutes.
Retries can increase both spend and annoyance. Preserve provider IDs and delivery/call status with the business task. A missing receipt is not by itself a reason to send another text or place another call. Keep incoming replies connected to the original request and allow the agent to stop when a human takes ownership.
Which API to buy
Choose Twilio for an existing application or a team whose experience with its call and messaging tools reduces implementation work. The rate premium in a small workflow is often less than a few minutes of engineering.
Choose Telnyx for a new composed stack where lower public US components matter and the team understands the separate API, SIP, streaming and optional-service lines. Its price case strengthens with sustained traffic.
Choose Vonage when the existing NCCO application, channel agreements or operational fit make it the easier system to run. Use country/account rates in the worked formula instead of adopting a competitor's quoted number.
Use the signal-based outbound playbook to tie calls and messages to an actual next step. The infrastructure choice should make a useful workflow easier to operate, rather than turn a small difference in message rates into a costly rewrite.
FAQ
Does Telnyx voice cost only $0.002/minute?
That is the Voice API component. SIP transport and selected services are additional.
Does Twilio's phone rate include the AI model?
No. The application needs the selected speech/model arrangement. Media Streams and ConversationRelay are distinct integration choices with their own price bases.
Why is no exact Vonage total shown?
The current public pages do not establish the configured account's complete rate set. The article gives its documented capabilities, registration basis and a quantity formula, which supports a practical existing-stack recommendation.
Why can 1,000 texts produce more than 1,000 charges?
Longer or differently encoded texts split into parts. In the example, 200 two-part texts make the 1,000 sends total 1,200 billable outbound parts.
Which is cheapest for this workload?
Telnyx has the lower illustrated component total. At this small volume, the difference is too small to justify a substantial migration purely on usage rates.
