LinkFetch vs Coresignal — developer-first vs enterprise-first.
Pricing · LinkFetch vs Coresignal.
The table.
| capability | LinkFetch | Coresignal |
|---|---|---|
01Floor price | $0 · $5 credit, then $29 / mo | $49 / mo |
02Bulk jobs dataset | $199 one-time · 8M+ rows | $1,000+ per dataset |
03Real-time jobs webhook | Not yet — poll or live DB | $1,500 / mo Premium |
04Applicant count + history per posting | yes | no |
05Jobs is_active flag | yes | yes |
06Parsed salary (min · max · currency · interval) | yes | yes |
07Time to first call | 90 sec | Days · demo gated |
08Self-serve sign-up | yes | Starter only |
09Annual commit required | no | 20% off if you sign |
10MCP-native (Claude · Cursor · Zed) | yes | no |
11Pay-as-you-go credits | yes | no |
12Plain HTTPS + JSON (no SDK required) | yes | Partial |
13Provenance on every row | yes | no |
14GDPR + CCPA aligned | yes | Partial |
15Multi-source dedupe (LinkedIn + Indeed + Glassdoor) | no | yes |
16Historical depth (24+ months) | via Custom | yes |
LinkFetch: sign up, paste a key, first call in 90 seconds
Coresignal: sales demo → eval → annual contract → data delivery (weeks)
Swap Coresignal → LinkFetch in 30 minutes.
# Coresignal — Multi-Source Jobs API
# Webhooks gated at Premium ($1,500/mo). On lower tiers, you poll.
curl -X POST https://api.coresignal.com/cdapi/v2/job_multi_source/search/es_dsl \
-H "apikey: $CORESIGNAL_KEY" \
-d '{"query":{"bool":{"must":[
{"match":{"title":"backend engineer"}},
{"term":{"accepts_remote":true}},
{"range":{"date_posted":{"gte":"now-7d"}}}
]}}}'// LinkFetch — typed jobs API, plain fetch, 1 credit per call
const params = new URLSearchParams({
q: "backend engineer",
posted_within: "week",
limit: "50",
});
const res = await fetch(`https://api.linkfetch.io/v1/jobs?${params}`, {
headers: { Authorization: `Bearer ${process.env.LINKFETCH_KEY}` },
});
const { data, meta } = await res.json();
// data[i].salary_min, .applicant_count, .is_active — meta.fetched_atQuestions people ask before switching from Coresignal.
I just want LinkedIn jobs data — what's the price difference?
LinkFetch: a jobs search is 1 credit, the free tier ships with $5 of credit, Starter is $29/mo, and the entire 8M+ row archive is $199 one-time. Coresignal: Starter at $49/mo per their public pricing, datasets from $1,000, and real-time webhooks gated at the $1,500/mo Premium tier. LinkFetch does not have webhooks yet — you poll posted_within=24h or query the live database — so if push delivery is a hard requirement today, Coresignal Premium is the honest answer.
When should I pick Coresignal over LinkFetch?
If you need deep historical data (24+ months), multi-source dedupe across LinkedIn + Indeed + Glassdoor + Wellfound in a single feed, and your team is fine with a multi-week sales cycle — Coresignal is still a credible choice. If you want to ship an agent workflow this week against LinkedIn-only public jobs, LinkFetch is the answer.
Can LinkFetch match Coresignal's depth?
Not on history. Our archive starts in April 2026 and grows by roughly 45,000 postings a day, so it is the right choice when you care about what is being posted now, and the wrong one if you need multi-year backfill. What LinkFetch adds that Coresignal doesn't is the applicant-count time series per posting and per-row provenance.
Coresignal markets multi-source dedupe. What does LinkFetch do instead?
We're LinkedIn-only by design — that's our compliance line and our specialization. If you need cross-source dedupe across LinkedIn + Indeed + Glassdoor in a single feed, that's a real Coresignal advantage. If you need LinkedIn data with maximum freshness, an is_active flag re-checked on every crawl, and per-row provenance, that's LinkFetch.
What about compliance?
Both of us are aligned with GDPR and CCPA in our marketing. LinkFetch is stricter in practice: jobs come from LinkedIn's cookieless guest endpoints (the Meta v. Bright Data side of the line), profiles run on the user's own session via the extension, provenance on every row. Coresignal's posture varies by feed — ask for a DPA before you sign either of us.
Can I use both?
Yes. Common pattern: Coresignal for historical bulk analysis with multi-source dedupe; LinkFetch for real-time agent workflows, MCP tooling, and on-demand lookups. They're complementary, not strictly substitutable.