Retrieve structured LinkedIn profile data via pay-per-call MPP endpoint
What it does
Clado LinkedIn Profile is one endpoint in the Clado suite, a people-search and LinkedIn-enrichment service exposed through the Locus MPP (Micropayment Protocol). The `/clado/linkedin-profile` endpoint accepts a LinkedIn profile URL and returns profile data. Payment is settled per-call via Tempo (pathUSD on Tempo L2) at 13,000 base units, which equals $0.013 per request (pathUSD uses 6 decimals).
The broader Clado service available at the same origin includes people search, deep research for lead generation, LinkedIn scraping, contact enrichment (email and phone), post-reaction retrieval, and bulk contact enrichment. Each endpoint has its own pricing — search and deep research charge $0.01 per result, contact enrichment ranges from $0.04–$0.14, and LinkedIn scraping costs $0.023 per call. All endpoints use POST with JSON request bodies and settle payments via the Tempo method on the MPP protocol.
The probe did not return a 402 challenge on HEAD or GET for this specific endpoint, which is expected since the OpenAPI spec defines it as a POST-only route. The OpenAPI schema is well-defined with clear request parameters. No response schema is documented, so the exact shape of returned profile data is unknown. External documentation is referenced at docs.clado.ai and clado.ai but was not crawled.
Capabilities
Use cases
- —Retrieve structured profile data from a LinkedIn URL for CRM enrichment
- —Build lead generation pipelines that enrich prospects with LinkedIn data
- —Automate sales prospecting by looking up LinkedIn profiles programmatically
- —Enrich contact databases with up-to-date LinkedIn profile information
Fit
Best for
- —Sales and marketing teams needing LinkedIn profile data at scale
- —AI agents performing automated lead research
- —Developers building CRM integrations that require LinkedIn enrichment
Not for
- —Scraping LinkedIn in violation of LinkedIn's terms of service — users must assess compliance
- —Use cases requiring free or high-volume bulk access without per-call payment
- —Non-LinkedIn social media profile lookups
Quick start
curl -X POST https://clado.mpp.paywithlocus.com/clado/linkedin-profile \
-H "Content-Type: application/json" \
-d '{"linkedin_url": "https://www.linkedin.com/in/example-person"}'Example
Request
{
"linkedin_url": "https://www.linkedin.com/in/example-person"
}Endpoint
Quality
The OpenAPI spec is well-structured with clear request schemas and pricing metadata for all endpoints. However, no response schemas are documented, the probe did not capture a 402 challenge (expected for POST-only routes probed with HEAD/GET), and the crawl returned only 404 error pages. External docs at docs.clado.ai were not fetched.
Warnings
- —No 402 challenge captured — endpoint is POST-only and was probed with HEAD/GET; liveness not confirmed
- —No response schema documented in OpenAPI spec; returned data shape is unknown
- —External documentation at docs.clado.ai and clado.ai was not crawled
- —Users should independently assess LinkedIn ToS compliance for their use case
Citations
- —The /clado/linkedin-profile endpoint charges 13,000 base units in pathUSD (Tempo) per callhttps://clado.mpp.paywithlocus.com
- —The broader Clado service includes search, deep research, contacts, scrape, post-reactions, and bulk-contacts endpointshttps://clado.mpp.paywithlocus.com
- —External documentation is referenced at docs.clado.ai and clado.aihttps://clado.mpp.paywithlocus.com