MPPtempoquality 0.50

Check the status of an asynchronous Clado deep research job via pay-per-call MPP.

Price
$0.003 / call
Protocol
mpp
Verified
no
Endpoint
https://clado.mpp.paywithlocus.com/clado/deep-research-status

What it does

The Clado Deep Research Status endpoint lets you poll the progress and retrieve results of a previously submitted deep research job. Deep research is an asynchronous people-search workflow offered by Clado (clado.ai) that finds and enriches LinkedIn profiles matching a query. After launching a job via the `/clado/deep-research` endpoint, you call `/clado/deep-research-status` with the returned `jobId` to check whether the job is complete and to page through results.

This endpoint is part of a broader Clado API suite exposed through the Locus MPP (Micropayment Protocol) gateway. The suite includes people search, LinkedIn profile scraping, contact enrichment (email/phone), post-reaction harvesting, and bulk contact operations. Each call is settled on Tempo L2 using pathUSD (6 decimals). The deep-research-status endpoint charges a fixed 3 000 base units per call, which equals $0.003 (three-tenths of a cent). The request body requires a `jobId` (string) and optionally accepts `page` and `page_size` for pagination.

Note: the probe did not receive a 402 challenge when hitting this specific endpoint with HEAD/GET — the endpoint is POST-only, so the probe's HEAD/GET attempts returned 404. The OpenAPI spec clearly documents the endpoint as a POST with a 402 payment flow, and the broader Locus MPP gateway is responding. The endpoint should be considered live for POST requests.

Capabilities

deep-research-statusasync-job-pollingpeople-searchlinkedin-enrichmentlead-generationpaginationmpp-tempo-settlement

Use cases

  • —Polling a long-running people-search job to know when enriched results are ready
  • —Paginating through deep research results after the job completes
  • —Building automated lead-generation pipelines that launch research and periodically check status
  • —Integrating Clado deep research into agent workflows that need async task tracking

Fit

Best for

  • —Agents orchestrating multi-step lead-generation workflows
  • —Checking completion of asynchronous LinkedIn people-search jobs
  • —Paginating large result sets from deep research runs

Not for

  • —Launching a new deep research job (use /clado/deep-research instead)
  • —Real-time synchronous people lookups (use /clado/search)
  • —Non-LinkedIn data enrichment

Quick start

curl -X POST https://clado.mpp.paywithlocus.com/clado/deep-research-status \
  -H "Content-Type: application/json" \
  -d '{"jobId": "abc123", "page": 1, "page_size": 10}'

Example

Request

{
  "page": 1,
  "jobId": "abc123",
  "page_size": 10
}

Endpoint

URLhttps://clado.mpp.paywithlocus.com/clado/deep-research-status
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.50/ 1.00

The OpenAPI spec provides a clear schema, pricing, and endpoint description, but no response schema or examples are available. The probe returned 404 because it used HEAD/GET on a POST-only endpoint, so liveness is inferred rather than confirmed. No crawled documentation was retrieved.

Warnings

  • —Probe returned 404 on HEAD and GET; endpoint is POST-only so liveness could not be directly confirmed
  • —No response schema documented — callers must discover the response shape empirically
  • —Currency address 0x20c0…b9537d11c60e8b50 is assumed to be pathUSD (6 decimals) based on Tempo L2 convention; not independently verified
  • —External docs at https://docs.clado.ai and https://beta.paywithlocus.com/mpp/clado.md were not crawled

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 17:18:02Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/XTDHt6
Check the status of an asynchronous Clado deep research job via pay-per-call MPP. — Clawmart · Clawmart