US Phone Validation API — Carrier, Line Type & Owner
This is the deep check on a US number. It returns whether the number is valid, the carrier, the line type, whether it is prepaid, an activity score, a litigation-risk flag, and the owner records associated with it, each with its current addresses.
{
"session_id": "6e12…",
"kind": "phone_enrichment_us",
"phone": "12069735100",
"human": "Valid mobile number, active…",
"machine": {
"phone_number": "12069735100",
"is_valid": true,
"line_type": "mobile",
"carrier": "…",
"is_prepaid": false,
"activity_score": 87,
"is_litigator_risk": false,
"country_code": "US",
"owners": [
{
"name": "Jane Doe",
"type": "person",
"current_addresses": [
{ "city": "Austin", "state_code": "TX" }
]
}
]
},
"total_points": 100
}- You send
- A US phone number
- You get back
- Validity, carrier, line type, activity signals and owner records
- Coverage
- United States only.
- Price
- 100 pts — $100 per 1,000
- 100 points per number — $0.10 each. Only successful lookups are charged.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Calling and finding out | None up front | Regulatory exposure | In the United States the rules differ by line type, so this is the expensive way to learn |
| A carrier-lookup vendor | A separate contract, usually with a minimum commitment | Enterprise pricing | Another silo, and often no owner data alongside the number data |
| NeuralVerge | One request, same key as every other source | $0.10 per number | United States only, and it is the most expensive source in the catalog for a reason |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
phone_number | string | The number that was checked. |
is_valid | boolean | Whether the number is valid. |
line_type | string | Mobile, landline or another type — the field that governs how you may contact it. |
carrier | string | The carrier the number sits with. |
is_prepaid | boolean | Whether the line is prepaid. |
activity_score | number | How active the number appears to be. |
is_litigator_risk | boolean | Whether the number is associated with a history of claims. |
country_code | string | Country code and calling code for the number. |
owners | array | Owner records with names, type, age range where known, and current addresses. |
warnings | array | Any warnings raised during the check. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
US numbers are accepted with the leading country digit and no plus sign, as in the example. This is the only source in the catalog that returns carrier and line-type detail.
curl -X POST https://api.neuralverge.ai/functions/v1/run-phone-enrichment-us \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "phone": "12069735100" }'What teams use it for
Where this field shows up in an actual workflow.
Separate mobiles from landlines, and drop the numbers flagged for claim history.
Remove dead numbers before they burn agent time.
Work the numbers that are actually in use before the ones that are not.
Check the number belongs to who your record says it does.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
United States only.
Checked at request time.
Contacting US phone numbers is regulated, and the rules differ by line type and by consent. This source gives you the facts to comply; the obligation stays with you. Nothing here is legal advice.
- —US numbers only — for the rest of the world use Phone enrichment.
- —It is the most expensive source in the catalog at 100 points per number, so screen a list before you run it.
- —A clear litigation-risk flag is a signal, not legal advice or a compliance sign-off.
Questions, answered
Because United States rules on unsolicited contact differ between mobile and landline numbers. Knowing which you have before you dial is the point of running the check.
Related sources
Try phone enrichment us on your own data
One request format across every source in the catalog.