Skip to main content
Each surface here starts the same investigation, which you can open in the web app or read through the Atlas API.

People Intelligence

Send a struct to People Intelligence with tier: "xhigh" and the run returns your fields in structured_data, alongside a persistent investigation. scout with graph: true runs the same investigation tooling on Scout’s lighter model. Atlas runs take longer than other tiers, so start them with the async endpoint. GET /v1/jobs/{job_id} does not return a run’s investigation yet, so Atlas runs start and poll on the original routes, which keep working:
The start response and every /job-status response carry the investigation:
Open workspace_url to watch the run in the Atlas section of the Sixtyfour app, or read it through the Atlas API while it is still going.

Request parameters

Atlas runs take the People Intelligence parameters, plus:

Atlas API or People Intelligence

Both start the same investigation, and both take lead_info, struct, research_plan, max_credits, max_minutes, dispatch_id and private. Side by side:

Response

Poll GET /job-status/{task_id}; Job status and callbacks covers polling and statuses on the original routes. A completed Atlas job’s result has the People Intelligence fields, plus:
These three fields read from the investigation, so a later run on it changes what an earlier job returns. Attachment paths in them come back as permanent /v1/media URLs; see Images and attachments. Runs with a struct also return field_confidence: each answered field has its confidence, justification, sources and the graph nodes that support it. See Confidence Scoring.

Declined runs

When the agents decline to research a subject, the run ends before any research. The job still reports completed: result.notes starts with Declined: and gives the agents’ reason, and structured_data repeats your lead_info instead of answering your struct. A new investigation reads failed and gets no report. Check notes before you store structured_data. The agents do not research people under 18. When they find the subject is a minor, the run stops at that point, even partway through. Its notes start with Declined: the subject is a minor, and nothing it found is returned. The run’s price is not charged; paid lookups it made before that point still are. The result has no investigation_id or workspace_url. When the investigation holds nothing but this run’s work, it is also removed from the app; an investigation with earlier work is kept.

Bulk Intelligence

POST /bulk-intelligence/people accepts tier: "xhigh" and runs one investigation per row on the default budget. graph, max_credits, max_minutes and investigation_id aren’t accepted in bulk config. To set a budget per lead, start each run from People Intelligence instead. In the web app, Upload CSV starts one investigation per row with a budget you choose.

Workflows

Set the tier of an Enrich People block to XHigh to run an investigation for each row. In a workflow definition, set "tier": "xhigh" in the lead_enrichment block’s specs. Each row creates its own investigation on the default budget, and your return fields become columns. See Credit Costs for what a row costs. The block also adds: Place filters before the block so only the rows worth an investigation reach it.

Webhooks

Pass webhook_url to POST /people-intelligence-async to receive the result when the run finishes. See Outgoing Webhooks. To follow a run started with POST /v1/atlas/investigations, poll GET /job-status/{task_id} or stream its events.

MCP

The Sixtyfour MCP server lets a coding assistant start and read investigations. The Atlas tools appear only when your organization has Atlas enabled.
  1. sixtyfour_atlas_start starts an XHigh investigation on the default budget. Pass the subject (any of name, email, phone, username, ip_address, profile_url, company, domain, or a free-text query), a request_id as the idempotency key, an optional objective, and private: true to make the investigation visible only to you.
  2. sixtyfour_atlas_status polls the task until it finishes.
  3. sixtyfour_atlas_inspect reads the investigation’s summary, or a page of its findings, links or files.
  4. sixtyfour_atlas_file reads a chunk of a text file that sixtyfour_atlas_inspect listed.
sixtyfour_atlas_list lists your organization’s investigations. The tools read text only, so open the investigation in the web app or use the Atlas API for images and other attachments.