Enrich contact info (email, phone, social) from a LinkedIn URL, email, or phone number at $0.20/request.
What it does
The Clado Contacts Enrich endpoint on StableEnrich returns email addresses, phone numbers, and social media links given exactly one of: a LinkedIn profile URL, an email address, or a phone number. It is part of the StableEnrich platform, which aggregates multiple data providers behind a single pay-per-request interface with no subscriptions or API keys required.
The endpoint accepts a POST request with a JSON body containing one lookup key (`linkedin_url`, `email`, or `phone`) and optional boolean flags `email_enrichment` and `phone_enrichment` to request additional contact data. The response includes an array of contact records, each with a type (email or phone), value, confidence rating (0–100), and optional subType, plus an array of social profile links with their own ratings. Pricing is $0.20 per request, settled via x402 or MPP (Tempo method with pathUSD). The endpoint is documented in the StableEnrich OpenAPI spec and guidance notes recommend using Clado as a fallback when Apollo doesn't return personal emails or phone numbers, and using Minerva for LinkedIn profile data like experience and education instead.
Payments are processed on Base mainnet (eip155:8453), Solana, or Tempo. No authentication credentials are needed beyond the micropayment. The full request and response schemas are published in the OpenAPI 3.1.0 spec served by the provider.
Capabilities
Use cases
- —Find personal email and phone for a prospect given their LinkedIn URL
- —Reverse-lookup a phone number to discover associated email addresses and social profiles
- —Enrich a lead list with verified contact details before outreach
- —Supplement Apollo or Minerva results when personal contact info is missing
- —Build a contact database from LinkedIn profile URLs
Fit
Best for
- —Sales teams needing personal email/phone from LinkedIn profiles
- —AI agents performing autonomous lead enrichment workflows
- —Developers who want pay-per-call contact data without subscriptions
- —Enrichment pipelines that need a fallback source for personal contact info
Not for
- —Bulk LinkedIn profile scraping (experience, education, skills) — use Minerva instead
- —B2B company-level enrichment — use Apollo org-enrich instead
- —Free or high-volume low-cost lookups — at $0.20/request this is a premium source
Quick start
POST https://stableenrich.dev/api/clado/contacts-enrich
Content-Type: application/json
{
"linkedin_url": "https://www.linkedin.com/in/satyanadella"
}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": "+14255551234",
"rating": 72,
"subType": "mobile"
}
]
}
]
}Endpoint
Quality
Full OpenAPI 3.1.0 schema with request/response definitions, clear pricing ($0.20/request), documented payment protocols (x402 + MPP/Tempo), and detailed guidance. The probe returned 405 on HEAD/GET (expected for a POST-only endpoint) rather than a 402 challenge, which slightly lowers confidence in live-status verification but is consistent with method routing. No actual 200 response sample was captured.
Warnings
- —Probe did not capture a 402 MPP challenge because HEAD and GET returned 405; the endpoint is POST-only, so this is expected behavior, not a sign of downtime.
- —Example response is synthetic based on the schema — no real response was captured during probing.
- —This endpoint handles personal contact information (PII); ensure compliance with applicable privacy regulations.
Citations
- —Clado Contacts Enrich costs $0.20 per requesthttps://stableenrich.dev
- —Must provide exactly one of: linkedin_url, email, or phonehttps://stableenrich.dev
- —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
- —Supports x402 and MPP (method: tempo, intent: charge) payment protocolshttps://stableenrich.dev