> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pixiegtm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lead Finder

> Find contact-ready people and companies for Outbound.

Lead Finder is Pixie's contact-oriented discovery surface. It searches sources
such as LinkedIn People and Hiring.cafe, then turns strong
identities into workspace Leads that can be reviewed for Outbound.

## How Lead Finder Fits In

* Pixie uses your company and ICP context to focus each search.
* Runs collect and deduplicate contact-oriented results.
* Strong identities are saved as canonical Leads for the workspace.
* Static lead imports also appear in Lead Finder.
* Contact-ready results can be prepared as a draft Outbound execution.
* Outbound launch remains approval-gated.

<Note>
  Use `/api/lead-finder` for Lead Finder API calls.
</Note>

## Lead Finder Sources

Each search targets exactly one source. `maxQueries` is the largest number of
seed queries the source plan may contain.

| `sourceId` | What it collects | `maxQueries` |
| - | - | - |
| `linkedin_people` | Position and ICP-based LinkedIn people search. | 25 |

### LinkedIn People Targeting Fields

`linkedin_people` is the only source that accepts structured targeting on the
source plan. Sending any of these fields with another `sourceId` is rejected as
invalid.

| Field | Purpose |
| - | - |
| `personCriteria` | Up to 12 `current_title` criteria, each with up to 12 title values. |
| `companyCriteria` | Up to 12 company criteria; separate entries are AND-combined, so OR alternatives belong in one entry. |
| `companySize` | Headcount bound with `min`, `max`, or both. |
| `geography` | Explicit `countryCodes` (ISO-3166 alpha-2) with optional `cityNames`. |
| `resultTarget` | `{ "mode": "count", "count": N }` for a fixed volume, or `{ "mode": "all" }`. |
| `recurrence` | `finite` for a one-time sweep, `monitoring` to keep collecting. |
| `rankedCompanyCohort` | Restricts results to a ranked company cohort. |

`linkedin_people` keyword phrases may run up to 16 words.

### Reading Available Sources

```bash theme={null}
curl -s -H "Authorization: Bearer $PIXIE_API_KEY" \
  "https://app.pixie.ai/api/lead-finder/sources"
```

```json theme={null}
{
  "sources": [
    {
      "sourceId": "linkedin_people",
      "description": "Position and ICP-based LinkedIn people search backed by GetLeads.",
      "eligible": true,
      "ineligibleReason": null,
      "maxQueries": 25,
      "queryGuidance": "Provide concise source-native buyer-evidence queries."
    }
  ]
}
```

The endpoint returns `409` with code `missing_company_context` until company
context is complete, because Pixie cannot focus a search without it.

### Creating a Search on a Source

```bash theme={null}
curl -s -X POST -H "Authorization: Bearer $PIXIE_API_KEY" \
  -H "Content-Type: application/json" \
  "https://app.pixie.ai/api/lead-finder" \
  -d '{
    "title": "Series A RevOps leaders in the US",
    "intent": "Find RevOps leaders who own GTM reporting at Series A companies",
    "sourcePlan": {
      "sourceId": "linkedin_people",
      "query": ["revenue operations leader"],
      "reason": "RevOps leaders own GTM reporting tooling decisions",
      "personCriteria": [
        {
          "id": "revops-titles",
          "kind": "current_title",
          "values": ["Head of Revenue Operations", "RevOps Lead"]
        }
      ],
      "companySize": { "min": 20, "max": 200 },
      "geography": { "mode": "explicit", "countryCodes": ["US"] }
    }
  }'
```

## Related Concepts

<CardGroup cols={2}>
  <Card title="Outbound" icon="send" href="/core-concepts/campaigns">
    Turn contact-ready Lead Finder results into sequenced outreach.
  </Card>
</CardGroup>