LRN Pricing: What 3× Cheaper Means at Scale
Telnyx charges $0.0015 per LRN lookup. VRI charges $0.0005. The per-lookup gap is $0.001 — negligible in isolation, compounding fast at volume. Both providers pull LRN data from NPAC — the Number Portability Administration Center — the same authoritative source all carriers use. Accuracy is not the tradeoff.
| Monthly Lookups | VRI Cost | Telnyx Cost | Monthly Savings |
|---|---|---|---|
| 100,000 | $50 | $150 | $100 |
| 1,000,000 | $500 | $1,500 | $1,000 |
| 5,000,000 | $2,500 | $7,500 | $5,000 |
| 10,000,000 | $5,000 | $15,000 | $10,000 |
VRI's $0.0005 rate applies at all volumes; there's no minimum commitment or tiered gate to reach it.
What Telnyx Number Lookup Returns
Telnyx's number lookup API covers the fundamentals well. A standard response includes:
- LRN — the Local Routing Number used for call termination
- Carrier name — the current responsible carrier (T-Mobile, Verizon, AT&T, or an MVNO)
- Line type — mobile, landline, or VoIP
- Ported status — whether the number has been ported from its original carrier
- CNAM — caller name data where available
For basic call routing and line-type validation, Telnyx lookup is functional. The gap appears when you need to make decisions about SMS traffic, identify messaging infrastructure, or assess number age for fraud purposes.
What VRI Returns That Telnyx Doesn't
Messaging Provider Identification
Carrier data tells you who owns a number at the PSTN layer. Messaging provider identification tells you who is operating that number for SMS traffic right now — which CPaaS platform or aggregator is handling the messaging throughput on top of the underlying carrier.
- Spam and fraud detection — high-volume spam campaigns run through the same small set of messaging providers; flagging by provider is a distinct signal layer
- Traffic routing decisions — SMS aggregators can use messaging provider data to make smarter path selection and avoid double-counting traffic
- Compliance and audit — TCPA compliance teams increasingly need messaging infrastructure provenance, not just carrier ownership
Telnyx does not return messaging provider data at any price.
The activated_at Timestamp
The activated_at field records when a phone number was first activated on its current carrier.
This is distinct from the NPAC porting timestamp — it reflects the number's operational history at the
carrier activation layer.
- Fraud risk scoring — freshly activated numbers appear disproportionately in fraud, account takeover, and synthetic identity campaigns
- SMS delivery quality — some carrier filtering systems score newly activated numbers
differently;
activated_atlets you model delivery rate variance by number age - Contact database hygiene — if a contact's number was recently activated after dormancy, it may have been reassigned to a new subscriber
Telnyx number lookup does not return an activation timestamp. You cannot reconstruct this from ported status or carrier data alone.
Who Should Switch From Telnyx to VRI?
VRI is the stronger choice when any of the following apply:
- You run 100,000+ lookups per month — the $0.001/lookup savings compounds quickly
- You operate SMS or CPaaS infrastructure — messaging provider identification is a dataset unavailable in Telnyx's product, directly relevant to how you route, filter, and audit traffic
- You do fraud or risk scoring at the lookup layer —
activated_atis a high-signal fraud feature unavailable elsewhere at this price point - You need to pass audit or compliance review — regulators and enterprise buyers increasingly ask about messaging infrastructure provenance, not just carrier ownership
- You're building a phone number intelligence product — a richer data response means a richer downstream product without additional sourcing costs
Telnyx remains reasonable if you're deeply embedded in their broader telecom platform — SIP trunking, voice, number management — where switching costs are bundled. But if number lookup is a standalone API call in your stack, there's no lock-in worth preserving at 3× the price.
How to Migrate From Telnyx to VRI
- Sign up for VRI — 10 free lookups, no credit card required. Your API key is available immediately.
- Run parallel validation — point a portion of your lookup volume at VRI and compare responses. LRN, carrier, and line-type data should align with Telnyx; the additional fields (
messaging_provider,activated_at) will appear in VRI's response only. - Update your integration — swap the endpoint URL and API key. Adjust your response parsing to handle VRI's response schema, including the new fields if you want to use them downstream.
- Ramp down Telnyx — once you're confident in VRI's response quality, wind down the Telnyx integration and capture the savings.
Frequently Asked Questions
Is VRI's LRN data as accurate as Telnyx?
Yes. VRI sources LRN data from NPAC — the Number Portability Administration Center — the same authoritative database all carriers and LRN providers use. Accuracy is equivalent between VRI and Telnyx for LRN, carrier name, and line type. The difference is price and the additional data fields in VRI's response.
Does VRI offer a free trial?
Yes. Every VRI account starts with 10 free lookups, no credit card required. That's enough volume to
validate LRN accuracy, inspect messaging provider identification, and test the activated_at field
against your number sets before committing to a paid plan.
What is messaging provider identification?
Messaging provider identification is a data field that tells you which CPaaS platform or SMS aggregator is currently handling traffic on a specific phone number — independent of the underlying carrier. A number might be assigned to T-Mobile at the PSTN layer but operating through a major messaging platform at the application layer. Standard carrier lookup gives you the first layer; messaging provider identification gives you both.
What is the activated_at field and why does it matter?
The activated_at field records when a phone number was first activated on its current carrier.
Freshly activated numbers appear disproportionately in fraud campaigns and account takeover attempts.
Including activated_at in your lookup response lets you build activation age directly into your
risk models without a separate data source. Telnyx does not return this field.
How does VRI pricing scale for high-volume lookups?
VRI charges $0.0005 per LRN lookup at all volumes. There are no tiered commitments required to access this rate, and no minimum monthly spend. At 10 million lookups per month, VRI costs $5,000 — versus $15,000 on Telnyx at $0.0015 per lookup. The gap is $10,000 per month, or $120,000 annually at that volume.
Can I use VRI alongside Telnyx?
Yes. VRI is a standalone REST API that does not require you to route voice or SMS traffic through VRI's infrastructure. You can run VRI lookups in parallel with Telnyx during a validation period, then migrate incrementally as you confirm data quality meets your standards.
Does VRI support bulk or batch lookups?
Yes. VRI supports both single-number API calls and bulk lookup workflows for high-throughput use cases. If you're processing millions of lookups per day, contact the VRI team before starting to ensure optimal provisioning and throughput configuration for your volume.
Switch Today — LRN at $0.0005
10 free lookups. No credit card required. If you're currently paying $0.0015 per LRN on Telnyx, the math settles fast — and you gain messaging provider identification and activated_at data that Telnyx doesn't offer at any price.