Hunter API
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey4 EndpointsREST
For Agents
Find professional email addresses by company domain, generate likely emails from name and domain, and verify deliverability. Covers domain search, email finder, and email verification.
Use for: I need to find email addresses for people at a specific company, Generate the email address for John Smith at acme.com, Verify whether an email address is valid before sending, Search for all professional emails at a given domain
Not supported: Does not handle email sending, CRM management, or person profile enrichment beyond email — use for email discovery and verification only.
Jentic publishes the only available OpenAPI specification for Hunter API, keeping it validated and agent-ready. Discover professional email addresses for any company domain, generate the most likely email for a specific person given their name and company, and verify email deliverability before sending. The API exposes 4 endpoints covering domain-wide email search, individual email generation, deliverability verification, and account usage tracking.
Install Jentic One Beta
Connect the Hunter API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hunter API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Hunter API.
Discover all professional email addresses associated with a company domain
Generate the most likely email address for a specific person given their first name, last name, and company domain
Verify whether an email address is deliverable before sending outreach
Retrieve account usage information including remaining request credits
Paginate through large result sets with limit and offset parameters for domain searches
Use Cases
Patterns agents use Hunter API for, with concrete tasks.
★ AI Agent Email Discovery via Jentic
AI agents building outreach campaigns can find professional email addresses through Jentic by searching for email discovery operations. The agent passes a company domain and receives all known email addresses with their confidence scores, enabling automated prospect list building without manual research.
Search Jentic for 'find email addresses by domain', load the Hunter /domain-search schema, and query with domain='intercom.com' to retrieve all associated email addresses
Personalised Sales Outreach Email Generation
Sales reps and SDR automation tools generate the most likely email address for a specific prospect by providing their first name, last name, and company domain. Hunter's email pattern recognition returns the generated email with a confidence score, eliminating guesswork in cold outreach.
GET /email-finder with domain='hubspot.com', first_name='Brian', last_name='Halligan' to generate the most likely professional email address
Email Verification Before Campaign Send
Marketing and sales platforms verify email deliverability before sending campaigns to protect sender reputation and reduce bounce rates. The email verifier endpoint checks MX records, SMTP responses, and pattern matching to classify addresses as deliverable, risky, or undeliverable.
GET /email-verifier with email='john@example.com' to check deliverability status and determine whether to include in the outreach campaign
Domain-Wide Contact Discovery for Account Research
Account-based sales teams research target companies by pulling all discoverable email addresses for a domain. The domain search endpoint returns up to 100 addresses per page with pagination support, along with associated names and departments, giving teams a complete contact map for account penetration.
GET /domain-search with domain='salesforce.com' and limit=50 to retrieve the first 50 email addresses and associated names for that company
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for hunter api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/domain-search
Find all email addresses for a company domain
GET
/email-finder
Generate probable email from name and domain
GET
/email-verifier
Verify email deliverability
GET
/account
Retrieve account information and usage
GET
/domain-search
Find all email addresses for a company domain
GET
/email-finder
Generate probable email from name and domain
GET
/email-verifier
Verify email deliverability
GET
/account
Retrieve account information and usage
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Hunter API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access — the api_key query parameter is injected automatically and never exposed in the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'find professional emails at a company') and Jentic returns matching Hunter operations with their input schemas, so the agent can query the right endpoint without browsing docs.
Time to first call
Direct Hunter integration: 1-2 days for auth, pagination handling, and verification flow. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Hunter API through Jentic.
Why is there no official OpenAPI spec for Hunter API?
Hunter does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hunter API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Hunter API use?
The Hunter API uses an API key passed as a query parameter named 'api_key' on every request. Through Jentic, this key is stored encrypted in the credential vault and appended to requests automatically — agents never handle the raw key.
Can I find all email addresses at a company with the Hunter API?
Yes. The /domain-search endpoint accepts a domain parameter and returns all email addresses found for that company. Use the limit parameter (max 100) and offset for pagination to retrieve large result sets.
How does the email finder generate an email address?
The /email-finder endpoint takes a domain, first_name, and last_name, then applies pattern recognition across known email formats for that domain. It returns the most likely email address along with a confidence score indicating match probability.
How do I discover emails through Jentic?
Install the SDK with pip install jentic and search for 'find email addresses at a company'. Jentic returns the Hunter /domain-search operation schema. Pass the target domain and Jentic handles auth (appending the api_key parameter) and returns the list of discovered emails.
What does the email verifier check?
The /email-verifier endpoint checks MX records, SMTP server responses, and known email patterns for the domain. It returns a status indicating whether the address is deliverable, risky (accept-all domain), or undeliverable, helping you clean lists before sending campaigns.
GET STARTED