LinkedIn Profile Finder by Name & Company (No Cookies)

LinkedIn Profile Finder by Name & Company ✅ No Cookies

Find a LinkedIn profile from a full name + company or domain — no profile URL needed. Returns the best-matching person with headline, company and LinkedIn URL. Powered by the Neuralverge API. No cookies or account required, and you pay per completed lookup — matched or not; failed runs are never charged.

Ideal for sales prospecting, recruiting and lead enrichment when all you have is a name and where the person works.

✨ Why this Actor

• 🔎 No URL needed — start from a name + company/domain and get the LinkedIn profile.
• ✅ Verified match, or an honest no result — the profile that comes back is checked against the name you asked for. If the search lands on a different person at that company, that stranger is never stored as your match: you get a no result row saying the name did not match, so you are never billed for the wrong person's profile.
• 💸 Simple, predictable billing — starting the Actor is free and a failed run costs $0.00. A lookup that ran is billed as one profile, matched or not.
• 🍪 No cookies, login or account — never share LinkedIn credentials or risk account restrictions. Everything runs on the Neuralverge backend.
• ⚡ Real-time & structured — fresh data each run, ready for a spreadsheet, CRM or AI pipeline.

🔧 How it works

1. Provide a full name and a company name or domain (e.g. Bill Gates + Gates Foundation, or openai.com).
2. Run the Actor. The search and match happen on the Neuralverge backend.
3. Get one flat dataset row per lookup — 11 columns, all at the top level (company_or_domain, full_name, name, headline, linkedin_url, …). Export to CSV, JSON or Excel, or pull it over the Apify API.

If nothing matches — or the search returns someone who is not the person you asked for — the log names the rejected candidate and you get one no result row that echoes your query, billed like any other row.

Input

One lookup per run.

Field	Type	Notes
companyOrDomain	string	Company name or domain, e.g. Gates Foundation or openai.com.
fullName	string	The person's full name, e.g. Bill Gates.

{
  "companyOrDomain": "Gates Foundation",
  "fullName": "Bill Gates"
}

What you'll receive

One flat row per lookup. Every field sits at the top level of the row, so the Output tab shows a single table with all 11 columns — there are no nested objects and no views to switch between. Exports (CSV, JSON, XML, Excel) contain exactly the same fields. The profile columns are filled in only when the match is verified — see "How matching works" below.

• company_or_domain and full_name — the lookup inputs you submitted.
• name, headline, company, location, linkedin_url, public_identifier, source_query, scraped_at — the matched profile, as flat columns ready for a spreadsheet or CRM.
• total_candidates — how many candidates the underlying search returned before verification.

Nulls are normal. The column set is the same on every run, so a field the source does not expose for this lookup comes back null rather than disappearing — a spreadsheet or CRM mapping built on one run keeps working on the next.

How matching works

The underlying lookup is a site-restricted search, and a search will happily return somebody at the company even when the person you asked for is not there. So the returned name is compared against the requested one before anything is stored:

• accents and punctuation are ignored — Jan Curn matches Jan Čurn;
• shortened first names and initials are accepted — Nikolay Storonsky matches Nik Storonsky, Ryan Roslansky matches Ryan R.;
• extra middle names are fine — John Smith matches John Andrew Smith;
• a genuinely different person is rejected — asking for Dario Amodei and getting Daniela Amodei returns a no result row instead of the wrong profile.

When a candidate is rejected the log names it, so you can see what the source found. You never get billed for a stranger's profile — you get a row that says the name did not match, and that row is billed like any other (see Pricing).

This is a lightweight search match, not a full profile. It returns the LinkedIn URL and headline, but not experience, education or email. To get the full profile or a work email, feed the returned linkedin_url into the LinkedIn Profile or LinkedIn Email actor.

When nothing is found

A lookup that runs but matches nothing — or that rejects the candidate the source returned — still returns a row, so a batch never silently loses an input:

Column	Value
company_or_domain, full_name	echoed back exactly as submitted
found	false
message	why nothing was returned (no candidate, or the name did not match)

Filter these out with found != false (or drop rows where message is set). This row is billed as one result — see Pricing.

Example output (real run)

A real dataset row for Bill Gates @ Gates Foundation, shown in full.

{
  "company_or_domain": "Gates Foundation",
  "full_name": "Bill Gates",
  "name": "Bill Gates",
  "headline": "Chair, Gates Foundation and Founder ...",
  "company": "Gates Foundation",
  "location": null,
  "linkedin_url": "https://www.linkedin.com/in/williamhgates",
  "public_identifier": "williamhgates",
  "source_query": "site:linkedin.com/in \"Gates Foundation\" Bill Gates",
  "scraped_at": "2026-07-21T19:21:07.640Z",
  "total_candidates": 2
}

Genuine output from a live run — the search returned two candidates and resolved the top match to https://www.linkedin.com/in/williamhgates.

Pricing

Pay per event — $0.010 per profile ($10 per 1,000) written to the dataset. There is no run fee and no start fee.

Event	Price	Charged
Actor start	free	never
Failed run — invalid input, API error, timeout	free	never
Row written to the dataset	$0.010 ($10 / 1,000)	every row, including the "no result" row

A completed lookup is billed as one profile, matched or not. When the source returns nothing, the Actor writes one explicit no-result row — the query you submitted plus found: false and a message explaining it — and that row is charged at the normal per-profile price. A run that fails (missing input, bad key, upstream error) writes no row and costs $0.00.

Pricing is on top of your Apify platform usage.

Rate limit

There is a ceiling on how fast one Apify account can pull from the Neuralverge backend: 10 requests per second for this Actor, counted separately from the other Neuralverge Actors. One run is normally one request, so this is about how many runs you start at once, not about the size of a single run — at typical run times that is dozens of runs in flight at once, which is well above ordinary use.

Updated August 2026: this ceiling was doubled from 5 to 10 requests per second. Bulk jobs that used to hit 429s now go through.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan this Actor may be started 5 time(s) per calendar month per user. A run that finds nothing still counts, because the lookup is performed either way. Every Neuralverge Actor carries its own allowance — running one never uses up another's. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.

FAQ

Do I need a LinkedIn account or cookies? No. Everything runs on the Neuralverge backend — you never provide credentials or a session.

What if there are several people with the same name? total_candidates shows how many candidates the search returned; the row is the best one whose name actually matches what you asked for.

Why did I get no result for someone I know is there? The match is deliberately strict: a candidate whose name does not line up with the one you submitted is rejected rather than returned as a guess. The log names the rejected candidate, so you can check it and re-run with the spelling LinkedIn uses. The rejected lookup comes back as a no result row and is billed as one profile, like any other row.

Does it return emails or full profiles? No — this actor returns a search match (LinkedIn URL + headline). Use the LinkedIn Profile or LinkedIn Email actor for the full profile or a work email.

Am I charged if there's no match? Yes — a lookup that ran is billed as one profile even when it matched nothing; you get a no result row that says so. A run that fails (missing input, API error, timeout) writes no row and costs $0.00.

---

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn® is a registered trademark of LinkedIn Corporation. All trademarks are property of their respective owners.