LinkFetch vs Coresignal — developer-first vs enterprise-first.
Pricing · LinkFetch vs Coresignal.
The table.
| capability | LinkFetch | Coresignal |
|---|---|---|
01Floor price | $29 / mo | $49 / mo |
02Real-time jobs webhook | All paid tiers | $1,500 / mo Premium |
03Jobs is_active flag | yes | yes |
04Parsed salary (min · max · currency · interval) | yes | yes |
05Time to first call | 90 sec | Days · demo gated |
06Self-serve sign-up | yes | Starter only |
07Annual commit required | no | 20% off if you sign |
08MCP-native (Claude · Cursor · Zed) | yes | no |
09Pay-as-you-go credits | yes | no |
10Typed TypeScript + Python SDKs | yes | Partial |
11Provenance on every row | yes | no |
12GDPR + CCPA aligned | yes | Partial |
13Multi-source dedupe (LinkedIn + Indeed + Glassdoor) | no | yes |
14Historical 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 + webhook on every paid tier
import { LinkFetch } from "@linkfetch/sdk";
const lf = new LinkFetch({ apiKey });
// One call to search
const { data } = await lf.jobs.search({
q: "backend engineer",
workplace_type: "remote",
posted_within: "week",
});
// Or subscribe and never poll again
await lf.jobs.subscriptions.create({
filter: { q: "backend engineer", workplace_type: "remote" },
delivery: { url: "https://your-app.com/webhooks/linkfetch" },
});Questions people ask before switching from Coresignal.
I just want jobs webhooks — what's the price difference?
LinkFetch: $29/mo Starter or $89/mo Subscription, both include real-time jobs webhooks (<60s). Coresignal: webhooks are gated at the Premium tier — $1,500/mo. So roughly a 17–50× price difference for the same delivery shape. If your agent only needs jobs, you're paying Coresignal for an enterprise sales motion you're not consuming.
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?
Our Custom dataset tier delivers up to 12 months of historical backfill today; we're extending to 24 months in Q3 2026. For most agent workflows (sales-intent, recruiting, market research), 3–6 months of recency is enough — and LinkFetch is real-time where Coresignal's bulk is daily/weekly/monthly.
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.