# PhoneInfoga Phone Number Scraper - OSINT & Validation (`scrapesage/phoneinfoga-scraper`) Actor

Analyse phone numbers like PhoneInfoga: validate, format (E.164, international, national), detect country and line type, and generate OSINT footprint URLs (Google dorks, social, reputation, reverse lookup). Optional carrier enrichment via your numverify key. Export JSON, CSV, Excel.

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

## Pricing

from $4.40 / 1,000 phone number analyseds

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/actors/running/actors-in-store.md#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

## PhoneInfoga Phone Number Scraper - OSINT & Validation

> **Disclaimer:** This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the PhoneInfoga open-source project. All trademarks mentioned are the property of their respective owners. "PhoneInfoga" is referenced only to describe the kind of check this Actor performs.

Analyse phone numbers the way **PhoneInfoga** does: **validate** and **format** them, detect the **country** and **line type**, and get a ready-made set of **OSINT footprint URLs** for reconnaissance. Feed one number or thousands.

The core needs **no API key** - parsing, validation, formatting and footprint generation run offline. Add your own **numverify** key for carrier/location enrichment.

### What it does

- **Validates** each number and reports whether it is valid / possible.
- **Formats** it four ways: E.164 (`+14155552671`), international, national, and RFC 3966.
- Detects **country**, **calling code**, and **line type** (mobile, fixed line, toll-free, VoIP, ...).
- Builds **OSINT footprint URLs** - Google dorks, social-network searches, reputation/spam-check sites, reverse-lookup services, and messaging (WhatsApp/Telegram) links for the number.
- Optional **carrier / line-type / location** enrichment when you supply a **numverify** API key.

### Example output

```json
{
  "type": "phone",
  "input": "+14155552671",
  "valid": true,
  "e164": "+14155552671",
  "international": "+1 415 555 2671",
  "national": "(415) 555-2671",
  "countryCode": "US",
  "countryName": "United States",
  "countryCallingCode": "+1",
  "numberType": "FIXED_LINE_OR_MOBILE",
  "footprintUrls": [
    { "kind": "google", "name": "Google exact (E.164)", "url": "https://www.google.com/search?q=%22%2B14155552671%22" },
    { "kind": "social", "name": "Facebook search", "url": "https://www.facebook.com/search/top?q=%2B14155552671" },
    { "kind": "reputation", "name": "Truecaller", "url": "https://www.truecaller.com/search/us/4155552671" }
  ]
}
```

### Input

| Field | Description |
|---|---|
| **Phone numbers** | Numbers to analyse (E.164 preferred; up to 5,000). |
| **Default country** | Assumed country for local-format numbers without a `+` code. |
| **Include OSINT footprint URLs** | Generate recon search URLs for each number (on by default). |
| **numverify API key** | Optional - your own key to add carrier, line type and location. |

### Use cases

- **OSINT & fraud investigation** - fingerprint a number and get every recon lead in one place.
- **Lead validation & enrichment** - check that phone numbers are valid and mobile before outreach.
- **Data cleaning** - normalise messy numbers to E.164 with the country resolved.

### Notes

The footprint URLs are **constructed search links** - the Actor does not scrape those third-party sites, so the core runs fast and key-free. Carrier/line-type/location fields appear only when you provide a numverify key. `numberType` comes from the libphonenumber metadata and may read `FIXED_LINE_OR_MOBILE` where a country's ranges overlap.

### Run it from an agent (MCP / API)

Agent-ready: typed input schema, structured JSON output. An agent or automation can call this Actor to validate, normalise and fingerprint a phone number in one step. Pass `phoneNumbers` and read the `phone` records back.

### 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.

### How much does it cost?

This Actor uses Apify's **pay-per-event** pricing: you are charged only for the results it delivers, with no monthly rental and no start fee. The events it can charge are:

- **Phone number analysed** - One phone number analysed: validation, formats, country, line type and OSINT footprint URLs

The current price of each event is shown on the **Pricing** tab of this page. Set a maximum total charge on the run if you want a hard cap on spend, and use the input limits to control how much the Actor fetches.

### Automate & schedule

Run this Actor on autopilot and pull results into your own stack:

- **[Apify API](https://docs.apify.com/api/v2)** - start runs, fetch datasets and manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** - official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** - run it hourly, daily or weekly and keep your dataset current.
- **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** - trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

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

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/phoneinfoga-scraper').call({
    // your input - see the Input section above
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);
```

### Integrate with any app

Connect the dataset to thousands of apps - no code required:

- **[Make](https://docs.apify.com/platform/integrations/make)** - multi-step automation scenarios.
- **[Zapier](https://docs.apify.com/platform/integrations/zapier)** - push new records straight into your CRM or spreadsheet.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** - get notified when a scheduled run finds something new.
- **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** - auto-export every run to a spreadsheet.
- **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** - pipe results into your data warehouse.
- **[GitHub](https://docs.apify.com/platform/integrations/github)** - trigger runs from commits or releases.

### FAQ

**Do I need an API key?** No for the core (validation, formatting, country, line type, footprint). Yes only for carrier/location, via your own numverify key.
**Is analysing a phone number legal?** The Actor formats/validates numbers and builds public search links. You are responsible for how you use the results, in line with applicable law.

### Data & lawful use

You supply the input (phone numbers); the Actor only checks or enriches what you give it against publicly available sources. Make sure you collected that input lawfully and have a lawful basis to process it. This is a verification and open-source-intelligence tool for security research, fraud prevention and checking identifiers you are authorised to check. Do not use it to locate, track, profile or harass individuals, and follow the anti-spam and telemarketing rules that apply to you (for example GDPR and PECR in the EU and UK, CAN-SPAM and the TCPA in the US, CASL in Canada). Honour opt-outs and deletion requests.

Under [Apify's Standard Actor Contract](https://docs.apify.com/legal/standard-actor-contract), which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.

### Disclaimer

**This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the PhoneInfoga open-source project. All trademarks mentioned are the property of their respective owners.**

"PhoneInfoga" is referenced only in a descriptive, nominative sense - to describe the kind of check this Actor performs. This Actor is an independent implementation, is not an official PhoneInfoga product and is not authorised or certified by the PhoneInfoga open-source project. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws and regulations.

### Need help?

Open an issue on the Actor's **Issues** tab, or visit the [Apify help center](https://help.apify.com/). Feature requests are welcome - this Actor is actively maintained.

# Actor input Schema

## `phoneNumbers` (type: `array`):

Phone numbers to analyse. Use E.164 form (<code>+14155552671</code>) for best results, or local form with a Default country set. Up to 5,000 per run.

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

Country to assume when a number has no <code>+</code> country code. Ignored for E.164 numbers.

## `includeFootprint` (type: `boolean`):

Generate reconnaissance search URLs (Google dorks, social, reputation, reverse-lookup, messaging) for each number.

## `numverifyApiKey` (type: `string`):

Your own numverify (apilayer) API key to enrich each number with carrier, line type and location. Leave blank to skip - the core analysis and footprint need no key.

## `proxyConfiguration` (type: `object`):

Only used for optional numverify enrichment.

## Actor input object example

```json
{
  "phoneNumbers": [
    "+14155552671"
  ],
  "defaultCountry": "",
  "includeFootprint": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All analysed phone records as JSON items 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 = {
    "phoneNumbers": [
        "+14155552671"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/phoneinfoga-scraper").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 = {
    "phoneNumbers": ["+14155552671"],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/phoneinfoga-scraper").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 '{
  "phoneNumbers": [
    "+14155552671"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call scrapesage/phoneinfoga-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/1S8fRGQrwu9gXdmJE/builds/flMehgk8BttWeFPft/openapi.json