Sixtyfour Intelligence

Start an async bulk find-phone job and return a task_id for polling. Do not return the task_id as your final answer — poll sixtyfour_enrichment_job_status to completion first. Discovers phone numbers for 1-100 leads in one billable job. Best results need more than a name. If a lead only has a person's name, first use people search, get the person details, then include their LinkedIn URL, current company, or company domain before calling this tool. Poll the returned task_id with sixtyfour_enrichment_job_status. Args: leads: Leads to process (1-100). For a single lead, pass a list of one.

sixtyfour_find_phone_start

Find people similar to seed profiles (lookalike search) — "more people like these". Seeds come from `linkedin_urls` (1-1000 profile URLs) or `csv_text` — the full raw text of the user's seed file. When the user points at a file or a vague list, read it and pass ALL of it rather than a few sampled URLs: more seeds produce a better similarity cohort. The cohort's defining traits (roles, skills, industry, seniority, ...) are inferred automatically; pass `guidance` ONLY for hard requirements the user explicitly stated. Async and billable: capture task_id, poll sixtyfour_find_similar_status until completed, then page ranked people with sixtyfour_find_similar_results. Seed profiles are always excluded from results.

sixtyfour_find_similar_start

Return expanded details for one company from search results. Without include_fields, returns fields derived from the original search context. With include_fields, returns identity fields plus the requested fields (use dot-notation for nested fields, e.g. "key_executives.member_full_name"). Max 20 fields. Args: result_handle: The `result_handle` from a search result item (not raw_document_id). Expires after ~20 minutes; rerun search if expired. include_fields: Field names from sixtyfour_company_get_searchable_fields. If omitted, fields are derived from the original search context.

sixtyfour_company_get_company_details

Return expanded details for one person from search results. Without include_fields, returns fields derived from the original search context. With include_fields, returns identity fields plus the requested fields. Max 20 fields. Args: result_handle: The `result_handle` from a search result item. Expires after ~20 minutes; rerun search if expired. include_fields: Field names from sixtyfour_people_get_searchable_fields.

sixtyfour_people_get_person_details

Return every searchable field, nested path, query limit, and supported operator. Call once at the start of a session. Use the returned field names exactly in queries — unknown fields cause errors. Nested fields (e.g. funding_rounds.amount_raised) require $elemMatch when queried.

sixtyfour_company_get_searchable_fields

Return every searchable field, nested path, query limit, and supported operator for people profiles. Call once at the start of a session. Use the returned field names exactly in queries — unknown fields cause errors.

sixtyfour_people_get_searchable_fields

Fetch the next page of results from a previous company search. Returns the same shape as sixtyfour_company_search (with result_handles, previews, and a new next_cursor if more pages exist). Cursors expire after ~20 minutes; if expired, rerun the original search. Args: cursor: The `next_cursor` value from a sixtyfour_company_search or sixtyfour_company_next_page response. Billable: 0.1 credit per result returned (a 100-row page costs 10 credits). Each response includes `charge_credits`, the amount charged for that page.

sixtyfour_company_next_page

Fetch the next page of results from a previous people search. Returns the same shape as sixtyfour_people_search. Cursors expire after ~20 minutes; if expired, rerun the original search. Args: cursor: The `next_cursor` value from a sixtyfour_people_search or sixtyfour_people_next_page response. Billable: 0.1 credit per result returned (a 100-row page costs 10 credits). Each response includes `charge_credits`, the amount charged for that page.

sixtyfour_people_next_page

Page the ranked matches of a completed similarity search. Pass search_id for the first page, then the returned next_cursor (without search_id) for later pages. Each row carries a 0-100 similarity score, its rank, and the matched signals explaining why the person is similar. Billable per returned row.

sixtyfour_find_similar_results

Start an async Company Intelligence job and return a task_id for polling. Do not return the task_id as your final answer — poll sixtyfour_enrichment_job_status to completion first. Use this to enrich one company. `target_company` should contain identifiers such as company_name, website, domain, LinkedIn URL, or location. `struct` is required. Each key becomes a field in `structured_data`. Each value can be a plain-English description or an object like {"description": "Approximate employee count", "type": "int"}. Use `find_people` with `people_focus_prompt` for targeted people discovery. Use `full_org_chart` for broad department-level employee visibility. Example struct: { "company_name": "Name of the company", "industry": "Primary industry", "employee_count": {"description": "Approximate employee count", "type": "int"}, "uses_shopify": "True if the company uses Shopify" } Args: target_company: Company identifiers. struct: Company output fields to research and return. find_people: Whether to discover associated people. people_focus_prompt: Criteria for people discovery, e.g. "Find the CTO and VP of Marketing". lead_struct: Output schema for each discovered person. research_plan: Optional methodology for where/how to research. tier: Research depth/cost tier: micro, low, medium, or high. full_org_chart: Whether to return a compact org chart grouped by department.

sixtyfour_company_intelligence_start

Start an async People Intelligence job and return a task_id for polling. Do not return the task_id as your final answer — poll sixtyfour_enrichment_job_status to completion first. Use this to enrich one person or lead. `lead_info` should contain any known identifiers such as name, email, company, title, location, website, or LinkedIn URL. `struct` is required. Each key becomes a field in `structured_data`. Each value can be a plain-English description or an object like {"description": "The individual's primary work email", "type": "str"}. Example struct: { "name": "The individual's full name", "email": {"description": "Primary work email address", "type": "str"}, "linkedin": "LinkedIn URL for the person", "github_notes": "Detailed notes on their GitHub profile" } Args: lead_info: Lead identifiers. struct: Output fields to research and return. research_plan: Optional methodology for where/how to research. tier: Research depth/cost tier: micro, low, medium, or high.

sixtyfour_people_intelligence_start

Start an async bulk reverse-email lookup job and return a task_id for polling. Do not return the task_id as your final answer — poll sixtyfour_enrichment_job_status to completion first. Resolves the person behind each email address for 1-100 leads in one billable job. Each lead must include an `email` field. Poll the returned task_id with sixtyfour_enrichment_job_status. Args: leads: Leads to process (1-100), each with an `email` field.

sixtyfour_reverse_email_start

Start an async bulk reverse-phone lookup job and return a task_id for polling. Do not return the task_id as your final answer — poll sixtyfour_enrichment_job_status to completion first. Resolves the person behind each phone number for 1-100 leads in one billable job. Each lead must include a `phone` field. Poll the returned task_id with sixtyfour_enrichment_job_status. Args: leads: Leads to process (1-100), each with a `phone` field.

sixtyfour_reverse_phone_start

Search companies with a simple_filters query and return compact smart previews. Each result includes a `result_handle` (for get_company_details) and the response includes `next_cursor` and `has_more` (for next_page). Both expire after ~20 minutes. Args: query: MongoDB-style filter dict (not a text string). Bare values imply $eq. Operators: $ne, $gt, $gte, $lt, $lte, $in, $nin, $exists, $match (any token), $phrase (exact phrase), $elemMatch, $or, $and, $not, $nor, $search, $sort, $limit. page_size: Results per page. max_results: Cap on total results across all pages, not just the current page. include_fields: Field names to hint the preview planner. Not guaranteed — previews are budget-constrained. For full nested data, use get_company_details. If a search returns 0 results, use sixtyfour_company_explore_field_values to check valid values for categorical fields. On 400 errors, call sixtyfour_company_get_searchable_fields to verify field names. To look up a company by domain, filter on website_domain. Linking to people: the company's string source_id and the people field currentCompanies.company.companyId represent the same LinkedIn company ID. Convert source_id to a JSON number for the people filter. Examples: {"industry": "SaaS"} {"employees_count": {"$gte": 100, "$lte": 5000}} {"hq_country_iso2": "US", "industry": "SaaS", "employees_count": {"$gte": 50}} {"industry": "SaaS", "$sort": {"employees_count": -1}, "$limit": 100} {"$or": [{"industry": "SaaS"}, {"industry": "Fintech"}]} {"ownership_status": {"$ne": "public"}} {"hq_country_iso2": {"$in": ["US", "GB", "DE"]}} {"description": {"$match": "cloud security"}} {"website_domain": "stripe.com"} {"funding_rounds": {"$elemMatch": {"name": "Series B", "amount_raised": {"$gte": 10000000}}}} {"linkedin_url": {"$exists": true}} Billable: 0.1 credit per result returned (a 100-row page costs 10 credits). Each response includes `charge_credits`, the amount charged for that page.

sixtyfour_company_search

Search people profiles with a simple_filters query and return compact smart previews. Each result includes a `result_handle` (for get_person_details) and the response includes `next_cursor`, `has_more`, and `total_available` when the total is exact. Capped totals use `total_available_lower_bound` and appear as `N+` in the summary. Set `count_only=true` to return only the exact match count and timing. Result handles and cursors expire after ~20 minutes. Args: query: MongoDB-style filter dict. Bare values imply $eq. Operators: $ne, $gt, $gte, $lt, $lte, $in, $nin, $exists, $match, $phrase, $elemMatch, $or, $and, $not, $nor, $search, $sort, $limit. page_size: Results per page. max_results: Cap on total results across all pages. include_fields: Field names to hint the preview planner. count_only: Return only the exact match count and timing. Ignores page_size, max_results, include_fields, $limit, and $sort. If a search returns 0 results, use sixtyfour_people_explore_field_values to check valid values. On 400 errors, call sixtyfour_people_get_searchable_fields to verify field names. Linking to companies: the long field currentCompanies.company.companyId is the numeric form of the company's string source_id. Use $elemMatch to filter people by company, and inside it use the full dotted field path with a JSON number. Use exact field names from sixtyfour_people_get_searchable_fields; the examples below use common ones (job title lives at currentCompanies.positions.title, not a top-level field). Examples: {"headline": {"$match": "engineer"}} {"currentCompanies.positions.title": {"$match": "engineering manager"}} {"currentCompanies": {"$elemMatch": {"currentCompanies.company.companyId": 1234567}}} Billable: 0.1 credit per result returned (a 100-row page costs 10 credits). Each response includes `charge_credits`, the amount charged for that page.

sixtyfour_people_search

Start an async Age Verification job and return a task_id for polling. Do not return the task_id as your final answer — poll sixtyfour_verify_age_status to completion first. Establishes a person's date of birth (or a grounded age estimate when an exact date isn't available) from open-source research, with per-field confidence and sourced evidence. `subject` should contain any known identifiers such as name, company, LinkedIn URL, email, or location — more is better. Args: subject: Identifiers for the person to verify.

sixtyfour_verify_age_start