Scrape full LinkedIn profile data via Clado contact enrichment at $0.20/request
What it does
This endpoint (`/api/clado/linkedin-scrape`) is listed under the StableEnrich platform but does not appear in the published OpenAPI spec or documentation. The documented Clado endpoint is `/api/clado/contacts-enrich`, which enriches contact information (emails, phones, social links) from a LinkedIn URL, email, or phone number at $0.20 per request. It is possible that `/api/clado/linkedin-scrape` is an alias, a deprecated path, or an unlisted route — the probe returned 404 on both HEAD and GET, and the endpoint is not present in the OpenAPI paths.
The Clado contacts-enrich endpoint accepts exactly one of `linkedin_url`, `email`, or `phone` and optionally enables `email_enrichment` and `phone_enrichment` flags. It returns an array of contact objects (type, value, rating, subType) and social profile links. This is useful as a fallback when Apollo or Minerva don't return personal emails or phone numbers. The endpoint is part of StableEnrich's pay-per-request model, settling via x402 or MPP (Tempo) micropayments on Base mainnet or Solana — no API keys or subscriptions required.
Because the specific `/api/clado/linkedin-scrape` path returned 404 during probing and is absent from the OpenAPI spec, callers should use `/api/clado/contacts-enrich` instead. The documented contacts-enrich endpoint has full schema, pricing ($0.20/request), and response definitions available.
Capabilities
Use cases
- —Enrich a LinkedIn profile URL to get associated emails and phone numbers
- —Find personal contact info when Apollo or other B2B tools return incomplete data
- —Reverse-lookup a phone number or email to find associated social profiles
- —Build lead lists with verified contact details from LinkedIn URLs
- —Supplement CRM records with direct contact information
Fit
Best for
- —Agents needing personal email/phone from a LinkedIn URL
- —Fallback contact enrichment when B2B data providers lack personal info
- —Pay-per-use contact lookups without subscription commitments
Not for
- —Bulk LinkedIn profile scraping (single-record per call at $0.20)
- —Retrieving full LinkedIn work history or education (use Minerva /api/minerva/enrich instead)
- —Free or unauthenticated access — requires micropayment
Quick start
POST https://stableenrich.dev/api/clado/contacts-enrich
Content-Type: application/json
{
"linkedin_url": "https://www.linkedin.com/in/satyanadella",
"email_enrichment": true,
"phone_enrichment": true
}Example
Request
{
"linkedin_url": "https://www.linkedin.com/in/satyanadella",
"email_enrichment": true,
"phone_enrichment": true
}Response
{
"data": [
{
"error": false,
"social": [
{
"link": "https://twitter.com/satyanadella",
"type": "twitter",
"rating": 90
}
],
"contacts": [
{
"type": "email",
"value": "satya@example.com",
"rating": 85,
"subType": "personal"
},
{
"type": "phone",
"value": "+14155551234",
"rating": 72,
"subType": "mobile"
}
]
}
]
}Endpoint
Quality
The specific endpoint path `/api/clado/linkedin-scrape` returned 404 during probing and is not present in the OpenAPI spec. The documented equivalent `/api/clado/contacts-enrich` has full schema, pricing, and response definitions. Score reflects that the listed URL appears non-functional while the underlying capability exists at a different path.
Warnings
- —The endpoint /api/clado/linkedin-scrape returned 404 on HEAD and GET probes — it is not live at this path
- —This path does not appear in the published OpenAPI spec; the documented path is /api/clado/contacts-enrich
- —Callers should use /api/clado/contacts-enrich instead of /api/clado/linkedin-scrape
- —Personal data enrichment endpoint — may be subject to privacy regulations (GDPR, CCPA)
Citations
- —Clado contacts-enrich endpoint is priced at $0.20 per requesthttps://stableenrich.dev
- —Clado contacts-enrich accepts linkedin_url, email, or phone and returns contacts and social arrayshttps://stableenrich.dev/docs
- —Clado is useful as a fallback when Apollo doesn't return personal emails or phone numbershttps://stableenrich.dev
- —Payments are processed on Base mainnet (eip155:8453), Solana, or Tempohttps://stableenrich.dev/docs