Bulk Phone Number Validator - Format, Country & Type
Pricing
from $0.55 / 1,000 number validateds
Bulk Phone Number Validator - Format, Country & Type
Validate a list of phone numbers with Google libphonenumber: valid and possible, country and calling code, mobile or landline, plus E.164 / international / national formatting. Local, no anti-bot, cents per number.
Pricing
from $0.55 / 1,000 number validateds
Rating
0.0
(0)
Developer
Scrape Sage
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Clean a list of phone numbers before you dial or store them. For each number you get whether it is valid and possible, the country and calling code, the line type (mobile / fixed line), and the number reformatted to E.164, international and national styles - powered by Google's libphonenumber, the same engine Android uses.
Runs locally with no network calls and no anti-bot target, so it is fast and costs a fraction of a cent per number.
What each field means (honest about the limits)
| Field | Meaning |
|---|---|
valid | Passes libphonenumber's full validation for its country (length + prefix rules) |
possible | Has a plausible length for its country (a lighter check than valid) |
country / countryCallingCode | ISO country (e.g. US) and calling code (+1) |
lineType / isMobile / isFixedLine | MOBILE, FIXED_LINE, VOIP, TOLL_FREE, … where the country's metadata allows |
e164 / international / national | The number reformatted - +14155552671, +1 415 555 2671, (415) 555-2671 |
uri | tel: RFC-3966 URI |
This is format + metadata validation, not a live carrier lookup. It confirms a number is well-formed and assignable for its country and gives its likely type - it does not ping the carrier to confirm the line is active or reachable (that needs a paid HLR/carrier-lookup API). That is exactly what you need to clean and normalise a list before sending it anywhere.
Input
{"phones": ["+14155552671", "415-555-2671", "+442071838750"],"defaultCountry": "US"}
- Phone numbers - one per line.
+international numbers validate as-is; national-format numbers use the Default country. - Import from a file - paste a whole list, or link a public
.txt/.csv, a Google Sheet/Drive link, or an Apify key-value-store record. - Default country - the country to assume for numbers written without a
+. - Output fields - tick only the columns you need for a lean export.
Use with AI assistants (MCP)
Available through the Apify MCP server - an agent can validate and normalise a batch of numbers to E.164 before writing them to a CRM or sending messages.
Agent-ready: autonomous payments (x402 & Skyfire)
This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:
- x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
- Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.
Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.