Wiza alternative: U.S. emails and mobiles as one free file, and the LinkedIn profile behind a URL at $1.25 per 1,000

Billed monthly, an email past the plan's is $0.15: $150.00 per 1,000, and a phone number $350.00 per 1,000. Billed yearly, reveals are unlimited one at a time, but a list (a Sales Navigator search or list, a Recruiter project, a Wiza Prospect list or a CSV upload) has a hard cap of 2,500 export credits a month, one a person whether an email is found or not, says its help center. That's 30,000 people a year, $33.00 per 1,000 on Email and $66.33 on Email + Phone if every month's exports are used.

Wiza's API takes a LinkedIn URL and, with "enrichment_level": "none", returns the profile and its company without an email or a phone, for 1 credit when the URL is matched. One-off credits are $0.025 each, says its help center, so a profile is $25.00 per 1,000, whatever the amount; larger plans with volume discounts are by a sales call. Through Datacircle: $1.25 per 1,000 through Up2Data (a profile it can't find is free), $3.70 per 1,000 through HarvestAPI. Up2Data takes $1 a day per account (800 profiles), with a shared daily limit for all customers, then answers 429 until 00:00 UTC; HarvestAPI has no daily limit.

Datacircle at its least: Up2Data for 800 profiles a day, 24,000 in a 30-day month, and HarvestAPI past them. Wiza's API docs say its credits are valid 12 months; Datacircle's funds never expire.

On Wiza, a profile is two calls, as its API docs give them: start the reveal, then fetch it, about 5 seconds later on average.

# 1. Start the reveal: profile only, no email or phone
curl -X POST "https://wiza.co/api/individual_reveals" \
  -H "Authorization: Bearer $WIZA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"individual_reveal": {"profile_url": "https://www.linkedin.com/in/williamhgates"}, "enrichment_level": "none"}'

# 2. Fetch it with the id the first call returned (or take it on a webhook)
curl "https://wiza.co/api/individual_reveals/$ID" -H "Authorization: Bearer $WIZA_API_KEY"

Through Datacircle, it's Up2Data's own request with your Datacircle key, and the profile comes back in the answer:

curl -X POST "https://api.datacircle.dev/v1/profiles/enrich" \
  -H "Authorization: Token $DATACIRCLE_API_KEY" \
  -H "X-Data-Provider: up2data" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.linkedin.com/in/williamhgates"}'

Up2Data answers its own JSON for the profile at that URL, under data: name, headline, location, current company, the full job history, education and skills. Every field: LinkedIn Profile API in the docs. A whole CSV of URLs: with Python or with Node.js. Wiza's key also works inside Clay and n8n; so does ours: from a Clay table, in an n8n workflow.

The list Wiza exports from a Sales Navigator search, for people in the U.S., is one query on the file. Unzip it into us_10m/ and pip install duckdb:

import duckdb

duckdb.sql("create view people as select * from 'us_10m/us_smb_mid_market_persons.parquet'")
duckdb.sql("create view companies as select * from 'us_10m/us_smb_mid_market_companies.parquet'")

# A LinkedIn URL as the file writes it: the part after /in/, decoded and lowercased, so http, no www, a trailing slash or ?utm_source match
duckdb.sql(r"create macro profile(url) as lower(url_decode(regexp_extract(url, 'linkedin\.com/in/([^/?#]+)', 1)))")

# Sales leaders at U.S. companies of 51 to 200 employees, with a mobile phone or an email, to a CSV
duckdb.sql(r"""
  copy (
    select p.FULL_NAME, p.CURRENT_JOB_TITLE, c.NAME as COMPANY, c.LINKEDIN_INDUSTRY, p.CITY, p.STATE_CODE,
           p.MOBILE_PHONE, p.EMAIL, p.LINKEDIN_URL
    from people p
    join companies c on c.LINKEDIN_ID = p.CURRENT_JOB_COMPANY_LINKEDIN_ID
    where regexp_matches(p.CURRENT_JOB_TITLE, '\b(vp|vice president|head|director) of sales\b', 'i')
      and not regexp_matches(p.CURRENT_JOB_TITLE, '\bassistant\b.*\b(to|for)\b|\bexecutive assistant\b', 'i')  -- not their assistants
      and c.EMPLOYEE_COUNT_RANGE = '51-200'
      and (p.MOBILE_PHONE is not null or p.EMAIL is not null)
  ) to 'sales_leaders_51_200.csv'
""")

It ran on a laptop in 0.2 s. On Wiza's yearly plans, those 9,027 people are 4 months of list exports (2,500 a month), and a Sales Navigator search shows 2,500 leads at most (Sales Navigator alternative). Change the titles, c.EMPLOYEE_COUNT_RANGE or add p.STATE_CODE = 'TX' for your own market. Lists by job title, counted state by state: email lists by title.

Wiza's CSV upload takes a list of LinkedIn URLs and spends a credit for each email, phone or person. With the same setup, the file does the whole list in one join. Put your URLs in linkedin_urls.csv under a url header:

# Your LinkedIn URLs, one per row of linkedin_urls.csv under a "url" header, with each one's email and mobile from the file
duckdb.sql("""
  copy (
    select u.url, p.FULL_NAME, p.CURRENT_JOB_TITLE, c.NAME as COMPANY, p.EMAIL, p.MOBILE_PHONE, p.CITY, p.STATE_CODE
    from read_csv('linkedin_urls.csv') u
    left join people p on profile(p.LINKEDIN_URL) = profile(u.url)
    left join companies c on c.LINKEDIN_ID = p.CURRENT_JOB_COMPANY_LINKEDIN_ID
  ) to 'linkedin_urls_with_contacts.csv'
""")

We tested this query on 1,070 URLs: 1,020 people of the October 2026 file, each URL written one of the ways people paste them, were all found, and 50 made-up ones weren't (the numbers: ContactOut alternative). About half the people found have a contact, as across the whole file: 5,182,067 of 9,521,154 (54%). A URL the file doesn't hold comes back blank: someone outside the U.S., at a company of fewer than 11 or more than 500 employees, or not in the October release.

• Lookups of any LinkedIn profile, not only people in the U.S., personal emails included, up to 3 phone numbers a person.
• Each email checked at the moment you reveal it, and charged only when valid.
• A Chrome extension on LinkedIn, Sales Navigator and Recruiter, its own search (Wiza Prospect), AI Research and CRM integrations.
• An API that finds emails and phones too, and searches people and companies with filters.

Datacircle sells data, not a prospecting tool: the file is an October 2026 snapshot of people at U.S. companies of 11 to 500 employees, with work emails only, and the API returns the LinkedIn profile behind a URL. For anyone outside the file, or a personal email, Wiza's lookup is the one to use.

• The live profile behind each URL, title and experience as they are today: the LinkedIn profile API, at $0.00125 a profile found; every API's price per 1,000: LinkedIn profile API pricing compared.
• The same file next to other tools' contacts: ContactOut alternative, Lusha alternative, RocketReach alternative; what each tool's free plan gives: free B2B database.

The free file is on your dashboard once you sign up with your work email, with the $5 credit and your API key.