Scrape LinkedIn profile data via pay-per-call MPP endpoint settled on Tempo L2.
What it does
Clado's Scrape LinkedIn endpoint (`/clado/scrape`) accepts a LinkedIn profile URL and returns scraped profile data. It is one of several endpoints in the Clado suite, which also includes people search, deep research, contact enrichment, bulk contact enrichment, LinkedIn profile lookup, and post-reaction retrieval — all exposed through the Locus MPP (Micropayment Protocol) gateway.
This specific endpoint charges 23,000 base units of pathUSD (6 decimals) per call, which works out to $0.023 per scrape. Payment is settled via the Tempo method (pathUSD on Tempo L2) with a one-shot "charge" intent, meaning each request is independently paid. The request body requires a single field: `linkedin_url`, the full URL of the LinkedIn profile to scrape.
The broader Clado service offers people search at $0.01/result, deep research at $0.01/result, contact enrichment at $0.04–$0.14 per contact, LinkedIn profile retrieval at $0.013, and post-reaction scraping at $0.013. Documentation is referenced at https://docs.clado.ai and https://clado.ai. Note that the probe did not receive a 402 challenge on HEAD/GET for this endpoint (it returned 404), which is expected since the endpoint only accepts POST requests. The OpenAPI spec confirms the endpoint exists and defines its schema.
Capabilities
Use cases
- —Scraping a LinkedIn profile to extract structured professional data for CRM ingestion
- —Enriching lead lists with LinkedIn profile details before outreach
- —Building automated pipelines that gather prospect information from LinkedIn URLs
- —Feeding LinkedIn profile data into AI agents for personalized outreach generation
Fit
Best for
- —Sales teams needing on-demand LinkedIn profile data without a subscription
- —AI agents that need programmatic access to LinkedIn profile information
- —Developers building lead-generation workflows with pay-per-use pricing
Not for
- —High-volume bulk scraping where a flat-rate subscription would be cheaper
- —Use cases requiring real-time LinkedIn activity monitoring or webhooks
- —Scraping non-LinkedIn social profiles
Quick start
curl -X POST https://clado.mpp.paywithlocus.com/clado/scrape \
-H "Content-Type: application/json" \
-d '{"linkedin_url": "https://www.linkedin.com/in/example-profile"}'Example
Request
{
"linkedin_url": "https://www.linkedin.com/in/example-profile"
}Endpoint
Quality
The OpenAPI spec provides clear request schemas, pricing metadata, and endpoint descriptions for the full Clado suite. However, no response schemas are documented, no example responses are available, the probe returned 404 (expected for POST-only endpoint but no live 402 was captured), and the crawl pages yielded no additional documentation content.
Warnings
- —No 402 challenge was captured during probing — endpoint returned 404 on HEAD/GET, likely because it only accepts POST. Liveness via POST was not confirmed.
- —No response schema is documented in the OpenAPI spec; the structure of returned data is unknown.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on the Tempo method context; this is not explicitly confirmed in the spec.
- —External docs at https://docs.clado.ai and https://clado.ai were not crawled and may contain additional details.
Citations
- —The /clado/scrape endpoint charges 23,000 base units via Tempo with intent 'charge'https://clado.mpp.paywithlocus.com
- —The endpoint requires a linkedin_url field in the POST bodyhttps://clado.mpp.paywithlocus.com
- —Clado provides people search, LinkedIn enrichment, and deep research for lead generationhttps://clado.mpp.paywithlocus.com
- —API reference docs are at https://docs.clado.aihttps://clado.mpp.paywithlocus.com