Alternatives / Proxycurl · 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.
Last updated October 6, 2026
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 /find_personal_email | 5/call | — |
| Work Email Lookup | POST /email_finder | 5/call | — |
| Employee Listing | POST /linkedin_company_employees_search | 0.1/result | — |
| Job listings | POST /linkedin_job_search / linkedin_job_detail | 0.1/result + 1/call | — |
| Company posts / activity | linkedin_company_posts, post_activities | 0.2/result + 3/call | richer than Proxycurl's equivalent |
| (no equivalent) | ai_enrich | — | web intelligence suite, MCP server, and other things Proxycurl never had |
- 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 /find_personal_email- 5/call
- Work Email Lookup
POST /email_finder- 5/call
- Employee Listing
POST /linkedin_company_employees_search- 0.1/result
- Job listings
POST /linkedin_job_search/linkedin_job_detail- 0.1/result + 1/call
- Company posts / activity
linkedin_company_posts,post_activities- 0.2/result + 3/call · richer than Proxycurl's equivalent
- (no equivalent)
ai_enrich- — · web intelligence suite, MCP server, and other things Proxycurl never had
The four most-used Proxycurl endpoints each have a migration page with the request mapping: Person Profile, Company Profile, Person Lookup by email and Employee Listing. Billing and coverage side by side are on RichAPI vs Proxycurl.
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 by explicit endpoint rates (per call or per result), and unused bundle 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.ai with 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.
Proxycurl FAQ