Count emails Hunter knows for a company website

Give a company name or website link. The assistant checks how many email addresses Hunter knows for it and explains available email-type, department and seniority counts.

Your AI

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Use Toolmu to count Hunter-known emails for my company name or website link. Prepare the documented company-name lookup, or parse a verified website link to obtain its hostname for the domain lookup. Clarify ambiguous or insufficient company names with a full name or website instead of guessing. If I request an email type, map ordinary personal-work or general-purpose inbox choices to the documented options. Reuse my Toolmu connection or follow https://toolmu.com/get-started; check cost and honor my budget and authorization. Explain actual counts, preserving source labels, zeros and classification gaps. These are Hunter’s address counts, not actual addresses, employee headcount, full company coverage or proof of deliverability.

Task:
Check how many email addresses Hunter knows for [company name or website link]. Show the total, personal-work and general-purpose inbox counts, plus department and seniority breakdowns. Explain any gaps between those counts.

Paste into your connected AI's conversation.

Connection guide

Free

Hunter

Count emails Hunter knows for a company website

Give a company name or website link. The assistant checks how many email addresses Hunter knows for it and explains available email-type, department and seniority counts.

You receive

Get a total email-address count and the personal/generic split for the requested domain or company, plus source department and seniority counts. Use these figures to understand Hunter’s address coverage before deciding whether to retrieve actual addresses.

Start with your task

Check how many email addresses Hunter knows for [company name or website link]. Show the total, personal-work and general-purpose inbox counts, plus department and seniority breakdowns. Explain any gaps between those counts.

What to know

This result contains counts rather than email addresses. It does not establish employee headcount, complete domain coverage or address deliverability. The returned counts do not establish when individual address records were last updated.

Inputs & outputs

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

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Count lookup inputs`queryParams`	`object`	Optional	Provide domain or company. The endpoint needs at least one; domain takes precedence when both are present. Type is optional.
Address type`queryParams.type`	`string`	Optional	Optional personal or generic. Personal means an individual’s company address; generic means a role-based mailbox. Options `personal, generic`
Domain name`queryParams.domain`	`string`	Optional	Domain to count, such as hunter.io. Supplying a known domain avoids resolving a company name. Minimum length `1`
Company name`queryParams.company`	`string`	Optional	Alternative when the domain is unknown; at least three characters. Ignored in favor of domain if both are supplied. Minimum length `3`

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": "Count only personal or only generic addresses."
        },
        "domain": {
          "type": "string",
          "minLength": 1,
          "description": "Domain name, e.g. 'stripe.com'. Preferred over company — it skips the name-to-domain conversion."
        },
        "company": {
          "type": "string",
          "minLength": 3,
          "description": "Company name, e.g. 'Stripe'. When both company and domain are given, domain wins."
        }
      },
      "description": "Provide at least one of domain or company (domain wins when both are given)."
    }
  },
  "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
Known address count`result.data.total`	`number`	Hunter’s reported email-address count for the requested lookup, rather than employee headcount.
Personal address count`result.data.personal_emails`	`number`	Count of addresses Hunter classifies as belonging to individuals in the company. It does not verify address deliverability.
Generic address count`result.data.generic_emails`	`number`	Count of role-based addresses under Hunter’s generic classification.
Department counts`result.data.department`	`object`	Map of source department labels to address counts. Retain the labels and zero values; this breakdown covers only known department classifications.
Seniority counts`result.data.seniority`	`object`	Counts under source junior, senior and executive classifications; only addresses with known seniority are included.

Additional notes

Use a known domain when checking a target company: it avoids company-name resolution and takes precedence if both inputs are supplied. Leave type unset for a general count, or request personal or generic when you want one address type. Hunter uses personal for an individual’s company address and generic for a role-based mailbox.

Keep each department label as returned. The stored finance & accounting label and the older operation label are source classifications; do not merge or rename their counts when comparing results. Department and seniority are returned breakdowns, with no request filters for either in this Tool.

Inspect this Tool’s current input contract

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

Hunter counts only addresses with a known department or seniority in each breakdown. Addresses without that classification still contribute to the overall total, so do not fill a subtotal gap with invented categories or assume that zero means the company has no staff in that group.

Count emails Hunter knows for a company website

Count emails Hunter knows for a company website

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Give a company name or website

Say which kind of inbox you want to count

Read the count and its breakdowns

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Give a company name or website

Say which kind of inbox you want to count

Read the count and its breakdowns

Questions about this tool.

Why can the department or seniority counts add up to less than the total?