The Proxycurl alternative for LinkedIn data
Proxycurl shut down in July 2025. SocialCrawl gives you LinkedIn profile, company, and people data through one API — and 41 more platforms behind the same key. Migrate in a day.
Swap your base URL and set x-api-key. /v1/linkedin/profile and /v1/linkedin/company map straight onto your old /person and /company calls.
Facts last verified June 16, 2026
Searching 42 platforms in parallel
TikTok·
Instagram·
YouTube·
Facebook·
X·
LinkedIn·
Reddit·
Threads·
Pinterest·
Twitch·
Truth Social·
Snapchat·
Kick·
Bluesky·
Kwai·
Rumble·
Spotify·TikTok Shop·
Amazon Shop·
Google Shopping·
Trustpilot·
TripAdvisor·
Linktree·
Komi·
Pillar·
lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Google Finance·
Polymarket·
Tavily·
Hacker News·
GitHub·
Perplexity·
Naver·UUtility·
Universal SearchTikTok·Instagram·YouTube·Facebook·X·LinkedIn·Reddit·Threads·Pinterest·Twitch·Truth Social·Snapchat·Kick·Bluesky·Kwai·Rumble·Spotify·TikTok Shop·Amazon Shop·Google Shopping·Trustpilot·TripAdvisor·Linktree·Komi·Pillar·lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Google Finance·Polymarket·Tavily·Hacker News·GitHub·Perplexity·Naver·UUtility·Universal SearchTikTok·Instagram·YouTube·Facebook·X·LinkedIn·Reddit·Threads·Pinterest·Twitch·Truth Social·Snapchat·Kick·Bluesky·Kwai·Rumble·Spotify·TikTok Shop·Amazon Shop·Google Shopping·Trustpilot·TripAdvisor·Linktree·Komi·Pillar·lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Google Finance·Polymarket·Tavily·Hacker News·GitHub·Perplexity·Naver·UUtility·Universal SearchTikTok·Instagram·YouTube·Facebook·X·LinkedIn·Reddit·Threads·Pinterest·Twitch·Truth Social·Snapchat·Kick·Bluesky·Kwai·Rumble·Spotify·TikTok Shop·Amazon Shop·Google Shopping·Trustpilot·TripAdvisor·Linktree·Komi·Pillar·lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Google Finance·Polymarket·Tavily·Hacker News·GitHub·Perplexity·Naver·UUtility·Universal SearchWhat should I use now that Proxycurl has shut down?
Proxycurl permanently closed on July 4, 2025 after LinkedIn's lawsuit. The same team relaunched as Enrich Layer, which honors old keys — but it's still LinkedIn-only. SocialCrawl ships LinkedIn as one of 42 platforms, so the next shutdown can't take your whole pipeline with it.
Unified schema
One field name across 42 platforms. Write one parser, not 13.
MCP server
`npx socialcrawl-mcp` on the MCP Registry. Works in Claude Code, Cursor, Windsurf.
Visual Explorer
Paste any URL, see rich cards and export as code. No API key needed to browse.
How does SocialCrawl compare to Proxycurl for LinkedIn data?
Side by side on the things a stranded Proxycurl customer actually asks about: LinkedIn coverage, platform breadth, agent tooling, and billing risk. Proxycurl rows reflect its last-known pre-shutdown state (service discontinued July 2025); SocialCrawl rows verified 2026-06-16.
| Feature | SocialCrawl | Proxycurl |
|---|---|---|
| Status | ||
| Service availability | Live, actively maintained | Shut down July 4, 2025 (redirects to Enrich Layer) |
| Successor | N/A — original product | Enrich Layer (same team, LinkedIn-only) |
| LinkedIn coverage | ||
| Profile lookup by URL | /v1/linkedin/profile | /person (now dark) |
| Company lookup by URL | /v1/linkedin/company | /company (now dark) |
| People / employee search | Post search + company endpoints | Employee + people search (now dark) |
| Posts, transcripts, ad library | Company posts, post, post search, transcript, ad, ads search | Partial (posts, jobs — now dark) |
| Platforms & endpoints | ||
| Platforms covered | 42 platforms | 1 (LinkedIn only) |
| Total endpoints | 264 endpoints | LinkedIn-only endpoint set |
| Single-platform shutdown risk | Spread across 42 platforms | Entire product gone when LinkedIn sued |
| Schema & data quality | ||
| Unified response schema | Enforced at the gateway | LinkedIn-specific field names only |
| Computed fields (engagement_rate, estimated_reach) | Pre-calculated on every response | Not provided |
| Agent readiness | ||
| Official MCP server | Shipped (npx socialcrawl-mcp) | None (predated MCP) |
| Skills bundle / agent tooling | Skills bundle across 40+ runtimes | None |
| Non-technical tooling | ||
| Visual Explorer (browse before code) | Paste a URL, see cards, export code | Docs pulled — nothing to preview |
| Pricing & billing | ||
| Billing model | Monthly subscription, GBP | Credit packs + annual commit, no rollover (discontinued) |
| Free tier | 100 credits, no card | No free tier |
| Lock-in risk | Cancel anytime | 12-month commit, prepaid credits stranded at shutdown |
| Internationalization | ||
| Bilingual surface (EN + KO) | Native English + Korean docs | English-only |
Status
Service availability
Successor
LinkedIn coverage
Profile lookup by URL
Company lookup by URL
People / employee search
Posts, transcripts, ad library
Platforms & endpoints
Platforms covered
Total endpoints
Single-platform shutdown risk
Schema & data quality
Unified response schema
Computed fields (engagement_rate, estimated_reach)
Agent readiness
Official MCP server
Skills bundle / agent tooling
Non-technical tooling
Visual Explorer (browse before code)
Pricing & billing
Billing model
Free tier
Lock-in risk
Internationalization
Bilingual surface (EN + KO)
Does SocialCrawl cover the LinkedIn endpoints Proxycurl gave me?
Yes — the core ones map directly. Proxycurl's /person and /company become SocialCrawl's /v1/linkedin/profile and /v1/linkedin/company, plus company posts, post lookup, post search, transcripts, and the ad library — all returning one unified schema.
- Person and company enrichment by LinkedIn URL works the same way: pass the URL, get a normalized profile or company object back.
- People-search and job-style enrichment flows map onto post search and company endpoints, so most integrations need only field renames.
- Every LinkedIn response shares the same field names, ISO-8601 UTC timestamps, and integer counts as the other 41 platforms.
- Computed fields like engagement_rate and estimated_reach arrive pre-calculated, so you analyze data instead of deriving it.
Your existing fetch-by-URL pattern carries over — you remap field names once, not rebuild the integration.
Why did relying on one LinkedIn API leave me stranded?
Proxycurl was LinkedIn-only, so when LinkedIn's lawsuit forced it to close, customers lost everything overnight with no fallback. SocialCrawl ships LinkedIn as 1 of 42 platforms, so a single platform's legal trouble can't take your whole data pipeline down with it.
- The same key reaches TikTok, Instagram, YouTube, X, Reddit, Facebook, and 36 more — LinkedIn is one source among many, not the whole product.
- If any single platform becomes unavailable, the other 41 keep returning data and your integration keeps running.
- 264 endpoints across 42 platforms mean you can add a second or third data source without signing up for another vendor.
- GET /v1/search/everywhere fans out across 12 social platforms in one call when you need reach beyond LinkedIn.
Spreading across 42 platforms means the next shutdown costs you one source, not your entire pipeline.
Can my AI agent call LinkedIn data directly?
Yes — SocialCrawl ships an MCP server and a Skills bundle, so agents in Claude Code, Cursor, and Windsurf query LinkedIn (and 41 other platforms) without custom glue. Proxycurl predated MCP and never offered any of this.
- npx socialcrawl-mcp registers on the MCP Registry and installs in seconds — no SDK to wire up per platform.
- Responses arrive normalized, so your agent reasons over profiles and companies instead of parsing raw JSON per endpoint.
- The Skills bundle exposes the same API across 40-plus agent runtimes, not just one editor.
- If you're building enrichment into an AI workflow, the data lands in a shape your model can use straight away.
For agent builders, an MCP install is the difference between a two-minute setup and a week of custom integration.
npx socialcrawl-mcpListed on MCP RegistryMCP Registry · npm · Smithery · skills.sh
npx proxycurl-mcpNot on MCP Registry, npm, or Smitherypersonal GitHub only · not registered
Can I see the LinkedIn data before writing any code?
Yes — paste any LinkedIn URL into the Visual Explorer and see the profile or company as rich cards and sortable tables, then copy it as cURL, JavaScript, or Python. No API key needed to browse. Proxycurl's docs are pulled, so there's nothing left to preview.
- PMs, analysts, and recruiters confirm 'can we actually get this field?' themselves, without booking engineering time.
- Every Explorer query exports as a ready-to-paste code snippet, so the jump from preview to production is one copy.
- Browse a profile or a company's posts as cards first, then drop into code once you know the shape fits your product.
See your data before writing a single line — usually enough to decide whether to migrate today.
fetch("/v1/...")Enrich Layer = Nubela's Proxycurl successor · honors old keys · still LinkedIn-only · noted 2026-06-16
Is Enrich Layer a viable place to stay?
For some teams, yes — and pretending otherwise would be dishonest. Enrich Layer is the same Nubela team that built Proxycurl, it reportedly honors existing Proxycurl keys and credits, and it offers a request-conversion tool, so a like-for-like LinkedIn migration is genuinely low-effort. If LinkedIn is your only data source and you trust the operator, staying is a fair call.
- Enrich Layer continues the Proxycurl product under a new name, with the same person/company endpoints developers already know.
- The honoring of old keys and a conversion tool make a same-team migration the path of least resistance for LinkedIn-only stacks.
- Where SocialCrawl differs is breadth and durability: LinkedIn is 1 of 42 platforms here, plus an MCP server and monthly billing — so the question is whether to stay single-platform or de-risk onto a wider base.
How does SocialCrawl pricing compare to Proxycurl's?
There's no live head-to-head here: Proxycurl's pricing went dark when the service closed in July 2025, so the right column shows its last-known pre-shutdown rates for context only. SocialCrawl pricing is live, verified 2026-06-16.
No lock-in
Monthly billing, no 12-month commit
SocialCrawl: monthly, cancel anytime · Proxycurl: annual commit, no rollover (now discontinued) · noted 2026-06-16
Proxycurl figures are last-known pre-shutdown rates (service discontinued July 2025) shown for context, not a live quote — and were credit-pack and annual-commit, so prepaid credits could strand at closure. SocialCrawl bills monthly in GBP with no 12-month lock-in; treat any cross-currency per-credit comparison as indicative.
See full pricingWho should migrate to SocialCrawl?
Stranded Proxycurl customers and Enrich Layer users who want more than LinkedIn: B2B enrichment and sales-intelligence teams, recruiting tools, and AI-agent builders who'd rather not bet a whole product on one platform again.
Migrate to SocialCrawl if:
- You were burned by a single-platform shutdownLinkedIn is 1 of 42 platforms here, so no one platform's legal trouble can take your whole pipeline dark again.
- You build B2B enrichment or sales intelligenceProfile and company lookups by LinkedIn URL map straight onto /v1/linkedin/profile and /v1/linkedin/company.
- You're shipping with AI agentsnpx socialcrawl-mcp installs in Claude Code, Cursor, and Windsurf — tooling Proxycurl never had.
- You want billing without lock-inMonthly subscription, no 12-month commit, and no prepaid credits stranded if priorities change.
- You serve Korean-market or bilingual teamsSocialCrawl ships native English and Korean docs and a /ko/ surface, not English-only access.
Stay on Enrich Layer if:
Enrich Layer is a reasonable home for some Proxycurl refugees — and saying so plainly is more useful than pretending SocialCrawl is the only option.
- LinkedIn is your only data sourceIf you never touch TikTok, Instagram, YouTube, or any other network, a single-platform LinkedIn API may be all you need.
- You want the lowest-effort migrationEnrich Layer honors old Proxycurl keys and ships a request-conversion tool, so a same-team move is close to drop-in.
- You're comfortable with the operator's legal postureIt's the same Nubela team and the same LinkedIn-data model — if you trust that footing, staying is a fair call.
- You prefer credit-pack billing for batch runsIf occasional batch enrichment fits credit packs better than a monthly plan, that billing shape may suit you.
Already migrated to Enrich Layer and only ever need LinkedIn? You may not need to move again yet. Come back when you need a second platform, an MCP server, or a vendor that doesn't ride on one network's legal standing.
Frequently asked questions
Can't find what you're looking for? Talk to our team or ask the AI agent below
Ask AI about SocialCrawl
Looking for the best Proxycurl alternative for social media data?
Every SocialCrawl comparison follows the same honest format — verified pricing, a schema diff, and a straight answer on which team each tool fits.
Move your LinkedIn data onto a platform that can't shut down overnight
100 free credits, no card — pull real LinkedIn profiles and companies and see the migration is a day, not a rebuild.