Read Hunter person and company information by email

Give an email address. The assistant reads the person and company information Hunter associates with it, and explains available work details separately from the company background.

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 read Hunter’s person-and-company context for the email address I provide. Prepare the email lookup yourself; ask me to clarify an incomplete address in ordinary language. Reuse my Toolmu connection or follow https://toolmu.com/get-started; check cost and honor my budget and authorization. Keep actual person employment and associated company facts separate, checking their names and websites before describing the relationship. Explain supplied job and company information in ordinary language, preserve missing information and flag inconsistencies. Source associations do not verify identity, current employment or whether the mailbox can receive mail.

Task:
Read Hunter’s person and company information for [email address]. Explain available employment details and company background separately, and point out missing or inconsistent information.

Paste into your connected AI's conversation.

Connection guide

Up to 0.005741 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Hunter

Read Hunter person and company information by email

Give an email address. The assistant reads the person and company information Hunter associates with it, and explains available work details separately from the company background.

You receive

Read the person’s reported employment alongside the associated company profile in one lookup. Compare employer names and domains, then review available role, title and seniority information separately from the company’s description, industry, location and size.

Start with your task

Read Hunter’s person and company information for [email address]. Explain available employment details and company background separately, and point out missing or inconsistent information.

What to know

Returned associations are source information, not verified identity, consent or current employment. Person and company fields may be missing or null, and company metrics or technologies do not establish complete current records.

Inputs & outputs

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

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Combined lookup input`queryParams`	`object`	Required	Required object containing one email address. No domain-only or output-format parameter is defined. Required fields `email`
Email to enrich`queryParams.email`	`string`	Required	Required email-formatted string for the person/company lookup. Format `email` Pattern `^(?!\.)(?!.\.\.)([A-Za-z0-9_'+\-\.])[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\-]*\.)+[A-Za-z]{2,}$`

View raw JSON

{
  "type": "object",
  "required": [
    "queryParams"
  ],
  "properties": {
    "queryParams": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "email"
      ],
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      },
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "The email address to look up."
        }
      },
      "additionalProperties": false
    }
  },
  "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
Source employment record`result.data.person.employment`	`object`	Reported employer and role context for the person. Missing or null fields stay unknown; this is not verified current employment.
Employer name`result.data.person.employment.name`	`string`	Employer name in the employment record, rather than the person’s name.
Employer domain`result.data.person.employment.domain`	`string`	Employer domain reported for the person; compare it with the separate company record.
Reported job title`result.data.person.employment.title`	`string`	Job title supplied by the source, without independent confirmation that it is current.
Reported role`result.data.person.employment.role`	`string`	Source role classification, distinct from the job-title text.
Reported seniority`result.data.person.employment.seniority`	`string`	Source seniority classification for the employment record.
Company name`result.data.company.name`	`string`	Name of the associated company in the company profile.
Company domain`result.data.company.domain`	`string`	Domain in the company profile; keep distinct from the employment-domain field.
Company description`result.data.company.description`	`string`	Source description of the associated company’s activities or offering.
Company industry categories`result.data.company.category`	`object`	Industry labels and codes supplied for the company; retain the source classifications.
Company location`result.data.company.location`	`string`	Source company-location string, separate from any personal location fields.
Company employee range`result.data.company.metrics.employees`	`string`	Company-size range reported by the source, not a count of enriched people.
Company technology list`result.data.company.tech`	`array`	Source technology identifiers for the company, without a completeness or current-usage guarantee.

Additional notes

Use email enrichment to understand an inbound business email’s context before deciding what to ask next. The employment name and domain describe the employer reported for the person; they are distinct from a person’s name. If employment and company details differ, retain both source records rather than silently treating the association as verified.

Keep company-size ranges as ranges and source technology lists as reported lists. Leave unknown financial or parent fields open; an empty list does not prove that no funding or technology exists. A combined lookup supplies context for a human or Agent to review, without automatically qualifying a lead or changing a CRM record.

Inspect this Tool’s current input contract

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

No. This lookup reads associated person and company information. Matching a profile or job title does not establish whether the address can receive mail.

Read Hunter person and company information by email

Read Hunter person and company information by email

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Give the email address

Let the assistant confirm the lookup

Read work details and company background separately

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Give the email address

Let the assistant confirm the lookup

Read work details and company background separately

Questions about this tool.

Does this lookup confirm that the email can receive messages?