6 providers · from $0.0015 per result · $0.000 markup

LinkedIn API and LinkedIn scraper: a person's profile by URL, headline, experience and education

Give your agent a LinkedIn profile URL and get the profile back as data: name, headline, location, current role, past roles and education. 6 providers answer through one treg.to key, the cheapest of them a tenth of a cent a profile, each at its own rate with no markup and none behind a monthly seat. No session cookie of yours, no browser extension, no Sales Navigator subscription and no account of yours making the request. LinkedIn's own row is here too and it is honest about what it is: it returns the profile of the account you connected, and nobody else's.

Start free See the comparison

$1.00 of free credit on every new team · no provider signup · no card

4 of 6 endpoints on this page are live-verified against the provider.

compared on this page

Try it

What’s the best way to ask ChatGPT?

1Set your agent up, once

in your agent's chat

set up treg — https://treg.to/llms.txt

2Ask for the job

the prompt

Using treg, fetch these 40 LinkedIn profile URLs from the cheapest verified provider, show me the price per profile first, then give me name, headline, current company and years in the current role as a table, and list the URLs that came back empty.

works in

Why this prompt works

Give the profile URL

Most rows take the public profile URL or its slug. A name and a company is a different job, and a different page.

Say which fields you need

A full profile is a large object. Naming the columns keeps the table readable and keeps the agent from spending its context on someone's volunteering history.

Ask for the price first

The rates here differ by more than an order of magnitude per profile. treg.to prints the rate before the call, so 40 profiles has a number on it before anything runs.

Ask for the misses by name

Every provider misses some profiles. A list of the URLs that came back empty is worth more than a table that quietly has 34 rows instead of 40.

Why treg.to

Why go through treg.to

One key, not 9 accounts

treg.to holds the provider keys. Neither you nor the agent sees them.

Price before the call

The provider's own rate, $0.000 markup, from a prepaid balance.

No subscription, no seats

Charged per call. $1.00 free per new team, no card to start.

Your own keys are free

Already pay Hunter? Register it and those calls are never metered.

Switch by changing a word

Another provider is a different word in the prompt, not a new integration.

Nothing to integrate

No SDK, no OAuth dance per vendor, no seats.

Behind the scenes

What ChatGPT sees before it calls

treg.to does not choose for you. It hands ChatGPT this comparison, with the price shown before any call, and ChatGPT picks. Or you tell it how: "cheapest", "most reliable", "the one that takes what I have", or a provider by name.

Which LinkedIn API is cheapest per profile?

Cheapest per result

Bright Data at $0.0015

Cheapest per call

ScrapeCreators at $0.00188

Cheapest per found

TikHub at $0.001

Those units are not interchangeable: one call can return many results, so compare on the unit you will actually be billed in.

Which LinkedIn API is the most reliable?

Provider	Success	Median	Sample
LinkedIn	100%	213ms	6 calls
TikHub	100%	13.2s	300 calls
Just One API	100%	18.9s	9 calls
Bright Data	100%	26.1s	84 calls
ScrapeCreators	100%	2.5s	1999 calls

Measured on treg.to traffic: real calls, real inputs, and sample sizes differ by provider. Live reliability, not a controlled benchmark.

How do the LinkedIn providers compare?

Provider	Price	Accepts	Success rate	Verified
TikHub	$0.001 per found	url	100% (300 calls)	2026-07-28
Bright Data	$0.0015 per result	dataset_id, format, input	100% (84 calls)	2026-07-28
ScrapeCreators	$0.00188 per call	url	100% (1999 calls)	2026-07-28
Just One API	$0.0295 per found	username	100% (9 calls)	2026-07-28
Fiber AI	$0.04 per call	identifier, getDetailedEducation, getDetailedWorkExperience	(3 calls)	unverified
LinkedIn	free, your own account	see endpoints	100% (6 calls)	unverified

Run one

the cheapest verified call

treg call brightdata.linkedin.user.profile --query dataset_id=gd_l1viktl72bvl7bjuj0 --query format=json --data '[{"url":"https://www.linkedin.com/in/satyanadella"}]'

Swap the id for any provider above. All 6 endpoints behind this job, with their parameters and captured responses, are on the LinkedIn shelf.

How these numbers are made

PricesEach provider’s own published rate, converted to US dollars for one chargeable event of the unit they bill in. treg.to adds $0.000. Where a provider bills in credits, the conversion uses the rate on their public pricing page, last checked 2026-07-28.

Success ratetreg.to’s own served calls over the last 30 days: 2xx counts as a success, 5xx and timeouts as a failure. A 4xx is excluded, because it usually means the caller sent bad parameters and one bad query should not make a healthy endpoint look broken.

What this is notA controlled benchmark. These are real calls with real inputs, so sample sizes and the difficulty of what was asked differ by provider. Treat the rates as live reliability, not a like-for-like test.

VerifiedThe date treg.to last called the endpoint end to end and confirmed the shape of its response and the price it charged.

From the field

What people actually struggle with

LinkedIn data is one of the most seeded topics on Reddit: of the ~170 posts read in August 2026, one account posted fourteen actor listings in a subreddit it appears to run, one promo shipped with its template placeholder still in the body, and one seeded thread carried a zero-width space. These five are practitioners, and the last one is the reason the page will not claim zero risk.

An extension got an SDR restricted in days

“My SDR got his account limited after using PhantomBuster for like 3 days.” r/b2bmarketing, 16 points

What this page can do about it: That risk is the one thing these rows genuinely remove. A call here runs on the provider's infrastructure, not on your seat, so there is no cookie of yours and no activity on your account to flag.

Being banned is not survivable for some jobs

“I review hundreds of Linkedin profiles a week for a living and it is not viable to be banned from the platform.” r/apify

What this page can do about it: Which is the argument for keeping the fetch off your login entirely. Read the profiles through a provider, keep your own account for the human work, and pay per profile rather than per seat.

The enrichment tools are priced for a different buyer

“Tools like Clay's 'Enrich Profile' feature or APIs like Brightdata feel quite pricey. Any suggestions or alternative approaches?” r/revops, 5 points

What this page can do about it: Bright Data is one of the rows here, at its own per-record rate with nothing added, and it is not the cheapest one. The point is the shape: a profile is a call, there is no plan to be on, and the rate is printed before the agent spends it.

The default answer shut down

“Looking for a good alternative to Proxycurl (they shut down) for B2B sales automation” r/n8n, 6 points

What this page can do about it: This page is five of the alternatives with their prices next to each other. It is worth saying that the forum has not moved on to one successor, so the checklist that thread asks for, profile plus company plus job changes, is three jobs here and three rows.

The restriction can arrive with no automation at all

“the funny thing is i wasnt using anything to automate linkedin, just clicking around and opening new tabs” X, 199 likes

What this page can do about it: Which is why this page says the rows remove the automation risk on your own login and stops there. Nothing here makes LinkedIn safer for the account you browse with; it just stops needing it.

The detail

What actually differs

Five third-party rows and one official one, and the official one is a different job.

LinkedIn's own OAuth row is free, runs on your team's connected account and is never metered, and it returns that account's own profile: name, email, member id. It cannot fetch a prospect. The other five fetch anyone's public profile and none of them uses an account of yours, so no cookie of yours, no extension in your browser and no view on your activity log.

The units differ, so read the rate and the word after it.

TikHub bills per successful call, ScrapeCreators per call whether or not the profile comes back, Bright Data per record delivered, JustOneAPI per success priced in yuan and converted, and Fiber per credit for a live fetch. The cheapest claim on this page is made inside one unit and never across them. ScrapeCreators, Bright Data, TikHub and JustOneAPI have been called live and carry a verified date in the catalog; the Fiber row and the LinkedIn OAuth row are documented from the provider's own docs and have not been verified through treg.to.

What nobody can promise is coverage, and this page will not.

Each provider reads LinkedIn its own way, so a profile one returns in full is one another returns thin, and the fields most often missing are exactly the ones people want: the dated experience list. The cheap experiment is the honest answer: run the same twenty URLs through three rows for a few cents and count who filled the columns you need. treg.to shows the rows side by side and the agent picks; it does not route between them and it does not fail over.

Background

What is a LinkedIn API, and why is there no official one?

A LinkedIn API, as people mean the phrase, returns a person's public profile as structured data: headline, location, the roles they have held with dates, and where they studied. LinkedIn's official API does not do this. It is an OAuth API for the account that authorised it, so it can tell you your own name and email and it cannot tell you a stranger's job history; that product does not exist for you. Everything else on this page is a third-party provider that reads public profiles with its own infrastructure and sells the result per profile. Proxycurl, which was the default answer here for years, shut down, which is why the question keeps being asked.

Questions

Before you start

Is there an official LinkedIn API for other people's profiles?

No. LinkedIn's OAuth API returns the profile of the member who authorised your app, so it answers "who am I" and never "who is this person". The row on this page is that call, marked free and run on your own connection. Everything else here is a third party.

Will this get my LinkedIn account banned?

None of the five third-party rows uses an account of yours: no cookie, no session, no extension, so there is nothing of yours for LinkedIn to restrict. That is not the same as zero risk in general, because the restriction stories in the forum include people who were only browsing. The risk these rows remove is the automation risk on your own login; the provider carries its own.

What replaced Proxycurl?

Nothing single replaced it. The five third-party rows here are what the catalog carries for a person profile by URL, priced per profile with no plan, and the honest note is that they are not a drop-in: the field coverage and the freshness are each provider's own. Company pages, job changes and people search are separate jobs on separate rows.

Which provider should my agent use?

The one whose fields survive your list at a rate that fits the volume. treg.to puts the rate, the billing unit and the measured success rate beside each other and the agent chooses, or you tell it which to use. treg.to compares; it does not pick for you.