US Phone Number Validator & Reverse Lookup — Carrier & Owner
Pricing
from $100.00 / 1,000 results
US Phone Number Validator & Reverse Lookup — Carrier & Owner
Validate any US phone number and enrich it with carrier, line type (mobile / landline / VoIP), prepaid status and the people or businesses linked to it — names, age range, addresses and industry. Pay only for a valid, enriched result; invalid numbers are free.
Pricing
from $100.00 / 1,000 results
Rating
5.0
(1)
Developer
NeuralVerge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
US Phone Number Validator & Reverse Lookup — Carrier & Owner ✅ No API Key
Validate any US phone number and enrich it with carrier, line type, prepaid status and the people or businesses linked to it — names, age range, addresses and industry. Powered by the Neuralverge API. No API key or account required, and you only pay for a valid, enriched result.
Ideal for lead validation, TCPA / line-type screening, identity resolution, fraud checks and CRM hydration.
✨ Why this Actor
- ☎️ Validate + enrich in one call — confirm a US number is real and get its carrier, line type (mobile / landline / VoIP) and prepaid flag.
- 👤 Reverse lookup — resolve the number to the linked people and businesses, with names, age range, gender, addresses and industry.
- 💸 Pay only for valid results — invalid numbers are never billed. No empty, billable rows.
- 🔑 No API key or account — enrichment runs on the Neuralverge backend.
- ⚡ Real-time & structured — fresh data each run, ready for a spreadsheet, CRM or AI pipeline.
🔧 How it works
- Provide a US phone number — any format works (the Actor strips
+, spaces, dashes and parentheses and sends digits only; the leading1country code is optional). - Run the Actor. Validation and enrichment happen on the Neuralverge backend.
- Get one dataset row per validated number — the source
phoneand the structuredmachineobject. Export to CSV, JSON or Excel, or pull it over the Apify API.
If the number is invalid or returns no result, it's logged and skipped without charge.
Input
One number per run.
| Field | Type | Notes |
|---|---|---|
phone | string | The US phone number to validate and enrich. Any format; digits are extracted automatically. Leading 1 is optional. |
{"phone": "19165058708"}
What you'll receive
Each dataset row mirrors the Neuralverge system output and has two top-level blocks:
phone— the digits-only number you submitted.machine— the structured result:phone_number(E.164),is_valid,line_type,carrier,is_prepaid,country_calling_code,activity_score,is_litigator_risk, and anownersarray. Each owner carriesname,type(Person / Business),firstname/middlename/lastname,alternate_names,age_range,gender,industry,link_to_phone_start_dateandcurrent_addresses(street, city, state, postal code, country).
Nulls & empty values are normal. Only fields that resolve for the number are filled — e.g.
activity_score,is_litigator_riskand some owner fields are oftennull, and a number may have zero, one or several owners.
Example output (real run)
A real dataset row for a US phone lookup, shown in full — the structured
machine-readable result (machine). The human markdown summary is produced by the
system but omitted from the dataset.
{"phone": "9165058708","machine": {"id": "Phone.88b010e6-d1a7-4f0b-8ffe-e41aac0eab6d","phone_number": "+19165058708","is_valid": true,"activity_score": null,"country_calling_code": "1","country_code": null,"country_name": null,"line_type": "Mobile","carrier": "T-Mobile USA, Inc.","is_prepaid": false,"is_litigator_risk": null,"owners": [{"id": "Person.29d3ffb8-b9d9-3937-b1bb-137b6b95acf7","name": "Stephen M Sewell","firstname": "Stephen","middlename": "M","lastname": "Sewell","alternate_names": ["Steve M Sewell","S M Sewell"],"age_range": "36-40","gender": "M","type": "Person","link_to_phone_start_date": "2004-03-26","industry": [],"current_addresses": [{"id": "Location.5290fe2a-6ee5-4120-9de6-7b95244a3c4f","location_type": "Address","street_line_1": "585 29th St Apt C","street_line_2": null,"city": "San Francisco","postal_code": "94131","zip4": "2240","state_code": "CA","country_code": "US","delivery_point": "MultiUnit","link_to_person_start_date": "2021-03-01"}]},{"id": "Business.4dc14931-dd9b-397f-b084-cb3e4e748e28","name": "Builder.io, Inc","firstname": null,"middlename": null,"lastname": null,"alternate_names": [],"age_range": null,"gender": null,"type": "Business","link_to_phone_start_date": null,"industry": ["Data Processing, Hosting, & Related Services"],"current_addresses": [{"id": "Location.7a4b3bb1-d40e-4d1a-8c57-04752c0f9031","location_type": "Address","street_line_1": "95 3rd St PMB 2 San Fr","street_line_2": null,"city": "San Francisco","postal_code": "94103","zip4": "3103","state_code": "CA","country_code": "US","delivery_point": "SingleUnit","link_to_person_start_date": null}]}],"warnings": [],"error": null}}
Genuine output from a live run — the number validated as a T-Mobile mobile line and resolved to a linked person and business with addresses.
Pricing
Pay per result — $0.10 per validated number ($100 per 1,000) returned to the dataset. You pay only for rows returned — invalid numbers are free.
| Event | Price |
|---|---|
| Actor start | Free |
| Validated number returned (per dataset row) | $0.10 |
Numbers that are invalid or return no result are not billed. Pricing is on top of your Apify platform usage.
Integrations & API
Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.
FAQ
Do I need an account or API key? No. Validation and enrichment run on the Neuralverge backend.
Which numbers are supported? US phone numbers. Any format — the Actor strips +, spaces,
dashes and parentheses and sends digits only. The leading 1 country code is optional.
What line types can it detect? Mobile, landline and VoIP, along with the carrier and prepaid status.
Am I charged if a number is invalid? No. You're billed only for valid numbers returned to the dataset.
Disclaimer: This Actor is an independent tool. Use enriched personal data in compliance with applicable privacy laws (e.g. TCPA, CCPA, GDPR) and only where you have a lawful basis.