Skip to main content
This page uses the original routes, which keep working. For new integrations, see People Intelligence.

Request parameters

Atlas runs (xhigh, or scout with graph: true) accept more parameters. The async start response lists unrecognized body keys in unrecognized_fields.

Tiers

The tier parameter controls research depth and cost.

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:
Specific descriptions return better results: "The individual's primary work email" beats "email". For supported types and casting, see Fields & Type Casting.

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:
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

Atlas (xhigh)

xhigh is a structured version of Atlas, 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 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.
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.

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.
Request
Response
See Credit Costs.

Pricing

See Credit Costs for the price of each tier.