The Anyphone Scraper finds publicly accessible mobile phone numbers for leads by scouring the web and validating through multiple sources. Designed for lead generation and contact enrichment workflows, it helps you build contact lists with phone numbers for leads based on name, email or LinkedIn profile data.
Created by Bitbash, built to showcase our approach to Scraping and Automation!
If you are looking for Anyphone Scraper you've just found your team — Let's Chat. 👆👆
Anyphone uses AI-orchestrated web scraping to search public sources for phone numbers associated with provided leads. It merges results across sources, validates numbers, and returns a structured dataset — letting you skip manual, time-consuming searches and focus on outreach, CRM enrichment or lead analysis.
- Automatically finds phone numbers for leads (name, email, LinkedIn URL).
- Works across multiple public sources for better coverage and validation.
- Saves time compared to manual lookup or guesswork.
- Outputs structured contact data ready for CRM import or analytics.
| Feature | Description |
|---|---|
| Multi-Source Search | Scours public web sources to locate available mobile numbers. |
| AI-Driven Matching & Validation | Uses AI orchestration and heuristics to improve match accuracy and detect mobile lines. |
| Lead-Based Input Handling | Accepts leads with name, email, and/or LinkedIn URL; works with CSV upload or JSON input. |
| Contact Data Output | Returns phone numbers, their confidence score, source list and marks primary number. |
| Region & Proxy Support | Supports regional phone-format validation and optional proxy configuration for scraping. |
| API & SDK Access | Can be used through CLI, HTTP API, or via Apify client libraries (Python/JS). |
| Field Name | Field Description |
|---|---|
| name | Lead’s full name. |
| Lead’s email address (if provided). | |
| linkedin_url | Lead’s LinkedIn profile URL (if provided). |
| phone_numbers | Array of found phone numbers with metadata (number, confidence, source, is_mobile flag). |
| primary_number | The best-matched phone number (if found). |
| confidence | Confidence score of the match (e.g. 0.85) indicating reliability. |
| sources | List of sources where the number was found (e.g. “linkedin”, “google_search”). |
[
{
"name": "John Doe",
"email": "john@example.com",
"linkedin_url": "https://www.linkedin.com/in/johndoe",
"phone_numbers": [
{
"number": "+15551234567",
"confidence": 0.85,
"sources": ["linkedin", "google_search"],
"is_mobile": true
}
],
"primary_number": "+15551234567",
"confidence": 0.85,
"sources": ["linkedin", "google_search"]
}
]
anyphone-scraper/
├── src/
│ ├── main.js
│ ├── search_engine/
│ │ ├── scraper.js
│ │ ├── validator.js
│ │ └── ai_matcher.js
│ ├── utils/
│ │ ├── proxy_config.js
│ │ ├── phone_formatter.js
│ │ └── logger.js
│ ├── config/
│ │ └── input_schema.json
├── package.json
└── README.md
- Sales/BD teams enrich lead lists with valid phone numbers for outreach.
- Recruiters/Staffing agencies discover contact numbers for candidate databases.
- Marketing teams build contact-rich lists for campaigns.
- Freelancers / Agencies enhancing CRM records for clients with verified contact info.
- Data-driven tools automating contact enrichment workflows for lead generation.
What inputs are supported?
Name + email + LinkedIn profile URL. CSV upload also supported.
Does it only find mobile phone numbers?
It attempts to find mobile phone numbers and marks is_mobile: true when possible; quality depends on public availability.
Is data collection ethical and compliant?
Yes — only publicly available data is used; tool advises compliance with GDPR, CCPA and site terms. :contentReference[oaicite:0]{index=0}
What is the confidence score?
A heuristic score indicating how likely the matched phone number corresponds to the lead; used to pick a primary number.
Which formats does output come in?
JSON by default, but usable via Apify API; export into CSV/Excel possible via downstream processing.
Primary Metric:
About 30–60 seconds per lead search (varies by depth and number of sources). :contentReference[oaicite:1]{index=1}
Reliability Metric:
Claims ≥85% validity for returned mobile numbers. :contentReference[oaicite:2]{index=2}
Coverage Metric:
Targets ≥70% of leads to get at least one phone number (if publicly available). :contentReference[oaicite:3]{index=3}
Quality Metric:
Provides structured phone number data with metadata — ready for CRM/lead-gen workflows with minimal cleanup.
