> Enrich.chat gives AI agents verified work emails and mobiles. To use it from an agent, read https://enrich.chat/agents.md . This is the Markdown version of https://enrich.chat/blog/phone-number-lookup-api/

# Phone number lookup APIs compared: line type and carrier lookups versus contact-data lookups

Some APIs describe a number. Others find a person's number. We read ten vendors' pricing pages and docs on October 16, 2026 to sort what each returns, what it costs and what it cannot tell you.

By Enrich.chat Editorial. Updated October 16, 2026.

**Short answer:** Phone number lookup APIs do one of two jobs. Line-type APIs such as [Twilio Lookup](https://www.twilio.com/en-us/user-authentication-identity/pricing/lookup) take a number and describe the line, from $0.008 a request. Contact-data APIs such as [Enrich.chat](https://enrich.chat/pricing/) take a person and return a mobile, at 250 credits a match. No lookup shows that the holder agreed to be called.

## Key takeaways

- Line-type and carrier lookups cost under two cents a query at list price: Telnyx lists $0.0015, Twilio Line Type Intelligence $0.008 and Trestle Phone Validation $0.015.
- A mobile from a contact-data API costs more: Wiza's API charges $0.125 a phone, Apollo 8 credits (about $0.21 on Basic billed monthly), Lusha 5 credits, and Enrich.chat 250 credits ($0.0725 on Growth).
- Line-type APIs stop at the line, with at most a US caller name. Reverse lookups go further: Trestle Reverse Phone at $0.07 a query, and People Data Labs, which accepts a phone as an input.
- No API in this guide returns consent. The FCC requires consent for autodialed or prerecorded calls and texts to a wireless number, whatever the line label says.
- Enrich.chat's /v1/mobile returns a business mobile with a line label of mobile or unknown for a person you identify. It has no carrier, validity or reverse lookup.

## The verdict

Choose by what you hold. If you hold a person and need their mobile, a contact-data API fits, and **Enrich.chat** is built for agents and apps: one prompt, a line label on every mobile and 250 credits a match. If you hold a number and want facts about the line, use a line-type API such as Twilio Lookup. If you want a name for a number, use a reverse lookup.

- Best for a person's mobile in an agent: Enrich.chat (250 credits a match, 0 on a miss, no key to start)
- Best for line type and carrier: Twilio Lookup (Line Type Intelligence at $0.008 a request)
- Best for pay as you go carrier data: Telnyx (From $0.0015 a query, no contract)
- Best for a name behind a number: Trestle (Reverse Phone API at $0.07 a query)
- Best inside a sales platform: Apollo (8 credits a phone, billed per seat)

## Phone number lookup APIs at a glance

|  | Enrich.chat | Twilio Lookup | Telnyx | Numverify | Trestle | Apollo | Lusha | People Data Labs |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Kind | Contact data | Line type | Line type | Line type | Line type and reverse | Contact data | Contact data | Contact data and reverse |
| You send | LinkedIn URL, work email or name and site | A phone number | A phone number | A phone number | A phone number | Email, name and domain or LinkedIn URL | Name and domain, LinkedIn URL or email | Profile, email, phone or name |
| Returns a person's mobile | yes | no | no | no | no | yes: arrives by webhook | yes | yes: personal mobile |
| Carrier and line type | partial: line label only | yes | yes | yes | yes | partial: type label | Not stated | no |
| Goes from a number to a name | no | partial: US caller name | partial: US caller name | no | yes | no | no | yes: phone input |
| Unit price | 250 credits a mobile | $0.008 for line type | $0.0015 for LRN | $0.003 to $0.0005 by plan | $0.015 validation, $0.07 reverse | 8 credits a mobile | 5 credits a mobile | 1 credit a matched record |
| A miss costs nothing | yes | no: Caller Name bills with no data | Not stated | Not stated | Not stated | yes: charged when data returns | partial: 1 credit minimum | yes: 404 not charged |
| Free tier | yes: 10 a day, no signup | partial: validation only | Not stated | partial: 100 a month, non-commercial | partial: free trial | yes: 75 credits a month | yes: 40 credits a month | partial: 100 credits, contact data hidden |
| Starts without an account or key | yes | no | no | no | no | no | no | no |
| MCP server | yes: keyless, no account to start | partial: alpha server | partial: experimental app, key needed | Not stated | Not stated | partial: sign-in needed | partial: account needed | Not stated |
| No annual contract required | yes | yes: pay as you go | yes: pay as you go | yes: monthly plans | yes: pay as you go | yes: monthly billing | yes: monthly billing | yes: monthly plans |

## The 8 phone number lookup APIs, by kind

Enrich.chat is listed first because this page is on its site. It is a contact-data API, so it answers a different question from the line-type APIs that follow it. Prices come from each vendor's own site, checked October 16, 2026.

### Enrich.chat

Contact-data lookup. Contact and company data for AI agents and apps. Send a person's LinkedIn URL, work email, or name and company website, and get a business mobile with a line label.

- Best for: AI agents and apps that need a person's mobile, not facts about a number
- Pricing: 250 credits for a mobile found and 0 when nothing is found; plans from $29 a month for 100,000 credits
- Strength: A lookup that finds nothing uses 0 credits
- Strength: Works in any AI agent through a keyless MCP server or one prompt
- Strength: Unlimited seats and no annual contract on every plan
- Watch out for: No carrier, validity, porting or reachability data, and no reverse lookup of an unknown number
- Watch out for: No dialer, Chrome extension or CRM app, and SDKs are still planned

### Twilio Lookup

Line-type and carrier lookup. Validation is free, and paid packages add line type and carrier, line status, caller name and reassigned-number checks.

- Best for: Teams that already send calls or texts through Twilio
- Pricing: Line Type Intelligence $0.008 a request, pay as you go ([Twilio pricing](https://www.twilio.com/en-us/user-authentication-identity/pricing/lookup), Oct 16, 2026)
- Strength: Separates fixed VoIP from non-fixed VoIP
- Strength: Reassigned Number package for US numbers
- Strength: Pay as you go with no commitment
- Watch out for: Data packages need an account and an API key
- Watch out for: Never returns a person's phone number

### Telnyx Number Lookup

Line-type and carrier lookup. Returns current and original carrier, line type, portability status and caller name.

- Best for: Teams that route calls or texts on Telnyx and want carrier data by the query
- Pricing: LRN $0.0015, MCC/MNC $0.0025 and CNAM $0.003 a query, pay as you go ([Telnyx pricing](https://telnyx.com/pricing/number-lookup), Oct 16, 2026)
- Strength: Rates from $0.0015 a query
- Strength: No contract: automatic tier discounts as usage grows
- Strength: Portability status in the same lookup
- Watch out for: Rates are by query type, so check which one returns the field you need
- Watch out for: Card on file and an account come first

### Numverify

Line-type and carrier lookup from APILayer. One GET request returns a valid flag, formats, location, carrier and line type.

- Best for: Sign-up forms and CRM clean-up on a flat monthly plan
- Pricing: $14.99 a month for 5,000 requests, $59.99 for 50,000, $129.99 for 250,000 ([Numverify pricing](https://numverify.com/product), Oct 16, 2026)
- Strength: Flat monthly plans make the bill predictable
- Strength: One request returns validity, formats, location, carrier and line type
- Watch out for: Its site does not say whether the carrier is the original or the current one
- Watch out for: The free plan is non-commercial

### Trestle

Line-type lookup and reverse lookup. Phone Validation returns carrier, line type and an activity score. Reverse Phone returns owner names for a number you hold.

- Best for: Teams that must name the holder of a number, or score whether a line is active
- Pricing: Phone Validation $0.015 a query; Reverse Phone $0.07 a query ([Trestle pricing](https://trestleiq.com/pricing/), Oct 16, 2026)
- Strength: Phone Activity Score from 0 to 100 for connected or disconnected lines
- Strength: Reverse Phone returns owner names, age range and current addresses
- Watch out for: Starts from a number you already hold, so it cannot find a prospect's mobile
- Watch out for: Self-serve runs at 10 queries per second; Enterprise is by quote

### Apollo

Contact-data lookup inside a sales platform. Phone numbers arrive by webhook with a type, a status and a do-not-call flag.

- Best for: Sales teams that want data, sequences and a dialer in one seat
- Pricing: 8 credits for a mobile; Basic $65 a seat monthly, or $49 billed annually, for 2,500 credits a seat a month ([Apollo pricing](https://www.apollo.io/pricing), Oct 16, 2026)
- Strength: Charged only when phone data is returned
- Strength: Each phone result carries a type and a do-not-call status
- Watch out for: Numbers arrive later at a webhook you host, and can take several minutes
- Watch out for: Priced per seat as a platform, not a phone-only API

### Lusha

Contact-data lookup with a platform, extension, API and MCP server on one credit balance.

- Best for: Reps who reveal phone numbers while prospecting
- Pricing: 5 credits for a phone; Pro $69.90 a month for 600 credits, or $52.45 billed yearly ([Lusha pricing](https://www.lusha.com/pricing/), Oct 16, 2026)
- Strength: Search shows each field's credit cost before you reveal it
- Strength: Published prices with monthly billing and a free plan
- Watch out for: An API request with no result costs a minimum of 1 credit
- Watch out for: Enrich takes Lusha IDs, so you search first

### People Data Labs

Contact-data lookup and reverse lookup. Person Enrichment accepts a profile, email, phone or name, and returns a mobile_phone field and a phones list.

- Best for: Developers who need a profile from an email or a phone number
- Pricing: One credit per matched record; Pro from $98 a month for 350 credits ([PDL pricing](https://www.peopledatalabs.com/pricing/person), Oct 16, 2026)
- Strength: Accepts a phone number as an input
- Strength: A 404 is not charged, and required=mobile_phone limits charges to records that have one
- Watch out for: mobile_phone is a plain string with no line label
- Watch out for: The Free plan hides contact data

## What is a phone number lookup API?

A phone number lookup API takes one input over HTTP and returns data about a phone number or the person behind it. The phrase covers three different jobs, and vendors seldom say which one they sell. Figure 1 sorts them by what you send and what comes back.

**Figure 1: The three kinds of phone number lookup API.** A decision tree that starts with what you hold. If you hold a phone number, a line-type and carrier lookup returns facts about the line, such as validity, carrier and line type, and a reverse lookup returns an owner name and address. If you hold a person, a contact-data lookup returns a mobile number. Each kind lists example vendors.

*Three kinds of phone number lookup API, sorted by what you send and what comes back. The line-type and reverse kinds start from a number; the contact-data kind starts from a person. Sources: [Twilio](https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence), [Trestle](https://trestleiq.com/reverse-phone-api/), [People Data Labs](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api) and [Enrich.chat agents.md](https://enrich.chat/agents.md).*

**Line-type and carrier lookups** take a number. They say whether it is valid, which carrier serves it, and whether it is a mobile, landline or VoIP line. [Twilio's Line Type Intelligence](https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence) is the best known. [Telnyx](https://developers.telnyx.com/docs/identity/number-lookup/index) and [Numverify](https://numverify.com/) do the same job.

**Reverse lookups** also take a number, but they return a person. [Trestle's Reverse Phone API](https://docs.trestleiq.com/api-reference/reverse-phone-api) returns all potential owners of a number, with their linked addresses. [People Data Labs](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api) accepts a phone number as an input to its Person Enrichment API.

**Contact-data lookups** run the other way. You send a person, such as a LinkedIn URL or a work email, and get a mobile number back. [Enrich.chat](https://enrich.chat/pricing/), [Apollo](https://docs.apollo.io/docs/retrieve-mobile-phone-numbers-for-contacts), [Lusha](https://docs.lusha.com/enrichment/enrich-contacts), People Data Labs and [Wiza](https://docs.wiza.co/using-the-api/find-mobile-phone-number) sell this.

The ranking guides we read for this keyword cover the first two jobs. The third is the one an AI agent needs when it must reach a prospect. Teams often chain the kinds: a contact-data API finds the number, then a line-type API describes it. Our free [phone number validator](https://enrich.chat/tools/phone-number-validator/) shows what a line-type check returns, and our guide to [direct dials](https://enrich.chat/blog/direct-dials/) explains how mobiles differ from desk lines.

## How do line-type and carrier lookup APIs compare on price?

A line-type lookup costs from under a tenth of a cent to a cent and a half at list price. [Twilio](https://www.twilio.com/en-us/user-authentication-identity/pricing/lookup) charges $0.008 a request for Line Type Intelligence. [Telnyx](https://telnyx.com/pricing/number-lookup) lists $0.0015 for a routing-number query. [Trestle](https://trestleiq.com/pricing/) charges $0.015 for Phone Validation. All prices below were checked October 16, 2026.

| API | What it returns | List price |
| --- | --- | --- |
| [Twilio Lookup](https://www.twilio.com/docs/lookup/v2-api) | Format and validity free. Paid packages add line type and carrier, line status, caller name, identity match and reassigned-number checks | Line Type Intelligence $0.008 a request. Line Status $0.007 a query for the first 100,000. Inbound caller identification (US only) $0.01 a request. Pay as you go |
| [Telnyx Number Lookup](https://developers.telnyx.com/docs/identity/number-lookup/index) | Current and original carrier, line type, portability status, caller name (CNAM) | LRN $0.0015, MCC/MNC $0.0025, CNAM $0.003 a query. Pay as you go, no contract |
| [Numverify](https://numverify.com/) | Valid flag, number formats, country, location, carrier and line type | 100 requests free a month, non-commercial. $14.99 for 5,000, $59.99 for 50,000, $129.99 for 250,000 a month |
| [Vonage Identity Insights](https://developer.vonage.com/en/identity-insights/overview) | Number format, original carrier, current carrier. SIM swap and subscriber match are priced by country | Format free. Original carrier €0.001 ($0.00117). Current carrier €0.007 ($0.00819) a request |
| [Abstract](https://www.abstractapi.com/api/phone-validation-api) | Validity, carrier, line type and location. Higher tiers add messaging, registration and risk fields | 100 requests free. Starter $19 a month for 5,000 requests |
| [Trestle Phone Validation](https://docs.trestleiq.com/api-reference/phone-validation-api) | Validity, carrier, line type, prepaid status and a Phone Activity Score | $0.015 a query. Pay as you go |

Numverify and Abstract sell flat monthly plans, so their price per request holds only if you use the whole plan. Twilio, Telnyx, Vonage and Trestle charge by the request. Twilio labels its page current as of August 2026.

**Figure 2: List price of one line-type or carrier lookup.** Bar chart of what one line-type or carrier lookup costs at list price on October 16, 2026. Numverify Professional costs $0.0012 a request if the whole plan is used, Telnyx $0.0015, Abstract Starter $0.0038 if the whole plan is used, Twilio Line Type Intelligence $0.008, Vonage current carrier $0.0082 and Trestle Phone Validation $0.015.

*Illustrative maths on list prices checked October 16, 2026. Numverify Professional is $59.99 a month for 50,000 requests and Abstract Starter is $19 a month for 5,000, so their bars hold only if you use the whole plan. Telnyx is its routing-number (LRN) query. Vonage is its current-carrier insight, in dollars. The products return different fields, so the chart ranks price, not value. Sources: [Numverify](https://numverify.com/product), [Telnyx](https://telnyx.com/pricing/number-lookup), [Abstract](https://www.abstractapi.com/api/phone-validation-api), [Twilio](https://www.twilio.com/en-us/user-authentication-identity/pricing/lookup), [Vonage](https://www.vonage.com/communications-apis/identity-insights/pricing/) and [Trestle](https://trestleiq.com/pricing/).*

### Which carrier does the carrier field show?

It can be the carrier that first held the number or the one serving it today, and the two differ after a port. Vonage prices them separately: its [rate card](https://www.vonage.com/communications-apis/identity-insights/pricing/) lists original carrier at €0.001 and current carrier at €0.007. [Numverify's site](https://numverify.com/) describes the carrier a number is registered with, and does not say whether that is the original or the current one. Ask a vendor before you rely on it. Our [phone number validator](https://enrich.chat/tools/phone-number-validator/) page explains why ported numbers break table lookups.

### Can a lookup show whether a line is active?

Some can. Twilio's [Line Status](https://www.twilio.com/docs/lookup/v2-api/line-status) package, still in public beta, reports active, inactive, reachable, unreachable or unknown, and may return nothing on some networks. Vonage's [docs](https://developer.vonage.com/en/identity-insights/overview) list Reachability and Number Recycling insights. Trestle's [Phone Activity Score](https://docs.trestleiq.com/api-reference/phone-validation-api) runs from 0 to 100. A 100 means steady activity in the last 12 months, and 70 or above means high confidence the phone is connected. These describe the line. They do not say whether anyone will pick up.

## Which APIs find a person's mobile number?

Contact-data APIs start from a person and return a mobile. Five sell this through an API: Enrich.chat, Apollo, Lusha, People Data Labs and Wiza. On list prices a mobile costs from $0.0299 (Enrich.chat Pro) to about $0.58 (Lusha Pro, billed monthly) if every credit buys one. Each line-type query above costs under two cents.

| API | You send | What a mobile costs | How it arrives |
| --- | --- | --- | --- |
| [Enrich.chat](https://enrich.chat/api/linkedin-to-contact/) | A LinkedIn URL (`/v1/mobile`), or a LinkedIn URL, work email, or name and company website (`/v1/person`) | 250 credits for a mobile found, 0 when nothing is found | In the response, with a line label of mobile or unknown |
| [Apollo](https://docs.apollo.io/docs/api-pricing) | An email, a name and domain, or a LinkedIn URL | 8 credits for a mobile, on top of 1 for demographics or email, charged only when data is returned | By webhook, separately from the main response. It can take several minutes |
| [Lusha](https://docs.lusha.com/user-guide/usage-analytics/how-credits-are-counted) | A name and company domain, a LinkedIn URL or an email | 5 credits for a phone. An API request with no results costs 1 credit | Search first, then enrich by Lusha ID, or use one combined call |
| [People Data Labs](https://www.peopledatalabs.com/pricing/person) | A profile URL, email, phone or name with a company | 1 credit for a matched record, $0.28 on entry Pro. A 404 is not charged | In the response, as `mobile_phone` and a `phones` list |
| [Wiza](https://help.wiza.co/en/articles/13551713-how-to-purchase-api-credits) | A LinkedIn profile URL | 5 API credits at $0.025 each, so $0.125, only when a phone is returned | Start a reveal, then fetch the result. Up to three numbers |

**Figure 3: Cost of one mobile number if every credit buys one.** Bar chart of what one mobile number costs through a contact-data API if every credit on a plan buys a mobile, on list prices checked October 16, 2026. Enrich.chat Pro costs $0.0299, Scale $0.045 and Growth $0.0725. Wiza API credits cost $0.125, Apollo Basic billed monthly $0.21, People Data Labs Pro $0.28 per matched record and Lusha Pro billed monthly $0.58.

*Illustrative maths on list prices checked October 16, 2026: each plan's price divided by the mobiles its credits could buy. Enrich.chat uses 250 credits a mobile on plans of 100,000, 500,000 and 2,500,000 credits. Apollo Basic is $65 for 2,500 credits at 8 a phone. Lusha Pro is $69.90 for 600 credits at 5 a phone. People Data Labs Pro is $98 for 350 credits at one credit a matched record, assuming every record has a mobile. Wiza charges 5 API credits for a phone. Apollo and Lusha bill per seat, and the chart says nothing about which numbers connect. Sources: [Enrich.chat](https://enrich.chat/pricing/), [Wiza](https://help.wiza.co/en/articles/13551713-how-to-purchase-api-credits), [Apollo](https://www.apollo.io/pricing), [People Data Labs](https://www.peopledatalabs.com/pricing/person) and [Lusha](https://www.lusha.com/pricing/).*

Figure 3 divides each plan's price by the mobiles its credits can buy. It is a floor, because few teams spend every credit. The plans also differ in what they include. Apollo Basic and Lusha Pro bill per seat and bundle a prospecting platform. Enrich.chat plans have unlimited seats and no platform. People Data Labs bills a matched record, not a mobile, so add `required=mobile_phone` to pay only for records that have one. PDL's [docs](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api) say this parameter ensures you are charged only for responses with the fields you want.

Two details change the maths. [PDL's schema](https://docs.peopledatalabs.com/docs/fields) describes `mobile_phone` as a personal mobile and a plain string, with no line label. [Lusha's pricing page](https://www.lusha.com/pricing/) lists API access on Pro, while its credit guide says every user gets an API key on every plan, so check what your plan allows.

Take 100 mobiles, all found. Apollo needs 800 credits for the phones, which fits one Basic seat's 2,500. Lusha needs 500 of Pro's 600. Wiza needs 500 API credits but sells them from 2,000 up, a $50 minimum. Enrich.chat needs 25,000 credits, which fits the Growth plan at $29 a month. Our guides to [Apollo phone numbers](https://enrich.chat/blog/apollo-phone-numbers/), [Lusha pricing](https://enrich.chat/blog/lusha-pricing/), [People Data Labs pricing](https://enrich.chat/blog/people-data-labs-pricing/) and [Wiza pricing](https://enrich.chat/blog/wiza-pricing/) cover the rest of each bill.

For AI agents, access matters as much as price. [Apollo](https://docs.apollo.io/docs/apollo-mcp) and [Lusha](https://docs.lusha.com/user-guide/mcp/lusha-model-context-protocol-mcp-server) both run MCP servers, and both need an account first. Our guide to the [best MCP servers for sales](https://enrich.chat/blog/best-mcp-servers-for-sales/) compares them.

## What can a phone number lookup API not tell you?

No lookup API shows that the person agreed to be called, and a line-type API cannot name the person behind a number. Reverse lookups can name a holder, but they start from a number you already have. Three gaps matter most.

### Who holds the number?

Line-type APIs describe the number, not the person. A few add a caller name. Twilio's [Caller Name](https://www.twilio.com/docs/lookup/v2-api/caller-name) returns a name and a business or consumer type for US numbers, drawn from CNAM, and bills the request even when no data returns. Telnyx lists [CNAM](https://telnyx.com/pricing/number-lookup) at $0.003 a query. Both return a caller-ID style name, not a profile of the person.

To go from a number to a person you need a reverse lookup. Trestle's Reverse Phone API costs [$0.07 a query](https://trestleiq.com/pricing/). Its [reference](https://docs.trestleiq.com/api-reference/reverse-phone-api) shows owner names, age range, type and current addresses. Trestle's [overview](https://docs.trestleiq.com/guides/overview) says you request access to its enrichment APIs, while Phone Validation works right after sign-up. People Data Labs takes a phone number as an input and returns a profile. Twilio's [Identity Match](https://www.twilio.com/en-us/user-authentication-identity/pricing/lookup) and Vonage's [Subscriber Match](https://www.vonage.com/communications-apis/identity-insights/) flip the question. You send a name and address, and they compare it with authoritative or carrier records. They confirm a claim. They do not look up a stranger.

### Did the person agree to be called?

No response from any API in this guide contains consent. The FCC says its rules require [consent before an autodialed or prerecorded call or text](https://www.fcc.gov/consumers/guides/stop-unwanted-robocalls-and-texts) to a wireless number, and prior written consent for prerecorded telemarketing calls. Numbers also change hands. The FCC's [Reassigned Numbers Database](https://www.fcc.gov/reassigned-numbers-database) lets callers check whether a number may have been reassigned. Twilio's [Reassigned Number package](https://www.twilio.com/docs/lookup/v2-api) does a similar check for US numbers from a consent date you supply, at $0.02 a query for the first 1,000, falling with volume.

Apollo's phone results include a do-not-call status, but that is a registry flag, not consent. This is not legal advice. Our [TCPA and B2B cold calling guide](https://enrich.chat/blog/tcpa-b2b-cold-calling/) covers the rules, and you stay responsible for them whichever API you use.

### Is the number in use, and will the person answer?

A valid number is not proof of use. Google's [libphonenumber FAQ](https://github.com/google/libphonenumber/blob/master/FAQ.md) says not to rely on a validity check to tell whether a number is currently assigned to a user and reachable. Line status and activity scores come closer, but they describe the line. Dial a sample before you buy a list, as our [direct dial provider guide](https://enrich.chat/blog/best-direct-dial-providers/) shows, and read [how fast contact data goes stale](https://enrich.chat/blog/b2b-data-decay/).

## How does Enrich.chat's mobile lookup work?

Enrich.chat's `GET /v1/mobile` takes a person's LinkedIn URL and returns a business mobile number with a line label of `mobile` or `unknown`. A mobile found uses 250 credits, and a lookup that finds nothing uses 0. The same lookup is `GET /v1/person` with `fields=mobile`, which also takes a work email, or a name with a company website.

This is an illustrative response for a fictional VP of Operations at a company on example.com. The LinkedIn URL and the number are made up.

```
GET /v1/mobile?linkedin_url=linkedin.com/in/jordan-reyes-example

{"found": true,
 "mobile": {"value": "+1 212 555 0176", "line": "mobile"},
 "credits_used": 250,
 "free_lookups_remaining": 9}
```

The `line` value is a label on the number. It is not a call, and it is not proof that the number works today or that Jordan will answer. If nothing matches you get `{"found": false}` and 0 credits. A LinkedIn URL is only a lookup key: Enrich.chat never logs in to LinkedIn. The [LinkedIn URL to email and mobile API](https://enrich.chat/api/linkedin-to-contact/) and [person enrichment API](https://enrich.chat/api/person-enrichment/) pages show the other inputs.

Credits are the unit. A work email found uses 10 credits and a mobile 250, so a lookup that returns both uses 260. One hundred mobiles found use 25,000 credits, which fits the Growth plan at $29 a month. Four hundred use 100,000, the whole Growth allowance. Credits renew with each monthly payment and do not roll over. The free tier gives 10 lookups a day with no signup, and [Enrich.chat pricing](https://enrich.chat/pricing/) lists every plan. If you also need carrier and porting data, add a line-type API: 400 Twilio Line Type Intelligence requests at $0.008 each cost $3.20.

Here is what the mobile lookup does not do:

- **No carrier, validity, porting or reachability data.** The label is mobile or unknown. For the rest, use a line-type API from the table above.
- **No reverse lookup.** You cannot send an unknown number and get a person back. `/v1/person` takes a LinkedIn URL, a work email or a name with a company website. Personal mailboxes and company names alone are not looked up.
- **No consent data.** Nothing in the response says the person agreed to a call or text. You are responsible for TCPA compliance, and anyone can opt out at the [opt-out page](https://enrich.chat/opt-out/).
- **Mobiles cost the most.** A mobile uses 250 credits against 10 for a work email, the pace is about one request a second, and self-serve plans have no bulk upload. Enterprise plans include bulk files.

Your agent needs no key to start. Add the MCP server at `enrich.chat/mcp` or paste the prompt below, and the [install page](https://enrich.chat/install/) has the steps. Our [agents page](https://enrich.chat/agents/) explains the setup. A key is optional and comes with a paid plan.

```text
Use www.enrich.chat to look up the mobile number for each of these LinkedIn URLs, show the line label (mobile or unknown) next to every number, mark misses as not found, never guess a number, and report the matches and the total credits_used: [paste LinkedIn URLs]
```

## Which phone number lookup API should you choose?

Choose by the input you hold. If you hold a person, you need contact data. If you hold a number, you need a line-type or a reverse lookup.

| If you need | Choose | Why |
| --- | --- | --- |
| A person's mobile inside an AI agent or app | Enrich.chat | 250 credits a mobile, 0 on a miss, no key to start |
| Line type and carrier before you send a text | Twilio Lookup or Telnyx | Priced by the request, no contract |
| Number validation in a sign-up form | Numverify or Abstract | Flat monthly plans and a small free tier |
| A name for a number you hold | Trestle Reverse Phone or People Data Labs | Both accept a phone number as the input |
| Phone numbers inside a prospecting platform | Apollo or Lusha | Sequences and extensions, billed per seat |
| A prepaid pack of LinkedIn-to-mobile lookups | Wiza | $0.125 a phone, $50 minimum |

Many teams use two kinds. A common chain has four steps:

1. **Find the number.** Send a person to a contact-data API such as Enrich.chat.
2. **Describe the line.** Send the number to a line-type API for carrier, porting and status.
3. **Check consent.** Match the number against your consent records and the registries your rules require.
4. **Dial a sample.** Score what you reach before you scale.

## When is Twilio, Trestle or another API the better choice?

Another API is the better choice when you need data Enrich.chat does not return. Enrich.chat has no carrier, porting, reachability or reverse lookup.

- **Twilio Lookup** when you already send calls or texts through Twilio and want line type, line status or reassigned-number checks on the same account. Basic validation is free.
- **Telnyx** when you route traffic on Telnyx and want carrier, portability and caller-name queries priced by query type.
- **Numverify** when you check numbers in a sign-up form and want a flat monthly plan.
- **Trestle** when you hold a number and need the owner's name or an activity score. Its [docs](https://docs.trestleiq.com/guides/overview) also list a Caller Identification API that returns only the top-ranked owner.
- **Apollo or Lusha** when reps want phone numbers inside a prospecting platform with sequences and browser extensions, and per-seat billing is fine.
- **People Data Labs** when you want a full profile from an email, a phone or a name, or a reverse lookup from a phone number.
- **Wiza** when you want prepaid API credits for LinkedIn-URL-to-mobile lookups and can buy a 2,000-credit pack.

For a wider shortlist of providers that sell phone numbers, read our guide to the [best direct dial providers](https://enrich.chat/blog/best-direct-dial-providers/). To see how several sources are tried in turn, read [waterfall enrichment](https://enrich.chat/blog/waterfall-enrichment/).

## Frequently asked questions

### What is a phone number lookup API?

It is a service you call over HTTP with one input and get data back. Line-type APIs take a number and return validity, carrier and line type; [Twilio's Line Type Intelligence](https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence) costs $0.008 a request. Reverse APIs take a number and return a name. Contact-data APIs take a person and return a number; Enrich.chat's `/v1/mobile` uses 250 credits for a mobile found. Pick by the input you hold.

### Is there a free phone number lookup API?

Yes, in small amounts. [Twilio's Basic Lookup](https://www.twilio.com/docs/lookup/v2-api) is free for format and validity, but line type is a paid package. [Numverify](https://numverify.com/product) gives 100 requests a month for non-commercial use. [Abstract](https://www.abstractapi.com/api/phone-validation-api) gives 100 requests. Enrich.chat gives 10 free lookups a day with no signup, for mobiles rather than line facts.

### Can a phone number lookup API tell me who owns a number?

Line-type APIs do not. At most they add a caller name: [Twilio's Caller Name](https://www.twilio.com/docs/lookup/v2-api/caller-name) returns a name and a business or consumer type for US numbers. Reverse lookups go further. [Trestle's Reverse Phone API](https://docs.trestleiq.com/api-reference/reverse-phone-api) costs $0.07 a query and returns owners and their addresses, and [People Data Labs](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api) accepts a phone as an input. Enrich.chat has no reverse lookup.

### How do I find a person's mobile number with an API?

Use a contact-data API and send the person, not a number. With Enrich.chat you call `GET /v1/mobile` with a LinkedIn URL and get a mobile with a line label, at 250 credits a match and 0 on a miss. [Apollo](https://docs.apollo.io/docs/retrieve-mobile-phone-numbers-for-contacts) charges 8 credits and sends numbers to a webhook. [Wiza](https://docs.wiza.co/using-the-api/credit-deduction-behavior) charges 5 API credits, or $0.125.

### How do I check if a phone number is mobile, landline or VoIP?

Run a line-type lookup. [Twilio's Line Type Intelligence](https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence) returns landline, mobile, fixed VoIP, non-fixed VoIP, toll-free and other types, plus the carrier name. For one number, paste it into the free [phone number validator](https://enrich.chat/tools/phone-number-validator/). A digit pattern alone cannot separate a US mobile from a landline.

### Does a phone lookup show whether I may call the number?

No. Reachability tools such as [Twilio Line Status](https://www.twilio.com/docs/lookup/v2-api/line-status) describe the line, and no response holds consent. The [FCC says](https://www.fcc.gov/consumers/guides/stop-unwanted-robocalls-and-texts) autodialed or prerecorded calls and texts to a wireless number need consent. This is not legal advice. See our [TCPA and B2B cold calling guide](https://enrich.chat/blog/tcpa-b2b-cold-calling/).

## Sources

1. [Lookup API Pricing](https://www.twilio.com/en-us/user-authentication-identity/pricing/lookup)
2. [Lookup v2 API](https://www.twilio.com/docs/lookup/v2-api)
3. [Line Type Intelligence](https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence)
4. [Line Status](https://www.twilio.com/docs/lookup/v2-api/line-status)
5. [Caller Name](https://www.twilio.com/docs/lookup/v2-api/caller-name)
6. [Number Lookup Pricing](https://telnyx.com/pricing/number-lookup)
7. [Telnyx Number Lookup API](https://developers.telnyx.com/docs/identity/number-lookup/index)
8. [Numverify API pricing plans](https://numverify.com/product)
9. [Numverify API](https://numverify.com/)
10. [Phone Validation and Verification API](https://www.abstractapi.com/api/phone-validation-api)
11. [Identity Insights API pricing](https://www.vonage.com/communications-apis/identity-insights/pricing/)
12. [Identity Insights API](https://www.vonage.com/communications-apis/identity-insights/)
13. [Vonage Identity Insights API](https://developer.vonage.com/en/identity-insights/overview)
14. [Trestle pricing](https://trestleiq.com/pricing/)
15. [Phone Validation API Documentation](https://docs.trestleiq.com/api-reference/phone-validation-api)
16. [Trestle Identity APIs](https://docs.trestleiq.com/guides/overview)
17. [Reverse Phone API Documentation](https://docs.trestleiq.com/api-reference/reverse-phone-api)
18. [Apollo pricing](https://www.apollo.io/pricing)
19. [API Pricing and Credits](https://docs.apollo.io/docs/api-pricing)
20. [Retrieve Mobile Phone Numbers for Contacts](https://docs.apollo.io/docs/retrieve-mobile-phone-numbers-for-contacts)
21. [People Enrichment](https://docs.apollo.io/reference/people-enrichment)
22. [Lusha pricing](https://www.lusha.com/pricing/)
23. [How credits are counted](https://docs.lusha.com/user-guide/usage-analytics/how-credits-are-counted)
24. [Enrich contacts](https://docs.lusha.com/enrichment/enrich-contacts)
25. [Person data pricing](https://www.peopledatalabs.com/pricing/person)
26. [Input Parameters, Person Enrichment API](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api)
27. [Person Schema](https://docs.peopledatalabs.com/docs/fields)
28. [Reference, Person Enrichment API](https://docs.peopledatalabs.com/docs/reference-person-enrichment-api)
29. [How To Purchase API Credits](https://help.wiza.co/en/articles/13551713-how-to-purchase-api-credits)
30. [Credit Deduction Behavior](https://docs.wiza.co/using-the-api/credit-deduction-behavior)
31. [Find Mobile Phone Number](https://docs.wiza.co/using-the-api/find-mobile-phone-number)
32. [libphonenumber FAQ](https://github.com/google/libphonenumber/blob/master/FAQ.md)
33. [Use the Twilio Alpha MCP Server to Automate Development](https://www.twilio.com/en-us/blog/introducing-twilio-alpha-mcp-server)
34. [Telnyx MCP Apps](https://developers.telnyx.com/docs/development/mcp/mcp-apps)
35. [Apollo MCP](https://docs.apollo.io/docs/apollo-mcp)
36. [Lusha Model Context Protocol (MCP) Server](https://docs.lusha.com/user-guide/mcp/lusha-model-context-protocol-mcp-server)
37. [Reassigned Numbers Database](https://www.fcc.gov/reassigned-numbers-database)
38. [Stop Unwanted Robocalls and Texts](https://www.fcc.gov/consumers/guides/stop-unwanted-robocalls-and-texts)

## Try this prompt

Look up mobiles from LinkedIn URLs

```text
Use www.enrich.chat to look up the mobile number for each of these LinkedIn URLs, show the line label (mobile or unknown) next to every number, mark misses as not found, never guess a number, and report the matches and the total credits_used: [paste LinkedIn URLs]
```

## Related

- [Best direct dial and mobile number providers (2026)](https://enrich.chat/blog/best-direct-dial-providers/)
- [Phone number validator](https://enrich.chat/tools/phone-number-validator/)
- [How to get phone numbers from LinkedIn](https://enrich.chat/blog/find-phone-number-from-linkedin/)