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

# People Intelligence

> Research a person and return the fields you ask for, with sources and a confidence score.

```bash cURL theme={null}
curl -X POST "https://api.sixtyfour.ai/people-intelligence" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  --max-time 900 \
  -d '{
    "lead_info": {
      "name": "Saarth Shah",
      "company": "Sixtyfour",
      "linkedin": "https://www.linkedin.com/in/saarthshah"
    },
    "struct": {
      "name": "The individual'\''s full name",
      "title": "The individual'\''s current job title",
      "company": "The company the individual works at",
      "linkedin": "LinkedIn URL for the person",
      "website": "Company website URL"
    },
    "tier": "medium"
  }'
```

```python Python theme={null}
import requests

response = requests.post(
    "https://api.sixtyfour.ai/people-intelligence",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "lead_info": {
            "name": "Saarth Shah",
            "company": "Sixtyfour",
            "linkedin": "https://www.linkedin.com/in/saarthshah"
        },
        "struct": {
            "name": "The individual's full name",
            "title": "The individual's current job title",
            "company": "The company the individual works at",
            "linkedin": "LinkedIn URL for the person",
            "website": "Company website URL"
        },
        "tier": "medium"
    },
    timeout=900
)
response.raise_for_status()
result = response.json()
```

```javascript JavaScript theme={null}
const response = await fetch("https://api.sixtyfour.ai/people-intelligence", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    lead_info: {
      name: "Saarth Shah",
      company: "Sixtyfour",
      linkedin: "https://www.linkedin.com/in/saarthshah"
    },
    struct: {
      name: "The individual's full name",
      title: "The individual's current job title",
      company: "The company the individual works at",
      linkedin: "LinkedIn URL for the person",
      website: "Company website URL"
    },
    tier: "medium"
  }),
  signal: AbortSignal.timeout(900_000)
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const result = await response.json();
```

## Request parameters

| Parameter | Type | Default | Description |
| - | - | - | - |
| `lead_info` | object | required | What you already know about the person: any combination of `name`, `title`, `company`, `location`, `linkedin`, `email`, and other keys. |
| `struct` | object | required (optional on Atlas runs) | The fields to return. See [Using the `struct` field](#using-the-struct-field). |
| `tier` | string | `low` | Research depth. See [Tiers](#tiers). |
| `research_plan` | string | None | Plain-language guidance on where and how to look. Up to 100,000 characters. |
| `field_confidence` | boolean | off | Return a confidence score, justification and sources for every field. See [Confidence Scoring](https://docs.sixtyfour.ai/api-reference/endpoint/field-confidence.md). |
| `webhook_url` | string (HTTPS) | None | Receive the result by POST when the job finishes. Sync calls send it too. See [Outgoing Webhooks](https://docs.sixtyfour.ai/api-reference/webhooks/outgoing.md). |
| `dispatch_id` | string (8 to 128 chars) | None | Async only. Idempotency key: a repeat returns the first job and charges nothing. See [Async Jobs](https://docs.sixtyfour.ai/api-reference/legacy.md#sync-calls-and-retries). |
| `private` | boolean | `false` | Show the run's result, status and usage log only to you, or to the key's creator for an API key. Your team must allow private runs. Atlas runs need the async endpoint and a new investigation. |

Atlas runs (`xhigh`, or `scout` with `graph: true`) accept [more parameters](https://docs.sixtyfour.ai/atlas/integrations.md#request-parameters).

The async start response lists unrecognized body keys in `unrecognized_fields`.

## Tiers

The `tier` parameter controls research depth and cost.

| Tier | What it does | Access |
| - | - | - |
| `micro` | Lightweight lookup for very high volume. Up to 10 `struct` fields. | All orgs |
| `low` (default) | Fast, low-cost enrichment. Good for name → email or LinkedIn mapping at scale. | All orgs |
| `medium` | More sources and research iterations. Better for hard-to-find contacts. | All orgs |
| `high` | Open-source intelligence (OSINT) investigation: deep, recursive research across the open web, public records, directories and specialist sources. Built for the hardest prospects and for diligence. | [On request](mailto:support@sixtyfour.ai) |
| `scout` | The full `high` research toolset on a lighter, lower-cost model. Add `graph: true` to run it on [Atlas](https://docs.sixtyfour.ai/atlas/overview.md). | [On request](mailto:support@sixtyfour.ai) |
| `xhigh` | Deepest tier. Runs research with the [Atlas](#atlas-xhigh) engine and returns the requested `struct` fields. Can take much longer than other tiers. | [On request](mailto:support@sixtyfour.ai) |

## Using the `struct` field

The `struct` field defines the data you want back. Each key becomes a field in `structured_data`, and its value tells the agent what to find. Pass a plain-English description or an object with `description` and `type`:

```json theme={null}
{
  "struct": {
    "email": "The individual's primary work email",
    "github_url": {"description": "URL for their GitHub profile", "type": "str"}
  }
}
```

Specific descriptions return better results: `"The individual's primary work email"` beats `"email"`. For supported types and casting, see [Struct & Type Casting](https://docs.sixtyfour.ai/guides/struct-and-type-casting.md).

### Image fields

On the `high` and `xhigh` tiers, a field that asks for an image (a headshot, a logo, a screenshot of a page) comes back as a permanent image URL hosted by Sixtyfour:

```json theme={null}
{"struct": {"headshot": "A recent photo of the person"}}
```

```json theme={null}
{"structured_data": {"headshot": "https://api.sixtyfour.ai/v1/media/v1.eyJt..."}}
```

The URL needs no credentials and stays valid while your data is retained, so it embeds in an `<img>`, CRM record or spreadsheet cell. The source page is listed in `references`. Organizations with customer-managed encryption fetch media from a server with their `x-api-key` header, so their URLs cannot be embedded.

Page screenshots show the source URL and capture time (UTC) in a header above the page. For a printable version, ask for a PDF in the field description, for example `"Printable PDF capture of the source page"`. It comes back as the same kind of media URL, served as a US Letter PDF with the URL, capture time and page number on every page.

## Response

| Field | Type | Description |
| - | - | - |
| `structured_data` | object | One key per `struct` field, with the value found. |
| `notes` | string | A short research summary. |
| `references` | object | Source URL → what was found there. |
| `confidence_score` | number (0 to 10) | Overall quality, consistency and correctness of the result. Omitted when the response carries `field_confidence`. |
| `field_confidence` | object | Per-field confidence when `field_confidence` is on. If no field could be scored, the response carries `confidence_score` instead. See [Confidence Scoring](https://docs.sixtyfour.ai/api-reference/endpoint/field-confidence.md). |
| `connected_sources` | array | The team's [connections](https://docs.sixtyfour.ai/atlas/connections.md#use-it-in-a-run) the answer cites, each with its `connection` name and `connection_id`. Present only when a finding was read from one. |

```json theme={null}
{
  "structured_data": {
    "name": "Saarth Shah",
    "title": "CEO & Co-Founder",
    "company": "Sixtyfour",
    "linkedin": "https://www.linkedin.com/in/saarthshah",
    "website": "https://sixtyfour.ai"
  },
  "notes": "Confirmed current role from the LinkedIn profile and the company site.",
  "references": {
    "https://www.linkedin.com/in/saarthshah": "LinkedIn profile with current title",
    "https://sixtyfour.ai": "Company website"
  },
  "confidence_score": 9
}
```

## Atlas (xhigh)

> [!NOTE]
>
> `xhigh` is a structured version of [Atlas](https://docs.sixtyfour.ai/atlas/overview.md), Sixtyfour's deep investigation product. It runs the same agents and creates the same persistent investigation, then returns your `struct` fields in `structured_data`. See [People Intelligence on Atlas](https://docs.sixtyfour.ai/atlas/integrations.md#people-intelligence) for its parameters and response.

## Async and timeouts

People Intelligence runs take up to 10 minutes; Atlas runs take longer.

* Set sync client timeouts to at least 15 minutes.
* Use `POST /people-intelligence-async` and poll `GET /job-status/{task_id}` in production.

`POST /people-intelligence-async` takes the same body plus `dispatch_id` and returns a `task_id`. See [Async Jobs](https://docs.sixtyfour.ai/api-reference/legacy.md).

> [!WARNING]
>
> A sync call keeps running after your client times out or disconnects, and it is charged when it finishes. A retry starts and charges a second run. To retry safely, use the async endpoint with `dispatch_id`.

## Bulk

To enrich a file of leads in one job, use [Bulk Intelligence](https://docs.sixtyfour.ai/api-reference/legacy/bulk-intelligence.md).

## LinkedIn profile enrichment

`POST /enrich-linkedin` reads one person's LinkedIn profile and extracts the fields you ask for in a single pass, without researching other sources. It is sync only.

| Parameter | Type | Default | Description |
| - | - | - | - |
| `linkedin_url` | string | required | The person's LinkedIn profile URL. |
| `struct` | object | see description | The fields to extract, in the same format as [`struct`](#using-the-struct-field). Without it: `full_name`, `headline`, `summary`, `current_company`, `current_title`, `location`, `email`, `phone`, `skills`, `experience_summary`, `education_summary` and `connections`. |

```json Request theme={null}
{
  "linkedin_url": "https://www.linkedin.com/in/saarthshah",
  "struct": {
    "full_name": "Full name of the person",
    "current_title": "Current job title",
    "current_company": "Current employer"
  }
}
```

```json Response theme={null}
{
  "linkedin_url": "https://www.linkedin.com/in/saarthshah",
  "structured_data": {
    "full_name": "Saarth Shah",
    "current_title": "CEO & Co-Founder",
    "current_company": "Sixtyfour",
    "linkedin_url": "https://www.linkedin.com/in/saarthshah"
  },
  "confidence_score": 9,
  "notes": "Current role taken from the profile's experience section.",
  "elapsed_seconds": 4.2,
  "profile_found": true
}
```

| Field | Type | Description |
| - | - | - |
| `linkedin_url` | string | The URL you sent. |
| `structured_data` | object | One key per `struct` field, plus `linkedin_url`. Values are empty strings when nothing could be extracted. |
| `confidence_score` | integer (0 to 10) | Overall confidence in the extracted values. |
| `notes` | string | A short summary, or why nothing was extracted. |
| `elapsed_seconds` | number | How long the call took. |
| `profile_found` | boolean | `false` when the profile could not be retrieved. |

See [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md).

## Related

* [Batch Processing](https://docs.sixtyfour.ai/guides/batch-processing.md)
* [Async Jobs](https://docs.sixtyfour.ai/api-reference/async-jobs.md)
* [Handling Errors](https://docs.sixtyfour.ai/api-reference/errors.md)
* [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md)

## Pricing

See [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md) for the price of each tier.

> [!NOTE]
>
> For new integrations, see [People Intelligence](https://docs.sixtyfour.ai/api-reference/endpoint/people-intelligence.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.