# Clado Deep Research via Locus x402

> Clado Deep Research via Locus x402 is a paid API for AI agents from clado.x402.paywithlocus.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Performs deep research on people matching a search query, enriching LinkedIn profiles for lead generation with optional company-level filtering.

## Facts

- Endpoint: POST https://clado.x402.paywithlocus.com/clado/deep-research
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/clado-deep-research-via-locus-x402-b7be6e45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1uA7SrJfBYrB9HrgpkjWq

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability clado-deep-research-via-locus-x402-b7be6e45 -d '<json body>'
```

Example prompt: Use Clado to deep research up to 20 people who are 'VP of Engineering at Series B SaaS startups', filtered to companies at linkedin.com/company/stripe and linkedin.com/company/plaid, so I can build a targeted outreach list.

## When to prefer this

Choose this endpoint when you need comprehensive, deeply researched people profiles for B2B lead generation, sales prospecting, recruiting, or partner discovery — especially when you want to restrict results to specific companies via LinkedIn company URLs. It is preferable over basic people-search endpoints when you need enriched, research-grade data rather than shallow contact lookups. Best for batch research tasks where latency is acceptable in exchange for depth.

## Known failure modes

- Empty results if query is too narrow or no matching profiles exist
- Payment failure if USDC balance is insufficient or x402 payment protocol fails
- Rate limiting or quota errors if too many concurrent requests are made
- Partial results if limit is set very high and not enough profiles are found
- Invalid LinkedIn company URL format causing filter to be ignored or return an error
- Async result not yet ready — agent must poll the statusUrl for completion

## How this service works

Locus public pay-per-use API

## Output

A JSON object with a data field containing enriched people profiles gathered through deep research, including LinkedIn-sourced information relevant to the query. Also includes payment settlement details (0.001 USDC), a request ID, and a status URL for async result polling.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "number",
   "description": "Max profiles to research (default 30)"
  },
  "query": {
   "type": "string",
   "description": "Search query"
  },
  "hard_filter_company_urls": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "LinkedIn company URLs to restrict results to specific organizations"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/clado-deep-research-via-locus-x402-b7be6e45/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from clado.x402.paywithlocus.com](https://www.zero.xyz/host/clado.x402.paywithlocus.com/llms.txt)