For developers building intelligence workflows
Turn a person or company identifier into structured intelligence. Define what you need to know, choose the depth of research, and build the findings into your own workflow.
You define the fields.
The agents do the research.
curl https://api.sixtyfour.ai/people-intelligence \
-H "x-api-key: $SIXTYFOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"lead_info": {
"name": "Lena Ortiz",
"company": "Oakvane Labs"
},
"struct": {
"current_role": "Current role and organization",
"professional_history": "Career history with sources"
},
"tier": "low"
}'Research API
Fixed datasets answer the questions someone else chose. Sixtyfour lets you define a research schema for a person or company, so you can request the context your product needs and receive it in a structured response.
Start with known context, define the fields you need, and choose how the research runs.
Step 01
Start with lead_info for a person or target_company for a business.
Better starting context helps distinguish the intended subject from similarly named people or companies.
Step 02
Use struct to describe the fields you want the research to return.
Field descriptions tell the agents what to research. Choose fields that answer a specific product question.
Step 03
Use synchronous, asynchronous or bulk endpoints to fit the size of the job.
Check the endpoint documentation for response shapes, limits, error handling and access requirements.
In your workflow
Research professional history, public profiles and other requested attributes from a known identity.
Investigate a business and the people connected to it using a custom research schema.
Run longer jobs asynchronously or process batches through the documented bulk endpoints.
Start building
The schema is the brief. Replace the subject and field descriptions with the information your workflow needs. Keep your API key on your server.
Review authentication, request parameters, errors and the current endpoint specification.
A little more context
No. The struct object describes the fields you want the agents to research. Write clear descriptions for each field and validate the response in your application.
The API supports different research depths. Start with the documented default and compare results on representative subjects. Higher tiers perform deeper research; high-tier intelligence requires enterprise access. See the docs for current access and pricing.
Yes. Dedicated bulk intelligence endpoints accept CSV, JSON and NDJSON uploads. They return a task identifier so your application can track the background job.
Make authenticated calls from your server. Do not embed the key in client-side JavaScript or public repositories. The quick start documents the x-api-key header.
