# Bulk Phone Number Validator - Format, Country & Type (`scrapesage/phone-validator`) Actor

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.

- **URL**: https://apify.com/scrapesage/phone-validator.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, Other, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.55 / 1,000 number validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Bulk Phone Number Validator - Format, Country & Type

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

```json
{
  "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](https://docs.apify.com/platform/integrations/mcp) - 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](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/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.

# Actor input Schema

## `phones` (type: `array`):

Phone numbers to validate, one per line. Numbers in international <code>+</code> form are validated as-is; numbers without a <code>+</code> use the <b>Default country</b> below. <b>Leave empty and the run returns a small free sample.</b>

## `phonesFromFile` (type: `string`):

Bulk-load numbers. Either <b>paste the whole list</b> (one per line or comma-separated), or give <b>a single link</b> to a public <code>.txt</code>/<code>.csv</code>, a Google Sheet/Drive link, or an Apify key-value-store record. Blank lines, <code>#</code> comments, quotes and extra CSV columns all parse. A file that cannot be read says so and charges nothing.

## `defaultCountry` (type: `string`):

The country to assume for numbers written WITHOUT a leading <code>+</code> (e.g. a national format like <code>415-555-2671</code>). Numbers already in <code>+</code> international form ignore this.

## `outputFields` (type: `array`):

Pick the fields you want and every record is trimmed to exactly those - handy for lean CSV/Sheets exports. Open the dropdown and tick, or type to filter (<code>valid</code>, <code>e164</code>, <code>type</code>).

## `maxItems` (type: `integer`):

Maximum numbers to validate in one run (after de-duplication).

## Actor input object example

```json
{
  "phones": [
    "+14155552671",
    "+442071838750"
  ],
  "defaultCountry": "",
  "maxItems": 10000
}
```

# Actor output Schema

## `results` (type: `string`):

Each scraped record - phone numbers validated and formatted - as a JSON item in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "phones": [
        "+14155552671",
        "+442071838750"
    ],
    "phonesFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/phone-validator").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "phones": [
        "+14155552671",
        "+442071838750",
    ],
    "phonesFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/phone-validator").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "phones": [
    "+14155552671",
    "+442071838750"
  ],
  "phonesFromFile": ""
}' |
apify call scrapesage/phone-validator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/phone-validator"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/T9cZh9yczyzEGL2NH/builds/Vr3NJpoBi0nqg3FcP/openapi.json