> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/compare/proxycurl>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/compare/proxycurl.mdx>

---

# Proxycurl alternative: live LinkedIn data, plus every other network

Proxycurl shut down in 2025. Get live LinkedIn profiles and company pages as JSON — plus TikTok, Instagram, YouTube and X on the same key.

Proxycurl was the default LinkedIn enrichment API for many teams until it shut down in July 2025 after LinkedIn litigation. Traffic now points at Enrich Layer (and related successors). Social Fetch is a live multi-platform public social API — LinkedIn included, but not LinkedIn-only.

## At a glance

|  | Social Fetch | Proxycurl |
| --- | --- | --- |
| Status (2026) | Live, actively maintained | Proxycurl shut down July 2025; successor products exist |
| Core focus | Public social data across 25 platforms | LinkedIn person/company enrichment (historically) |
| Entry pricing | 100 free credits; $14 Starter pack (1,000 credits, one-time, never expire) | Was credit-based; see Enrich Layer for current terms |
| LinkedIn | Structured profile & company routes | Was deep LinkedIn enrichment; API now dark |
| Other networks | TikTok, Instagram, YouTube, Reddit, X, … | Not the historical product center |
| Best fit today | Teams rebuilding after Proxycurl or starting fresh | Enrich Layer if you want a like-for-like LinkedIn migration |

## Pricing (last verified 2026-09-23)

**Migrating off a shutdown vendor.** Proxycurl shut down July 2025 after LinkedIn litigation. Enrich Layer offers key/credit carryover for many users. Social Fetch: self-serve packs from $14, LinkedIn profile lookups at 3 credits each, and LinkedIn is one of 25 platforms on one key. Do not budget 2026 spend on dead Proxycurl SKUs.

|  | Social Fetch | Proxycurl | Note |
| --- | --- | --- | --- |
| Can I buy Proxycurl today? | N/A | No — service shut down July 2025 |  |
| LinkedIn profile JSON (live vendor) | ~$0.0049 per profile (3 credits) at the Scale pack rate | Enrich Layer / other LinkedIn APIs (separate pricing) |  |
| Multi-platform in one key | Yes — 264 operations | Historically LinkedIn-centric |  |
| Free start on Social Fetch | 100 credits, no card | N/A (Proxycurl) |  |
| Single-network shutdown risk | Spread across many platforms | Realized — LinkedIn legal action ended the product |  |
| Migration effort from Proxycurl | Map person/company fields to SF LinkedIn routes | Enrich Layer aims for wire-compatible migration |  |

Shutdown details from Nubela's Proxycurl goodbye post (July 2025) and public migration guides. Enrich Layer terms from enrichlayer.com docs. Social Fetch pricing from socialfetch.dev/pricing (September 2026): Scale pack $379 for 230,000 credits, about $1.64 per 1,000; LinkedIn credit costs from the API reference.

## Feature matrix

| Feature | Social Fetch | Proxycurl |
| --- | --- | --- |
| Synchronous REST JSON (no actor run polling) | Yes | Yes |
| One API key for all platforms | Yes | Yes |
| Unified schema across platforms | Yes | Yes |
| Public OpenAPI specification | Yes | Yes |
| Official TypeScript SDK | Yes | Yes |
| Interactive API playground | Yes | Yes |
| TikTok, Instagram, YouTube, LinkedIn, Facebook, Reddit, X in one vendor | Yes | Yes |
| Pay-as-you-go without required monthly subscription | Yes | Yes |
| PAYG credits never expire | Yes | Yes |
| Web fetch (markdown/HTML) in same product | Yes | Yes |
| Scheduled account / feed monitors | Yes | No |
| Signed webhooks when watched accounts post | Yes | No |

## Proxycurl shut down in July 2025

Proxycurl was widely used for LinkedIn person and company enrichment: URL in, JSON out, credit billing, developer-friendly docs. In 2025 LinkedIn sued; the service wound down. The founder's public goodbye stated the team complied with the settlement and stopped the product.

If your integration still calls proxycurl.com hosts, it is already broken. This page exists for migration shopping, not for a living price war with a dead API.

## Enrich Layer as the like-for-like path

Enrich Layer positions itself for former Proxycurl users: existing API keys, similar endpoints, credit carryover, base URL change. If LinkedIn enrichment is your only requirement and you trust that operator path, it can be the lowest-effort migration.

Social Fetch is not pretending to be a drop-in Proxycurl clone. Field names differ. People-search depth differs. What you get instead is a maintained multi-platform public social API with LinkedIn as one network among many — plus self-serve pricing and an official TypeScript SDK.

## The lesson is vendor concentration

Proxycurl's revenue concentration on LinkedIn scraping became an existential risk when litigation hit. Teams that only ever needed LinkedIn still felt it; teams that had parked "we will add Instagram later" on the same vendor lost the whole enrichment layer overnight.

Social Fetch spreads public coverage across 25 platforms and 264 operations. That does not make anyone lawsuit-proof — public data vendors all carry platform risk — but it means your product roadmap is not a single-network monoculture behind one enrichment SKU.

## Where they win

If you need maximum wire compatibility with old Proxycurl clients and LinkedIn is your only network, evaluate Enrich Layer first. Social Fetch will cost engineering time to remap fields.

If you are rebuilding anyway, or you already needed TikTok/Instagram/YouTube beside LinkedIn, starting on a live multi-platform API is usually cheaper than stitching Enrich Layer plus three other vendors.

## When Proxycurl is the better choice

- You want the lowest-effort Proxycurl → Enrich Layer migration for LinkedIn-only
- Your codebase depends on Proxycurl-shaped endpoints and you refuse a remap
- LinkedIn enrichment is the entire product surface

## When Social Fetch is the better choice

- You are rebuilding and want a live vendor with published PAYG pricing
- You need LinkedIn plus other social networks under one key
- Official TypeScript SDK, playground, and requestId matter
- You want to reduce single-network vendor concentration risk
- Cold public enrichment without waiting on a LinkedIn-only successor sales motion

## Verdict: Dead LinkedIn API vs live multi-platform API

Proxycurl is gone. Enrich Layer is the continuity bet for LinkedIn-only stacks. Social Fetch is the rebuild bet for teams that want public social JSON across many networks with self-serve credits. Choose based on migration pain versus roadmap breadth — not on nostalgic Proxycurl rate cards.

## FAQ

### Is Proxycurl still available?

No. The service shut down in July 2025. Treat any "Proxycurl pricing 2026" page that implies you can buy it as outdated.

### What is Enrich Layer?

A LinkedIn-focused successor path documented for many former Proxycurl customers (keys/credits/base URL). Evaluate it separately from Social Fetch.

### Does Social Fetch replace Proxycurl 1:1?

Not as a wire-compatible clone. Expect to remap LinkedIn person/company fields to Social Fetch routes and retest. You gain multi-platform coverage in exchange.

### Does Social Fetch offer LinkedIn people search like Proxycurl?

There is a public people search route, `GET /v2/linkedin/people/search` (3 credits), alongside profile, company, job, and post routes. That is not a promise of every historic Proxycurl endpoint — check the [LinkedIn endpoint list](https://www.socialfetch.dev/platforms/linkedin) and validate the exact operations you need.

### Why compare against a dead product?

Because search traffic still asks "Proxycurl alternative." This page answers with accurate shutdown context and a live multi-platform option — without pretending Proxycurl still sells credits.
