π Leads Scraper β $0.8/1k Leads β 250M+ Database β Like Apollo
Pricing
from $0.80 / 1,000 lead returneds
π Leads Scraper β $0.8/1k Leads β 250M+ Database β Like Apollo
Find Leads With Emails, LinkedIn URL, Phone Numbers, & More! Similar to Apollo, ZoomInfo, Lusha. 250+ Million Verified Database!
Pricing
from $0.80 / 1,000 lead returneds
Rating
3.7
(89)
Developer
Pipeline Labs
Maintained by CommunityActor stats
294
Bookmarked
10K
Total users
187
Monthly active users
5.1 hours
Issues response
17 hours ago
Last modified
Categories
Share
π B2B Lead Search - 250M+ Verified Contacts (Pay Per Lead)
A powerful alternative to Apollo, ZoomInfo, and Lusha, at a fraction of the cost. Search our database of 250M+ premium B2B contacts and get verified emails, LinkedIn profiles, phone numbers, and rich company data. Pay only for the leads you extract, no subscription.
85-90% email coverage. Pay per lead from $0.80/1,000 leads - less than the cost of a single seat on Apollo, ZoomInfo, or Lusha. Zero results = zero cost.
π€ Support: contact@radarleads.io
π What this actor does
Searches 250M+ cross-verified B2B contacts. Every record confirmed across 10+ independent data sources, continuously enriched and validated by AI agents, and updated daily. Returns verified emails, LinkedIn URLs, phone numbers where available, and rich company data ready for CRM or outreach.
Extract up to 50,000 leads per run on every plan.
Two ways to use it:
- Run it with your filters as input and get up to 50,000 leads per run, the best way to build bulk lists.
- Call it as a REST API for an instant response per request: search page by page, or find a work email or phone number from a LinkedIn profile URL. Ideal for AI agents, n8n/Make/Zapier and your own apps. Details below.
π― Preview before you run - no guessing
Unlike other actors where you set filters and hope for the best, Pipeline Labs gives you a live preview tool that shows exactly how many leads match your filters before you run anything.
1οΈβ£ Open the Lead Viewer and build your filters, see the live count update in real time.
2οΈβ£ Tweak until the count looks right.
3οΈβ£ Export the JSON from the viewer and paste it into the Actor input on the Source tab, or set your filters there directly.
π Performance
- β‘ V4 Database, freshly built and just released
- 250M+ premium B2B contacts
- 85-90% email coverage - validated for deliverability
- 10+ independent data sources - every record cross-verified before entering the database
- Continuously enriched and validated by AI agents, updated daily
- LinkedIn URLs for people and companies
- Phone numbers where available
- Up to 50,000 leads per run
- β‘ Lightning fast - 1,000 leads in ~8 seconds, 50,000 leads in ~5 minutes
- π₯ Permanent progress tracking - after each run your position is saved, so the next run with the same filters picks up exactly where you left off. No duplicates, no paying twice for the same leads. Reset anytime from the actor run settings if you want to start over. You're always in control.
- π Instant REST API: no run to start, responses in about a second. Your saved progress is shared between runs and API calls.
π΅ Pricing
| Plan | Price per 1,000 leads | Run limit |
|---|---|---|
| Free | $2.00 | 50,000 leads/run |
| Starter | $1.00 | 50,000 leads/run |
| Scale | $0.90 | 50,000 leads/run |
| Business | $0.80 | 50,000 leads/run |
Check your plan's exact rate at the top of the actor page.
REST API pricing: same per-lead rates, and you only pay when something is returned.
| Plan | Search, per 1,000 leads | LinkedIn β email, per 1,000 found | LinkedIn β phone, per 1,000 found |
|---|---|---|---|
| Free | $2.00 | $2.00 | $4.00 |
| Starter | $1.00 | $1.00 | $2.00 |
| Scale | $0.90 | $0.90 | $1.80 |
| Business | $0.80 | $0.80 | $1.60 |
No match = no charge. No actor start fee on API calls.
A cost-effective alternative to Apollo, ZoomInfo, and Lusha, all of which charge hundreds to thousands per month whether you use them or not.
β Pay only for leads extracted. Zero results = zero cost. β No subscription, no contracts, no commitments.
π§© Filters
| Category | Options |
|---|---|
| Job title | Includes / excludes (free text) |
| Seniority | c_suite, vp, director, manager, senior, entry, owner, partner |
| Function | engineering, sales, marketing, finance, operations, HR, IT, business_development |
| Has email, status (verified / unverified) | |
| Phone | Has phone |
| First / last name | Includes / excludes (free text) |
| Person location | Country, state, city (include / exclude) |
| Company name | Includes / excludes (free text), broad / phrase / exact matching |
| Company domain | Exact match or contains |
| Company industry | Includes / excludes |
| Company keywords | Includes / excludes (searches name + description) |
| Company audience | b2b, b2c, b2b_b2c |
| Company size | Preset ranges: 1-10 through 10,001+ |
| Custom company size min | Exact minimum employee count (e.g. 50) |
| Custom company size max | Exact maximum employee count (e.g. 500) |
| Company location | Country, state, city |
| Revenue | <$1M through >$1B |
| Funding stage | Seed through IPO / acquired |
| Technologies | Includes / excludes (2,100+ tech stack values) |
π Examples
Example 1: CEOs at mid-size US SaaS companies
{"personTitleIncludes": ["CEO", "Chief Executive Officer"],"personTitleExcludes": ["Assistant", "Deputy"],"seniorityIncludes": ["c_suite"],"hasEmail": true,"emailStatusIncludes": ["verified"],"personLocationCountryIncludes": ["United States"],"companyIndustryIncludes": ["computer software", "saas", "internet"],"companySizeIncludes": ["51-200", "201-500"],"annualRevenueIncludes": ["1m_10m", "10m_50m"],"fundingStageIncludes": ["series_a", "series_b"],"totalResults": 5000}
Example 2: All filters
{"totalResults": 10000,"personTitleIncludes": ["VP of Sales", "Head of Sales"],"personTitleExcludes": ["Assistant", "Intern"],"seniorityIncludes": ["vp", "director"],"seniorityExcludes": ["entry"],"functionIncludes": ["sales", "business_development"],"functionExcludes": ["support"],"roleMatchMode": "any","hasEmail": true,"emailStatusIncludes": ["verified"],"emailStatusExcludes": ["unverified"],"hasPhone": true,"personFirstNameIncludes": ["John"],"personFirstNameExcludes": ["Bob"],"personLastNameIncludes": ["Smith"],"personLastNameExcludes": ["Jones"],"personLocationCountryIncludes": ["United States", "Canada"],"personLocationCountryExcludes": ["Mexico"],"personLocationStateIncludes": ["California", "New York"],"personLocationStateExcludes": ["Texas"],"personLocationCityIncludes": ["San Francisco", "New York City"],"personLocationCityExcludes": ["Los Angeles"],"companyNameIncludes": ["Acme"],"companyNameExcludes": ["Google", "Microsoft"],"companyNameMatchMode": "broad","companyDomainIncludes": ["acme.com"],"companyDomainExcludes": ["google.com"],"companyDomainMatchMode": "strict","companyIndustryIncludes": ["computer software", "saas"],"companyIndustryExcludes": ["staffing and recruiting"],"companyKeywordIncludes": ["cloud", "saas"],"companyKeywordExcludes": ["agency", "consulting"],"companyKeywordMode": "broad","companyMatchMode": "any","companySizeIncludes": ["51-200", "201-500", "501-1000"],"companySizeExcludes": ["1-10"],"companyEmployeeMin": 50,"companyEmployeeMax": 500,"companyLocationCountryIncludes": ["United States"],"companyLocationCountryExcludes": ["India"],"companyLocationStateIncludes": ["California"],"companyLocationStateExcludes": ["Florida"],"companyLocationCityIncludes": ["San Francisco"],"companyLocationCityExcludes": ["Los Angeles"],"annualRevenueIncludes": ["1m_10m", "10m_50m"],"annualRevenueExcludes": ["lt_1m"],"fundingStageIncludes": ["series_a", "series_b"],"fundingStageExcludes": ["seed"],"technologiesIncludes": ["Salesforce", "HubSpot"],"technologiesExcludes": ["WordPress"],"resetProgress": false,"dontSaveProgress": false,"customOffset": 0}
β‘ Call it as a REST API
Prefer an instant HTTP response instead of a run? This actor can also be called as a REST API: no run to start, no waiting for a container, one response per request. It's ideal for AI agents, n8n/Make/Zapier flows and your own apps. The full endpoint reference and your API URL are on the Endpoints tab. Authenticate with your Apify API token: Authorization: Bearer YOUR_APIFY_TOKEN.
| Endpoint | What it does | You pay for |
|---|---|---|
POST /search | Same filters as the input above, one page (up to 100 leads) per request | 1 lead per lead returned |
POST /linkedin/email | LinkedIn profile URL β work email | 1 lead, only when an email is found |
POST /linkedin/phone | LinkedIn profile URL β phone number | 2 leads, only when a phone is found |
Billed at your plan's normal price per 1,000 leads; see REST API pricing above.
Search, page by page. Send the filters as JSON, plus pageSize. Just like a normal run, your progress is saved: send the same request again and you get the next page, with no duplicates. Progress is shared with your runs of this actor, so you can mix both.
POST /search{ "personTitleIncludes": ["VP of Sales"], "personLocationCountryIncludes": ["United States"], "hasEmail": true, "pageSize": 25 }β { "total": 18234, "count": 25, "offset": 0, "nextOffset": 25, "remaining": 18209, "results": [ ... ] }
The run options work the same way as in a normal run:
| Option | What it does |
|---|---|
customOffset | Jump to a position, e.g. 5000 |
resetProgress: true | Start this search again from 0 (or from customOffset) |
dontSaveProgress: true | A one-off page that doesn't read or move your saved position |
searchAfter | Prefer to hold the cursor yourself? Send back the searchAfter from the previous response; nothing is saved |
If a response is ever lost, send resetProgress: true with customOffset set to the nextOffset of the last response you did receive, and you'll get the missing page again.
Find an email or phone from LinkedIn.
POST /linkedin/email{ "linkedinUrl": "https://www.linkedin.com/in/jane-doe" }β { "found": true, "result": { "linkedinUrl": "linkedin.com/in/jane-doe", "fullName": "Jane Doe", "email": "jane@acme.com", "emailStatus": "deliverable" } }
No match returns { "found": false, "result": null } and isn't charged. For bulk lists of thousands of leads, a normal run is cheaper per lead.
π Best Practices
- Always preview first. Use the Lead Viewer to check your filter count before running - it's free and takes seconds.
- Start broad, then narrow. Begin with title + country, then add industry or company size.
- Use excludes to cut noise.
personTitleExcludesandcompanyIndustryExcludesare powerful for precision targeting. - Zero results? Broaden your location, remove a filter, or check for typos in domain/title.
- Too many results? Add funding stage, revenue range, tech stack filter, or narrow to state/city.
- Custom employee range? Use
companyEmployeeMin/companyEmployeeMaxfor exact headcount targeting,companySizeIncludesfor preset buckets, or combine both. - Get the exact right JSON values: for fields with dropdowns (seniority, revenue, funding stage, technologies, etc.) the exact values must match what the backend expects. The easiest way: build your filters in the Lead Viewer, then export the JSON directly - it will have all the correct values pre-filled.
π€ Support
Email us at contact@radarleads.io - we respond fast and fix issues promptly.
We have a dedicated support and development team constantly improving the actor. Got feedback or a feature request? We want to hear it. Your input directly shapes what we build next.
β οΈ Disclaimer
Use for B2B prospecting only. Comply with all applicable laws including GDPR, CCPA, and CAN-SPAM.