Company Intelligence

Turn a company name or domain into a complete, sourced company profile, with the right contacts attached, for account research, CRM enrichment, lead qualification or diligence.

curl -X POST "https://api.sixtyfour.ai/company-intelligence" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  --max-time 900 \
  -d '{
    "target_company": {
      "company_name": "Pacific View Studios",
      "website": "https://pacificview.studio"
    },
    "struct": {
      "instagram_url": "The company'\''s primary Instagram profile URL",
      "headquarters": "City and country of the headquarters"
    },
    "tier": "medium",
    "find_people": true,
    "people_focus_prompt": "The founder and the head of operations"
  }'

import requests

response = requests.post(
    "https://api.sixtyfour.ai/company-intelligence",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "target_company": {
            "company_name": "Pacific View Studios",
            "website": "https://pacificview.studio"
        },
        "struct": {
            "instagram_url": "The company's primary Instagram profile URL",
            "headquarters": "City and country of the headquarters"
        },
        "tier": "medium",
        "find_people": True,
        "people_focus_prompt": "The founder and the head of operations"
    },
    timeout=900
)
response.raise_for_status()
result = response.json()

const response = await fetch("https://api.sixtyfour.ai/company-intelligence", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    target_company: {
      company_name: "Pacific View Studios",
      website: "https://pacificview.studio"
    },
    struct: {
      instagram_url: "The company's primary Instagram profile URL",
      headquarters: "City and country of the headquarters"
    },
    tier: "medium",
    find_people: true,
    people_focus_prompt: "The founder and the head of operations"
  }),
  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
`target_company`	object	required	What you already know about the company: `company_name`, `domain`, `website`, `linkedin`, `location`, or other keys.
`struct`	object	required	The fields to return. See Using the `struct` field.
`tier`	string	`low`	Research depth. See Tiers.
`research_plan`	string	—	Plain-language guidance on where and how to look. Up to 100,000 characters.
`find_people`	boolean	`false`	Also find people at the company and return them in `structured_data.leads`.
`people_focus_prompt`	string	—	Who to find when `find_people` is on, for example `"The VP of Marketing and the CTO"`.
`lead_struct`	object	—	Fields to return for each person in `structured_data.leads`, in the same format as `struct`.
`full_org_chart`	boolean	`false`	Return a department-level view of the company’s people in `org_chart`.
`field_confidence`	boolean	off	Return a confidence score, justification and sources for every field. See Confidence Scoring.
`webhook_url`	string (HTTPS)	—	Receive the result by POST when the job finishes. Sync calls send it too. See Outgoing Webhooks.

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 firmographic enrichment.	All orgs
`medium`	Deeper research: more sources, more fields filled.	All orgs
`high`	Open-source intelligence (OSINT) investigation: deep, recursive research across the open web, public records, directories and specialist sources. Built for high-stakes accounts and diligence.	On request

Company Intelligence has no scout or xhigh tier. See People Intelligence. To investigate a company in depth, use Atlas.

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:

{
  "struct": {
    "instagram_url": "The company's primary Instagram profile URL",
    "headquarters": {"description": "City and country of the headquarters", "type": "str"}
  }
}

Specific descriptions return better results: "The company's primary Instagram profile URL" beats "social". For supported types and casting, see Struct & Type Casting.

`find_people` vs `full_org_chart`

find_people finds specific people at the company. Pair it with people_focus_prompt to target roles or seniority, and with lead_struct to choose what is returned for each person.
full_org_chart returns a compact view of employees grouped by department, capped per department. It shows broad coverage of who works where; it is not a reporting tree or an exhaustive employee list.

`research_plan` vs `people_focus_prompt`

research_plan is methodology: where to look, for example "Check the About page and the LinkedIn company page".
people_focus_prompt is criteria: who to find, for example "The VP of Marketing and the CTO".

Response

Field	Type	Description
`structured_data`	object	One key per `struct` field, with the value found. It also echoes every key you sent in `target_company`, and holds `leads` when `find_people` is on.
`structured_data.leads`	array	People found when `find_people` is on. With `lead_struct`, each lead has your fields. Without it, each lead has `name`, `email`, `company`, `title`, `phone`, `linkedin`, `location` and a `score` (0–10): how likely the person is to help or respond.
`notes`	string	A short research summary.
`references`	object	Source URL → what was found there.
`confidence_score`	number (0–10)	Overall quality, consistency and correctness of the result. Omitted when the response carries `field_confidence`.
`org_chart`	object or null	The department-level view when `full_org_chart` is on, otherwise `null`.
`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.
`findings`	array of strings	Deprecated: a free-text log of what the research found. Read `structured_data` instead.

Async and timeouts

Company Intelligence runs take up to 10 minutes.

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

POST /company-intelligence-async takes the same body 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. Company Intelligence takes no dispatch_id, so a repeated async start also runs and charges again: keep the task_id from the first response.

Bulk

To enrich a file of companies in one job, use Bulk Intelligence.

Errors

For error responses (400, 403, 422, etc.), see Handling Errors.

Pricing

See Credit Costs for the price of each tier.

Get Started

Intelligence API

Atlas

Lattice

Search API

Workflows API

Monitors API

Webhooks

Developer Tools

Request parameters

Tiers

Using the `struct` field

`find_people` vs `full_org_chart`

`research_plan` vs `people_focus_prompt`

Response

Async and timeouts

Bulk

Errors

Pricing

​Request parameters

​Tiers

​Using the struct field

​Choosing related parameters

​find_people vs full_org_chart

​research_plan vs people_focus_prompt

​Response

​Async and timeouts

​Bulk

​Errors

​Pricing

Request parameters

Tiers

Using the `struct` field

Choosing related parameters

`find_people` vs `full_org_chart`

`research_plan` vs `people_focus_prompt`

Response

Async and timeouts

Bulk

Errors

Pricing