Hunter connector for AI agents

Tools your prospecting agent reaches for on Hunter, scoped per user.

CALL ANY TOOL

21 tools for email finding in Hunter: search a domain's addresses, find and verify emails, enrich people and companies, discover companies, manage saved leads and lists, and read campaign recipients.

hunter_count_emails

Count emails

Count how many email addresses Hunter holds for a domain or company, without returning the addresses. Free: uses no credits. Returns the total, the personal and generic split, and counts by department and seniority, optionally also by job title. Department and seniority counts only include addresses where that value is known, so they can sum to less than the total. Use hunter_count_emails to size a company before spending credits. Use hunter_domain_search to get the addresses themselves.

Parameters

Name

Type

Required

Description

company

string

Optional

Company name, used when the domain is unknown, for example Stripe. Supplying the domain gives better results; when both are sent, the domain is used. Provide domain or company. At least 3 characters.

domain

string

Optional

Company domain name, for example stripe.com. A URL or a leading @ is also accepted and reduced to the domain. Provide domain or company.

include_job_titles

string

Optional

Set to 1 to add counts by job title (data.job_titles). Omit to leave them out. One of: `1`.

type

string

Optional

Count only personal addresses (named people) or only generic, role-based addresses. Omit for both. One of: `personal`, `generic`.

hunter_create_lead

Create lead

Save a new lead to your Hunter account, or add an existing lead with the same email to another list. Returns the saved lead with its id, all fields and its leads list. Free. Use hunter_create_lead to save a contact. Use hunter_update_lead to change a lead you already have.

Parameters

Name

Type

Required

Description

string

Required

Email address of the lead. Example: alexis@reddit.com. If a lead with this email already exists on your team, it is added to the requested list instead of duplicated.

company

string

Optional

Name of the company the lead works at. Example: Reddit.

company_industry

string

Optional

Sector of the company. Any text is accepted; Hunter recommends one of: Animal, Art & Entertainment, Automotive, Beauty & Fitness, Books & Literature, Education & Career, Finance, Food & Drink, Game, Health, Hobby & Leisure, Home & Garden, Industry, Internet & Telecom, Law & Government, Manufacturing, News, Real Estate, Science, Retail, Sport, Technology, Travel.

company_size

string

Optional

Size of the company, as free text. Example: 201-500 employees.

confidence_score

integer

Optional

Estimated probability (0 to 100) that the email is correct, such as the score from hunter_find_email. Example: 97.

country_code

string

Optional

Country of the lead, as an ISO 3166-1 alpha-2 code. Example: US.

custom_attributes

object

Optional

Values for your team's custom attributes, keyed by attribute slug. An unknown slug returns 422. Example: {"customer_id": "cus-1234abcd"}.

department

string

Optional

Department the lead works in, for example sales. A display label such as Sales is stored as sales.

first_name

string

Optional

First name of the lead. Example: Alexis.

last_name

string

Optional

Last name of the lead. Example: Ohanian.

leads_list_id

integer

Optional

ID of the leads list to put the lead in. If neither this nor leads_list_name is set, the lead goes into the most recently created list. Cannot be combined with leads_list_name (422). Example: 42.

leads_list_name

string

Optional

Name of a leads list to put the lead in (up to 255 characters). An existing list with that name is reused (case-insensitive); otherwise a new list is created. Cannot be combined with leads_list_id (422). Example: Q4 prospects.

linkedin_url

string

Optional

URL of the lead's public LinkedIn profile. Example: https://www.linkedin.com/in/alexisohanian.

notes

string

Optional

Personal notes about the lead. Example: Met at SaaStr 2026.

phone_number

string

Optional

Phone number of the lead. Example: +1 415 555 0100.

position

string

Optional

Job title of the lead. Example: Cofounder.

source

string

Optional

Where the lead was found. Example: Conference list.

twitter

string

Optional

Twitter (X) handle of the lead. Example: alexisohanian.

website

string

Optional

Domain name of the lead's company. Example: reddit.com.

hunter_create_leads_list

List create leads

hunter_delete_lead

Delete lead

hunter_delete_leads_list

List delete leads

hunter_discover_companies

Discover companies

Search Hunter's company database with a natural-language query or structured filters: headquarters location, industry, headcount, company type, keywords, technology, funding, job openings, specific organizations or lookalikes. Free: uses no credits. Returns up to 100 companies per page with domain, name, email counts, industry, location, headcount, company type and technologies; meta.results holds the total and meta.filters the filters Hunter applied, which you can resend to page through a natural-language search consistently. Use hunter_discover_companies to build a target company list. Then use hunter_domain_search on a returned domain to get contacts, or hunter_enrich_company for a full profile.

Parameters

Name

Type

Required

Description

company_type

object

Optional

Company types to include and/or exclude. Values: educational, educational institution, government agency, non profit, partnership, privately held, public company, self employed, self owned, sole proprietorship. Example: {"exclude": ["non profit", "government agency"]}.

funding

object

Optional

Funding filters. series is a list of pre_seed, seed, pre_series_a, series_a, pre_series_b, series_b, pre_series_c, series_c+ or other; amount is a range with from and to in USD; date is an inclusive range with from and/or to in YYYY-MM-DD. Premium plans only. Example: {"series": ["series_a", "series_b"], "date": {"from": "2025-01-01"}}.

headcount

array

Optional

Company size ranges to include, as Hunter's ranges: 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+. Example: ["11-50", "51-200"].

headquarters_location

object

Optional

Headquarters locations to include and/or exclude. Each location sets a continent (Europe, Asia, North America, Africa, Antarctica, South America, Oceania), a business_region (AMER, EMEA, APAC, LATAM), or a country as an ISO 3166-1 alpha-2 code with an optional state and city. A city needs a country; state codes are US codes such as CA or ISO 3166-2 codes such as FR-IDF. Example: {"include": [{"continent": "Europe"}, {"country": "US", "state": "CA"}], "exclude": [{"country": "BE"}]}.

industry

object

Optional

Industries to include and/or exclude, using Hunter's industry names (see https://hunter.io/api/industries.json). Example: {"include": ["Software Development"], "exclude": ["Staffing and Recruiting"]}.

job_openings

object

Optional

Filter by open job postings. Set hiring to true for companies hiring now, or narrow by department (case-sensitive names such as sales, engineering, marketing), job_title include/exclude keyword lists, posted_date (last7d, last30d, last90d) and an open_roles range with from and/or to. Set include_closed_roles to true to also match closed roles. Example: {"hiring": true, "department": ["sales"], "posted_date": "last30d"}.

keywords

object

Optional

Keywords to include and/or exclude, and whether a company must match all or any of them (default all). Example: {"include": ["saas", "crm"], "match": "any"}.

limit

integer

Optional

Number of companies to return, from 1 to 100. Default 100.

offset

integer

Optional

Number of companies to skip, up to 10000. Only plans with Discover paging (Premium) can set an offset above 0; others get a 400 pagination_error.

organization

object

Optional

Specific companies to select, by domain and/or name. Example: {"domain": ["hunter.io", "stripe.com"], "name": ["Intercom"]}.

query

string

Optional

Natural-language description of the companies you want; an AI assistant turns it into filters. Required unless at least one filter is set. Up to 2000 characters. Example: Companies in Europe that specialize in software development.

similar_to

object

Optional

Find companies similar to one company, by domain or name; the domain is used if both are given. Premium plans only. Example: {"domain": "hunter.io"}.

technology

object

Optional

Technologies to include and/or exclude, using Hunter's technology slugs (see https://hunter.io/api/technologies.json), and whether to match all or any (default all). Premium plans only. Example: {"include": ["stripe", "hubspot"], "match": "any"}.

year_founded

object

Optional

Founding years to include or exclude, or a range with from and/or to. Premium plans only. Example: {"from": 2010, "to": 2020}.

hunter_domain_search

Search domain

Search the email addresses Hunter has found for a company, by domain or company name, with filters for seniority, department, job title, decision makers and verification status. Returns the domain's email pattern and organization name, then a page of people with email, type, confidence score, name, position, seniority, department, LinkedIn, phone number and verification status; meta.results holds the total count. Uses 1 search credit when at least one email is returned. Use hunter_domain_search to list many contacts at one company. Use hunter_find_email for one named person. Use hunter_count_emails to size a domain for free before searching.

Parameters

Name

Type

Required

Description

aggregations

boolean

Optional

When true, adds meta.aggregations with personal-email counts per department, the number of decision makers and the personal/generic split, all reflecting the filters.

company

string

Optional

Company name, used when the domain is unknown, for example Stripe. Supplying the domain gives better results; when both are sent, the domain is used. Provide domain or company.

decision_maker

boolean

Optional

true returns only the company's likely decision makers (people with buying authority, inferred from seniority and department); false returns only people classified as non-decision-makers. Omit for everyone.

department

string

Optional

Comma-separated departments to keep, for example sales,marketing. Values: executive, it, finance, management, sales, legal, support, hr, marketing, communication, education, design, health, operations, product, research, consulting, administrative, procurement. Unknown values are ignored; a list with no valid value returns 400.

domain

string

Optional

Company domain name, for example stripe.com. A URL or a leading @ is also accepted and reduced to the domain. Provide domain or company.

job_titles

string

Optional

Comma-separated job titles to keep. Titles match whole words and common equivalents (CTO matches Chief Technology Officer). Example: CTO,VP Sales.

limit

integer

Optional

Maximum number of email addresses to return, from 1 to 100. Hunter's default is 10. Example: 25.

offset

integer

Optional

Number of email addresses to skip, for paging. Increase it by the limit on each call. Default 0. On the Free plan, limit plus offset cannot exceed 10.

required_field

string

Optional

Comma-separated fields a person must have to be returned: full_name, position, phone_number. Example: full_name,position.

seniority

string

Optional

Comma-separated seniority levels to keep: junior, senior, executive. Example: senior,executive.

type

string

Optional

Return only personal addresses (a named person) or only generic, role-based addresses such as contact@. Omit for both. One of: `personal`, `generic`.

verification_status

string

Optional

Comma-separated verification statuses to keep: valid, accept_all, unknown. Example: valid.

hunter_enrich_company

Enrich company

hunter_enrich_person

Enrich person

hunter_enrich_person_and_company

Enrich person and company

hunter_find_email

Find email

hunter_get_account

Get account

hunter_get_lead

Get lead

hunter_get_leads_list

List get leads

hunter_list_campaign_recipients

List campaign recipients

hunter_list_campaigns

List campaigns

hunter_list_leads

List leads

List the leads saved in your Hunter account, newest first, with optional text search and attribute filters. Returns leads with id, email, name, position, company, website, country, phone, LinkedIn, notes, verification status, sending status, leads list and created date; meta.total holds the total count. Free. Use hunter_list_leads to browse or search saved leads. Use hunter_get_lead for one lead by ID. Use hunter_domain_search to find new contacts that are not saved yet.

Parameters

Name

Type

Required

Description

company

string

Optional

Filter by company name: contained text, * for any value, ~ for empty. Example: Stripe.

country_code

string

Optional

Filter by country, as an ISO 3166-1 alpha-2 code. Example: US.

string

Optional

Filter by email. Any text matches leads whose email contains it; * matches leads with any email; ~ matches leads with no email. Example: @stripe.com.

first_name

string

Optional

Filter by first name: contained text, * for any value, ~ for empty. Example: Jeremy.

industry

string

Optional

Filter by company industry: contained text, * for any value, ~ for empty. Example: Technology.

last_name

string

Optional

Filter by last name: contained text, * for any value, ~ for empty. Example: Hoon.

leads_list_id

integer

Optional

Only return leads in this leads list. Example: 42.

limit

integer

Optional

Maximum number of leads to return, from 1 to 1000. Hunter's default is 20. Example: 25.

offset

integer

Optional

Number of leads to skip, for paging, from 0 to 100000. Default 0.

position

string

Optional

Filter by job position: contained text, * for any value, ~ for empty. Example: CEO.

query

string

Optional

Free-text search over first name, last name, company, website and email. Every word must match one of these fields. An email address returns only the lead with that exact email. Example: stripe.

sort

string

Optional

Order of the leads: newest (default), oldest, or relevance (best matches first when query or position is set). One of: `newest`, `oldest`, `relevance`.

verification_status

array

Optional

Only return leads with one of these email verification statuses: accept_all, disposable, invalid, unknown, valid, webmail, pending. Example: ["valid", "accept_all"].

website

string

Optional

Filter by company website: contained text, * for any value, ~ for empty. Example: stripe.com.

hunter_list_leads_lists

List leads lists

hunter_update_lead

Update lead

Update fields of an existing lead. Only the fields you send change. Returns an empty response (HTTP 204) on success. Use hunter_update_lead to edit a saved lead by ID. Use hunter_create_lead to save a new one. Use hunter_get_lead to read the result.

Parameters

Name

Type

Required

Description

lead_id

integer

Required

ID of the lead, as returned by hunter_list_leads or hunter_create_lead. Example: 12345.

company

string

Optional

Name of the company the lead works at. Example: Reddit.

company_industry

string

Optional

company_size

string

Optional

Size of the company, as free text. Example: 201-500 employees.

confidence_score

integer

Optional

Estimated probability (0 to 100) that the email is correct, such as the score from hunter_find_email. Example: 97.

country_code

string

Optional

Country of the lead, as an ISO 3166-1 alpha-2 code. Example: US.

custom_attributes

object

Optional

Values for your team's custom attributes, keyed by attribute slug. Only the keys you send change; send an empty string to clear one. An unknown slug returns 422. Example: {"customer_id": "cus-1234abcd"}.

department

string

Optional

Department the lead works in, for example sales. A display label such as Sales is stored as sales.

string

Optional

Email address of the lead. Example: alexis@reddit.com.

first_name

string

Optional

First name of the lead. Example: Alexis.

last_name

string

Optional

Last name of the lead. Example: Ohanian.

leads_list_id

integer

Optional

ID of the leads list to put the lead in. Moves the lead to this list. Example: 42.

linkedin_url

string

Optional

URL of the lead's public LinkedIn profile. Example: https://www.linkedin.com/in/alexisohanian.

notes

string

Optional

Personal notes about the lead. Example: Met at SaaStr 2026.

phone_number

string

Optional

Phone number of the lead. Example: +1 415 555 0100.

position

string

Optional

Job title of the lead. Example: Cofounder.

source

string

Optional

Where the lead was found. Example: Conference list.

twitter

string

Optional

Twitter (X) handle of the lead. Example: alexisohanian.

website

string

Optional

Domain name of the lead's company. Example: reddit.com.

hunter_update_leads_list

List update leads

hunter_verify_email

Verify email

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Hunter tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["hunter"], toolNames: [
    "hunter_domain_search",
    "hunter_find_email",
    "hunter_verify_email"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find and verify the email of the head of sales at northwind.io" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["hunter"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find and verify the email of the head of sales at northwind.io" }],
  tools,
});

// Execute the tool call with the user's vaulted Hunter API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["hunter"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find and verify the email of the head of sales at northwind.io" }],
  tools,
});

// Tool call runs with the user's vaulted Hunter API key
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["hunter"] }, pageSize: 100,
});

const agent = new Agent({
  name: "prospecting_agent",
  model: "gemini-2.5-pro",
  instruction: "Hunter tools scoped to this user",
  tools,
});

await agent.run("Find and verify the email of the head of sales at northwind.io");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Hunter tool. Click to copy, paste into your agent, done.

Find emails

Copy the prompt

Copied

Find the email address of Priya Shah at northwind.io.

Copy the prompt

Copied

List the marketing decision makers Hunter has found at contoso.com.

Copy the prompt

Copied

How many email addresses does Hunter hold for fabrikam.com?

Verify and enrich

Copy the prompt

Copied

Verify whether jordan@contoso.com is deliverable.

Copy the prompt

Copied

Enrich the person and company behind alex@northwind.io.

Copy the prompt

Copied

Find SaaS companies in Germany with 50 to 200 employees.

Leads and campaigns

Copy the prompt

Copied

Create a leads list called Q4 fintech targets.

Copy the prompt

Copied

Save Priya Shah at northwind.io as a lead in Q4 fintech targets.

Copy the prompt

Copied

List the recipients of my latest email campaign.

SEE HOW AUTH WORKS

Each user connects their own Hunter API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Hunter

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Hunter

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Hunter

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Hunter

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other sales and marketing connectors.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Hunter API key looks fine in a demo. In production every lead saved and every email lookup looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Hunter today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Hunter as the user or through a shared API key?

As the user. Each user connects their own Hunter API key once, and Scalekit sends it with every call. Audit logs attribute every lookup and lead change to that user, not a shared service account.

Where is the Hunter API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Hunter?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the finder, verifier, and enrichment tools without hunter_delete_lead and hunter_delete_leads_list, which permanently delete saved leads and lists. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Hunter access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent size a company before spending Hunter credits?

Yes. hunter_count_emails returns how many addresses Hunter holds for a domain, split by department and seniority, and uses no credits. The agent can then call hunter_domain_search for the addresses themselves, and hunter_get_account shows the remaining credits.