Search masked contact records across companies with Hunter

Describe where the companies are based and which departments or seniority groups you want to review. Get matching contact records with available work context; email addresses remain hidden.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use Toolmu search-people-across-companies-hunter to inspect masked contact records with my ordinary company and contact requirements. Reuse a working Toolmu connection or follow https://toolmu.com/SKILL.md to connect. Check availability, current inputs and credit ceiling, keeping all requests within my authorization and total budget. Ask for a narrowing company or email criterion if none is supplied. Prepare actual documented company-location, department and seniority choices internally; clarify ambiguous categories in ordinary words. For this example request personal addresses and up to five rows on the first page. Do not ask me for source codes, comma-separated values or pagination cursors. Use only real returned continuation information when I ask for more. Do not infer source industry numeric IDs from the flat industry label list, or promise a non-decision-maker-only filter when the source ignores false. Preserve any unresolved catalog/source differences and do not pretend unsupported criteria were applied. Show available company and job context, verification labels and whether other information is recorded, keeping actual addresses, phone numbers and social URLs hidden. Matching rows are not necessarily unique people or qualified buyers. Do not reveal addresses automatically; if I request a reveal, let me select readable actual rows and use their original reveal information in a separate authorized request within the cumulative budget.

Task:
Use Hunter to review up to 5 personal email records at companies in [country or region], for [department, such as sales] and [seniority group, such as senior]. Keep email addresses hidden and show available company and work information.

Paste into your connected AI's conversation.

Connection guide

Free

Hunter

Search masked contact records across companies with Hunter

Describe where the companies are based and which departments or seniority groups you want to review. Get matching contact records with available work context; email addresses remain hidden.

You receive

Review a page of contact records with hidden email addresses, available company and work information, and source verification labels. The source may indicate which other details it has recorded without showing their contents, and report the overall match count.

Start with your task

Use Hunter to review up to 5 personal email records at companies in [country or region], for [department, such as sales] and [seniority group, such as senior]. Keep email addresses hidden and show available company and work information.

What to know

Actual email addresses, phone numbers and social URLs remain hidden. Source role and verification metadata do not establish current employment or a fresh delivery test, and matching rows are not necessarily unique people.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Masked record search`queryParams`	`object`	Optional	Provide at least one narrowing company or email filter. limit, search_after and per_domain alone do not select records.
Email record type`queryParams.type`	`string`	Optional	Select personal or generic. The generic category can represent a shared role address rather than a named individual. Options `personal, generic`
Rows per page`queryParams.limit`	`integer`	Optional	Optional integer from 1 to 100, default 100. The page can contain fewer matching email records. Minimum `1` Maximum `100`
industry`queryParams.industry`	`string`	Optional	Company industry(ies). Several values can be selected, comma-delimited. Minimum length `1`
Company countries`queryParams.location`	`string`	Optional	Company locations expressed as two-letter ISO country codes, such as US. Separate multiple values with commas. Minimum length `1`
Company size ranges`queryParams.headcount`	`string`	Optional	Select supported source size ranges such as 11-50 or 51-200, comma-separated. These are company-size criteria, not matching email totals. Minimum length `1`
Seniority categories`queryParams.seniority`	`string`	Optional	Choose junior, senior or executive; multiple selected values are comma-separated. Minimum length `1`
Departments`queryParams.department`	`string`	Optional	Comma-separated source departments, such as sales or executive. Each value must be supported; the unassigned-department ~ value is not accepted here. Minimum length `1`
Domain count breakdown`queryParams.per_domain`	`boolean`	Optional	Optional boolean, false by default. True requests matching email counts for at most the top 1000 domains by count.
Technology identifiers`queryParams.technology`	`string`	Optional	Comma-separated technology identifiers accepted by Hunter. Confirm supported source identifiers before selecting them. Minimum length `1`
Company names`queryParams.company_name`	`string`	Optional	One or more company names to match, separated by commas. Minimum length `1`
Company types`queryParams.company_type`	`string`	Optional	Comma-separated supported source company-type values. This category filter does not verify legal registration. Minimum length `1`
Founding years`queryParams.founded_year`	`string`	Optional	Comma-separated four-digit years from 1000 through next year, as accepted by the source. Minimum length `1`
Continuation cursor`queryParams.search_after`	`string`	Optional	Omit for the first page, then pass the previous response’s meta.next_search_after unchanged. No offset pagination is used. Minimum length `1`
Decision-maker selection`queryParams.decision_maker`	`boolean`	Optional	Set true to select the source decision-maker classification. False is ignored by this search and does not request non-decision-makers.
Minimum source score`queryParams.min_confidence`	`integer`	Optional	Use a source confidence threshold from 2 to 100 for the hidden address. Do not treat the threshold as a verified delivery probability. Minimum `0` Maximum `100`
Required source fields`queryParams.required_field`	`string`	Optional	Choose full_name, position and/or phone_number, comma-separated. Every requested field must exist; hidden fields remain hidden. Minimum length `1`
Verification labels`queryParams.verification_status`	`string`	Optional	Filter by valid, accept_all or unknown, comma-separated. These are source labels, not a fresh delivery test performed by this search. Minimum length `1`

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      },
      "properties": {
        "type": {
          "enum": [
            "personal",
            "generic"
          ],
          "type": "string",
          "description": "Only personal or generic addresses."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Email rows per page. Default and max 100."
        },
        "industry": {
          "type": "string",
          "minLength": 1,
          "description": "Company industry(ies). Several values can be selected, comma-delimited."
        },
        "location": {
          "type": "string",
          "minLength": 1,
          "description": "Company location(s), e.g. 'US'. Several values can be selected, comma-delimited."
        },
        "headcount": {
          "type": "string",
          "minLength": 1,
          "description": "Company size range(s), e.g. '11-50'. Several values can be selected, comma-delimited."
        },
        "seniority": {
          "type": "string",
          "minLength": 1,
          "description": "Seniority level(s): junior, senior, executive. Several values can be selected, comma-delimited."
        },
        "department": {
          "type": "string",
          "minLength": 1,
          "description": "Person department(s), e.g. 'executive'. Several values can be selected, comma-delimited."
        },
        "per_domain": {
          "type": "boolean",
          "description": "Include a per-domain breakdown of matching email counts (top 1,000 domains)."
        },
        "technology": {
          "type": "string",
          "minLength": 1,
          "description": "Technology(ies) in use. Several values can be selected, comma-delimited."
        },
        "company_name": {
          "type": "string",
          "minLength": 1,
          "description": "Company name(s) to match. Several values can be selected, comma-delimited."
        },
        "company_type": {
          "type": "string",
          "minLength": 1,
          "description": "Company type(s). Several values can be selected, comma-delimited."
        },
        "founded_year": {
          "type": "string",
          "minLength": 1,
          "description": "Founding year(s). Several values can be selected, comma-delimited."
        },
        "search_after": {
          "type": "string",
          "minLength": 1,
          "description": "Pagination cursor: pass the previous response's meta.next_search_after. Omit for the first page."
        },
        "decision_maker": {
          "type": "boolean",
          "description": "Only (non-)decision-makers."
        },
        "min_confidence": {
          "type": "integer",
          "maximum": 100,
          "minimum": 0,
          "description": "Minimum confidence score of the hidden address."
        },
        "required_field": {
          "type": "string",
          "minLength": 1,
          "description": "Required person field(s): full_name, position, phone_number. Several values can be selected, comma-delimited."
        },
        "verification_status": {
          "type": "string",
          "minLength": 1,
          "description": "Verification status(es): valid, accept_all, unknown. Several values can be selected, comma-delimited."
        }
      },
      "description": "Provide at least one company or email filter; limit/search_after/per_domain alone do not select anything."
    }
  },
  "additionalProperties": false
}

Result schema

No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.

Result schema
Field / Path	Type	Meaning
Masked email records`result.data`	`array`	Matching source email rows for the page, not necessarily unique people. The actual address stays hidden.
Source record type`result.data[].type`	`string`	The source personal/generic classification of the hidden address.
Company name`result.data[].company_name`	`string`	Company name associated with the source record.
Company domain`result.data[].domain`	`string`	Company domain associated with the matching record.
Source job title`result.data[].position`	`string`	Job title supplied with the record; it is not proof of current employment.
Source department`result.data[].department`	`string`	Department classification reported for the record.
Source seniority`result.data[].seniority`	`string`	Seniority category reported for the record.
Decision-maker flag`result.data[].decision_maker`	`boolean`	Source decision-maker flag. It does not independently establish authority, purchasing interest or the meaning of a false classification.
Source verification status`result.data[].verification.status`	`string`	Verification label supplied with the hidden address; preserve unknown as unknown rather than a delivery guarantee.
Source verification date`result.data[].verification.date`	`null`	Date supplied with the verification record when available. A null value supplies no date; status alone does not establish a recent check.
Full-name presence`result.data[].full_name_exists`	`boolean`	Boolean indicating whether the source has a full name, without supplying that hidden name.
Phone presence`result.data[].phone_number_exists`	`boolean`	Boolean indicating whether Hunter has phone information for the record, without providing the number.
LinkedIn presence`result.data[].linkedin_exists`	`boolean`	Boolean indicating whether Hunter has LinkedIn information for the record, without providing a profile URL.
Matching email-row total`result.meta.results`	`number`	Source-reported count across the full selection, not the page length or unique-person count. It may exceed the reachable 10000-row page limit.
Domain email counts`result.meta.per_domain`	`array`	Optional domain/count entries for matching emails, limited to the top 1000 domains by count. It is not a list of actual addresses.
Next-page cursor`result.meta.next_search_after`	`string`	Source cursor for the next page. Pass it unchanged as search_after; do not invent or decode a cursor.

Additional notes

Start a B2B contact survey by choosing the companies and roles you want to inspect. For example, location US with department sales and seniority senior requests records in those source categories. A returned row corresponds to a matching email record, which can be personal or generic, rather than necessarily one unique person.

The search keeps actual addresses hidden while showing available professional context and presence flags. A phone or LinkedIn presence flag does not provide the hidden value. The supplier uses separate reveal handles for a later address-reveal task; surveying these records does not carry out that step.

Use the returned cursor for another page with the same selection. Cursor access reaches the first 10,000 matching rows even when the reported total is larger. When requested, the domain breakdown covers at most the top 1,000 matching domains by count; narrow the filters to examine a more focused set. Check the current inputs before execution. Current Tool inputs

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

It shows a source record matching your selected categories. Assess the role’s relevance and the company’s needs separately; a matching job category or decision-maker flag does not prove purchase interest or fit.

Search masked contact records across companies with Hunter

Search masked contact records across companies with Hunter

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Replace the search requirements

Let your assistant prepare the choices

Review the information that is available

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Replace the search requirements

Let your assistant prepare the choices

Review the information that is available

Questions about this tool.

Does a matching record mean the person is a suitable customer?