TL;DR
This covers programmable communications platforms, meaning APIs you build on. Rep facing dialers are a different purchase and do not belong in the same columns. Best for: teams giving an agent or an application its own numbers, calls and messages.
Twilio has the deepest product surface and the most published rates, including a Pricing API for account specific figures, and it handles A2P registration through Trust Hub. Best for: teams that want documented everything and are willing to pay list.
Telnyx is materially cheaper on the same primitives, publishes machine readable rate cards, owns its carrier network, and has no plans or per seat fees at all. Best for: cost sensitive builds and teams that want programmatic pricing data.
Vonage bills voice per second rather than per minute and charges Verify only on successful verification, which suits low volume, high value flows. Best for: verification heavy or bursty workloads.
Registration is the hidden project. US A2P 10DLC brand and campaign fees plus per message carrier surcharges apply on every provider, and campaign registration takes 3 to 7 business days, stretching to 10 to 15 in busy periods. Best for: anyone planning a launch date.
Contents
- What a programmable communications platform is for
- Numbers and inventory
- Voice and messaging costs compared
- SDK, MCP and agent integration
- A2P 10DLC and identity requirements
- Modelling real usage cost
- Side by side summary
- FAQ: phone and SMS APIs for AI agents
What a programmable communications platform is for
When an AI agent needs to place a call, receive a call, send a message or verify a phone number, it needs a communications platform underneath it. That platform provides the numbers, the media path, the message routing, the identity registration and the usage billing.
This is not a comparison of rep dialers. A business phone system gives a human a handset, an app and a CRM integration. A programmable platform gives your code an endpoint and a per minute rate. Putting a $25 phone seat next to a $0.007 per minute voice API in the same table implies a substitutability that does not exist.
Three things drive the decision. Unit economics, because at agent volumes small per minute differences compound. The registration and identity path, because in the United States you cannot send A2P messages without registering a brand and a campaign. And the developer surface, meaning whether you can get rates, provision numbers and observe usage programmatically rather than through a dashboard.
1. Twilio
Layer: the broadest programmable communications platform, with the most published detail
Best for: teams that want every rate documented, a mature ecosystem and compliance handled through a first party product.
Twilio's advantage is coverage and documentation depth. Numbers are available in more than 100 countries across local, national, toll free and short code inventory. Trust Hub handles A2P 10DLC, GDPR and know your customer requirements as a product rather than a support ticket. Twilio was positioned a Leader in the 2026 Gartner Magic Quadrant for CPaaS.
For agent builds, the two most useful facts are structural. Volume discounts apply automatically without negotiation, so a growing workload gets cheaper without a procurement cycle, and committed use discounts exist above that. And there is a Pricing API that returns real time account specific pricing, which means an agent or a cost model can query what a call will actually cost rather than assuming list.
Pricing: US local numbers are $1.15 per month and toll free $2.15 per month, billed at full price on provision with no proration, then on the provision day each month. Outbound voice to the US and Canada is $0.014 per minute, inbound on local numbers $0.0085 and inbound toll free $0.0220. Conversation Relay is $0.07 per minute. Branded calling is $0.12 per call and answering machine detection $0.0075 per call. Call recording is $0.0025 per minute with storage at $0.0005 per minute per month, tiering down to $0.00025 after 5 million minutes and $0.00015 above 15 million. Transcription is $0.0500 per minute standard, $0.024 batch and $0.027 streaming. Text to speech per 100 characters is $0.0008 standard, $0.0032 neural and $0.0130 generative. SMS starts at $0.0083 to send or receive plus per segment carrier fees, and WhatsApp from $0.005 per message. Conversations API is $0.05 per active user per month, free to 200 users then tiering to $0.0475 and $0.0450, plus media storage from $0.25 per GB per month. Verify starts at $0.05 per verification and Lookup at $0.01 per inbound caller identification request. TURN is $0.40 per GB in US East, US West and Europe, $0.60 in Asia and $0.80 in Oceania, with STUN free. Twilio for Salesforce is $15 per seat per month after a 30 day trial. Developer support plans are free, with paid tiers scaling to monthly spend.
Where it falls short: compare the exact destination, number type and optional services against the other providers. A competitor’s published rate comparison can become stale and may exclude charges that apply to your implementation. Check the current rate cards and the renewal terms of your own agreement.
Verdict: the safest choice and the priciest. Choose it for coverage, compliance tooling and documentation, and use the Pricing API to model rather than assuming the published US rates.
2. Telnyx
Layer: owner operated carrier network with pure pay as you go pricing
Best for: cost sensitive agent workloads and teams that want rate cards their code can read.
Telnyx's structural difference is ownership. The carrier, the network and the API are one company, with carrier licences in more than 30 countries and inbound reach into more than 130 countries and territories. That shows up in the rates.
There are no plans and no per seat fees. Pay as you go earns automatic tier discounts with no contract, and committed pricing from $500 per month gives discounted rates across everything with nothing gated behind the commitment, which is unusually clean. Machine readable rate cards are available at a public pricing endpoint, with a query parameter to scope to SMS, so a cost model can stay current without scraping a page.
For Telnyx, use the applicable voice or messaging route and include numbers and optional services. Compare the same destination mix with the other providers.
Where it falls short: the ecosystem around it is smaller. Twilio has more prebuilt integrations, more third party tutorials and a larger hiring pool of engineers who have shipped on it. Telnyx also publishes its own competitor comparison, which is a vendor document rather than an independent one, so verify its Twilio and Vonage figures against those vendors' own pages before quoting them internally.
Verdict: the best unit economics here by a wide margin, and the best programmatic pricing access. The default choice for a high volume agent workload where you have engineering capacity.
3. Vonage
Layer: communications APIs with per second billing and success based verification
Best for: verification heavy flows and bursty voice workloads where per second billing matters.
Vonage sits between the other two on price and has two billing mechanics worth choosing it for. Voice is billed per second rather than rounded to the minute, which materially helps workloads made of many short calls, exactly the shape an agent generates. And the Verify API charges only on successful verification, so failed attempts do not bill at the verification rate, though attempt level messaging and voice rates still apply.
The developer surface is solid. There is a Pricing API v2 covering outbound SMS and outbound voice using basic authentication, rate limited to one request per second. A Reports API consolidates record retrieval across SMS, Messages, Voice, Video, Verify and Identity Insights, with automated volume discounts applied without negotiation. Elastic SIP trunking removes pre provisioning.
Where it falls short: the published pricing is the most inconsistent of the three across regional pages and third party sources, which makes budgeting harder than it should be. It is also more expensive than Telnyx on messaging and voice, and the API Management service and support plans are priced separately, so the platform total is not just usage.
Verdict: the right pick when per second voice billing or success only verification billing changes your economics. Confirm rates on the regional page you will actually be billed against.
Numbers and inventory
Inventory breadth favours Twilio, with local, national, toll free and short code numbers in more than 100 countries. Telnyx holds carrier licences in more than 30 countries with inbound reach into more than 130. Vonage sells virtual numbers with published monthly rental.
On cost, Telnyx is cheapest at $1.00 per month for a US local number, dropping to $0.79 on volume tiers. Vonage is $1.03 to $1.05 depending on the regional page, and Twilio is $1.15 with toll free at $2.15.
One billing detail deserves attention if you provision numbers programmatically. Twilio bills numbers at full price on provision with no proration and then on the same day each month, so an agent that creates and releases numbers frequently pays a full month each time. Design provisioning to be deliberate rather than dynamic.
Voice and messaging costs compared
Two cautions. Those cross vendor comparisons come substantially from Telnyx's own published August 2026 list comparison, which is a vendor source and reads in Telnyx's favour by construction. The per vendor figures above are from each vendor's own pages where available. And in every case carrier fees sit on top of the messaging rate and are not the provider's revenue, so a headline rate is never the delivered cost.
The practical shape is that Telnyx is roughly half of Twilio on the core voice and messaging primitives, and Vonage sits closer to Twilio with different rounding behaviour. Whether that difference matters depends entirely on your volume, which is the next section.
SDK, MCP and agent integration
For agent builds the question is not just which endpoints exist but whether your automation can operate the platform.
All three publish REST APIs with SDKs. What separates them is programmatic access to pricing and reporting. Twilio's Pricing API returns real time account specific rates, which is the strongest version of this because it reflects your negotiated and volume adjusted position rather than list. Telnyx publishes machine readable rate cards at a public endpoint with product scoping, which is easier to consume and reflects list rather than your account. Vonage's Pricing API v2 covers outbound SMS and outbound voice with basic authentication and a one request per second limit, and its Reports API consolidates records across all products.
Telnyx also ships AI Voice Agents at $0.05 per minute all in, which is a packaged path if you would rather not assemble speech to text, an agent and text to speech yourself. Twilio's Conversation Relay at $0.07 per minute plays a similar role.
One rule for any agent that holds these credentials. A communications API key can spend money and can send messages under your brand's registered identity. Keep it in a vault, scope it as narrowly as the platform allows, and never place it in an agent's context window or in content the agent retrieves.
A2P 10DLC and identity requirements
This is the part that delays launches, and it applies regardless of provider.
In the United States, application to person messaging over long codes requires registration with The Campaign Registry. There are two fee categories: registration fees and per message carrier fees. Both are charged by the carriers and passed through, and registration fees apply the moment the brand and use case are registered. This applies only to US long code A2P traffic, not to short codes and not to toll free traffic to the US.
The process is three steps. Register the brand. Create and register the campaign with a compliant opt in mechanism. Assign phone numbers to the campaign.
On timelines, campaign registration typically takes 3 to 7 business days and stretches to 10 to 15 days in high volume periods, with total end to end setup running 1 to 4 weeks. Twilio launched a sole proprietor registration path in April 2023 and handles registration through Trust Hub under Products and Services. Telnyx documents non compliance fees as well as registration fees.
If you take one thing from this section: start registration before you start building, because the code will be finished before the campaign is approved.
Modelling real usage cost
A worked example. An agent handles 2,000 outbound calls a month averaging 90 seconds, plus 10,000 SMS, on one US local number.
Messaging at 10,000 parts: Twilio from $0.0083 is $83 plus carrier fees, Vonage from $0.0079 is $79 plus carrier fees, Telnyx from $0.004 is $40 plus carrier fees. Carrier surcharges at $0.003 to $0.005 add $30 to $50 on all three.
Number rental: $1.15, $1.00 or about $1.05.
Side by side summary
| Tool | Layer | Best for | Entry price |
|---|---|---|---|
| Twilio | Broadest CPaaS with first party compliance tooling | Documented rates, coverage in 100+ countries, Trust Hub | US outbound voice $0.014 per minute; SMS from $0.0083 plus carrier fees |
| Telnyx | Owner operated carrier network, pure pay as you go | Lowest unit costs and machine readable rate cards | Voice API from $0.002 per minute; messaging from $0.004 per part |
| Vonage | Communications APIs with per second voice billing | Verification heavy and short call workloads | Voice from $0.00798 per minute domestic US; SMS from $0.00860 |
FAQ: phone and SMS APIs for AI agents
Which is cheapest for a high volume agent?
Calculate the actual destination and traffic mix, including numbers, call minutes, messages and optional services. A headline unit rate cannot establish the cheapest total implementation.
Do I have to register before sending SMS in the US?
Yes, for application to person traffic over long codes. You register a brand and a campaign with The Campaign Registry and assign numbers to the campaign. It does not apply to short codes or to toll free traffic to the US. Expect 3 to 7 business days for campaign registration, longer in busy periods, and 1 to 4 weeks end to end.
What does registration cost?
Registration and related messaging charges depend on the route, sender type and market. Consult the current provider rate card for the intended traffic rather than assuming one global fee.
Can I get pricing programmatically?
All three offer something. Twilio's Pricing API returns real time account specific rates, which is the most useful because it reflects your actual position. Telnyx publishes machine readable rate cards at a public endpoint. Vonage's Pricing API v2 covers outbound SMS and voice with basic authentication at one request per second.
Should I use these instead of a sales dialer?
No, they solve different problems. A dialer gives a human rep a calling interface with CRM logging. These give your code numbers and a per minute rate. Teams building agent driven calling use these; teams equipping reps buy a phone system or a parallel dialer.
What is the largest cost people underestimate?
Media processing and carrier surcharges. Transcription at $0.0500 per minute standard on Twilio can exceed the cost of the calls being transcribed, and per message carrier surcharges of $0.003 to $0.005 can rival the message rate itself at moderate volume. Model both before committing to a provider.
Call handling also needs a review process. Our guide to conversation intelligence tools covers the adjacent options.
Work with Forma Nôrden
We build signal based outbound systems for B2B companies selling into the enterprise and upper mid market. When calling and messaging become programmable, the registration path and the media processing bill decide the architecture more than the per minute rate does. Explore how we work.
For enquiries about this article: partnerships@formanorden.com
