Proxycurl alternative · 2026

Migrating from Proxycurl?
Here's the honest version.

Proxycurl shut down in July 2025 following LinkedIn's lawsuit. If your product depended on its API, you need two things: equivalent endpoints, and a provider built to survive. Here's exactly what maps, what doesn't, and why our data supply chain is different.

Start free — 25 credits Email the migration team

What happened (factual, no gloating)

Audit the supply chain of the API you choose.

In January 2025, LinkedIn filed suit against Proxycurl's operator, alleging large-scale data collection through fake accounts. By July 4, 2025, Proxycurl had shut down entirely — at roughly $10M in annual revenue. Thousands of products lost their enrichment backend with months of notice. The lesson isn't “don't use enrichment APIs.” It's: audit the supply chain of the one you choose.

Endpoint migration map

What maps, endpoint by endpoint.

You used (Proxycurl)	You'll use (RichAPI)	Credits	Notes
Person Profile endpoint	`POST /enrich_profile`	1	LinkedIn URL in, structured profile out
Company Profile endpoint	`POST /enrich_company`	1
Person Lookup (name+company)	`POST /people_search` → `enrich_profile`	0.1/result + 1
Reverse Email Lookup	`POST /person_enricher`	2 on success	waterfall; soft miss = 1
Work Email Lookup	`POST /email_finder`	2 on success	5-provider waterfall; soft miss = 1
Employee Listing	`POST /linkedin_company_employees_search`	per result
Job listings	`POST /linkedin_job_search` / `linkedin_job_detail`	per call
Company posts / activity	`POST /company_posts`, `post_activities`	2–3	richer than Proxycurl's equivalent
(no equivalent)	`ai_enrich`, web intelligence suite, MCP server	—	things Proxycurl never had

the whole migration for profile enrichment, in one diff

- GET https://nubela.co/proxycurl/api/v2/linkedin?url={profile}
-   Authorization: Bearer {token}
+ POST https://api.richapi.ai/api/v1/enrich_profile
+   x-api-key: {key}
+   {"url": "{profile}"}

The supply-chain difference

You're migrating off a risk profile,
not just endpoints.

What we don't do: operate fake-account networks, scrape behind login walls at bulk, or republish people-directories. What we do: buy from licensed data providers and run them in waterfalls, operate an engine with eight years of production history and 26,000+ workspaces behind it, honor deletion requests downstream, and put our supply-chain posture in writing at /security. You're not just migrating endpoints — you're migrating off the risk profile that killed your last vendor.

What's different (honest expectations)

Budget for these three things.

Response field names differ — budget a mapping layer (our migration guide in docs has the field tables).
We bill success-weighted credits, not monthly quotas: misses cost half or less, and unused credits never expire.
Some Proxycurl niche endpoints (e.g., school profiles) have no direct equivalent — check the map above before committing. Tell us what's missing: the catalog grows monthly.

Proxycurl refugees: email support@richapi.aiwith your old use case; we'll review your endpoint mix against the map on a call and credit your first bundle +20%. Most migrations are a day of work; ours took a customer an afternoon.

FAQ

Frequently asked questions

Is RichAPI just doing what Proxycurl did with extra steps?

No — different collection model entirely: licensed providers in waterfalls, not first-party mass scraping. Detail: /security.

Could RichAPI get shut down the same way?

Our exposure profile is structurally different (see the supply-chain section), our providers carry their own compliance obligations, and we're an EU company operating GDPR-first. No vendor can promise immortality; we can show you the architecture and let you judge.

What about price?

Proxycurl charged per call regardless of result. We bill full rate only on results — for email lookups especially, misses no longer cost full freight.

Migrate in an afternoon.