Hunter
Hunter is an email finding and verification service that helps find professional email addresses associated with a domain and verify email deliverability.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Hunter the way a machine reads it — 140 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Hunter scores 71.3/100 (exemplar), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Hunter
Each block below is one kind of artifact we hold for Hunter. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Hunter Account API
Retrieve account information and usage statistics.
Hunter Campaigns API
Manage email sequences and recipients.
Hunter Combined Enrichment API
Merge person and company enrichment for a single email address.
Hunter Company Enrichment API
Enrich company information linked to a domain name.
Hunter Discover API
Find companies matching criteria using natural language or filters.
Hunter Domain Search API
Search for email addresses associated with a domain.
Hunter Email Count API
Count email addresses found for a domain.
Hunter Email Enrichment API
Enrich personal information linked to an email or LinkedIn profile.
Hunter Email Finder API
Find the most likely email address for a person at a company.
Hunter Email Verifier API
Verify the deliverability of an email address.
Hunter Leads API
Manage leads stored in Hunter.
Hunter Leads Lists API
Manage leads list collections in Hunter.
Scroll within the panel for all 12 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Hunter API
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Hunter API
OPEN COLLECTIONArazzo Workflows 10
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Hunter Account-Guarded Domain Search
Check remaining search quota before running a domain search.
ARAZZOHunter Combined Enrich and Upsert Lead
Combine person and company enrichment for an email, then upsert it as a lead.
ARAZZOHunter Discover, Search, and Count
Discover a target company, search its domain, and count its emails.
ARAZZOHunter Domain Search to Build a Verified List
Search a domain, create a list, verify the top email, and upsert it as a lead.
ARAZZOHunter Domain Search, Find, and Verify
Search a domain for emails, find a named person's address, then verify it.
ARAZZOHunter Enrich, Verify, and Create Lead
Enrich a person from an email, verify the address, and save a verified lead.
ARAZZOHunter Find, Verify, and Add Campaign Recipient
Find a person's email, verify it, and add it to a campaign when valid.
ARAZZOHunter Find, Verify, and Create Lead
Find a person's email, verify it, and only save a lead when it is valid.
ARAZZOHunter Verify and Add to Campaign
Verify an email, add it to a campaign when valid, then start the campaign.
ARAZZOScroll within the panel for all 10 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Hunter Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hunter Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Hunter Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Domain Search
Find all email addresses associated with a domain name along with confidence scores and sources.
Email Finder
Generate the most likely email address for a person given their name and company domain.
Email Verification
Verify the deliverability and validity of email addresses with detailed status reporting.
Lead Management
Store, organize, and manage prospect leads with lists, tags, and CRM-like contact management.
Email Campaigns
Create and manage automated email outreach sequences with recipient tracking and scheduling.
Data Enrichment
Enrich email addresses and domains with personal, company, and firmographic data points.
Company Discovery
Find companies matching ideal customer profiles using natural language queries and advanced filters.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Hunter Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Hunter API Rules
SPECTRALHunter API Rules
SPECTRALJSON Schema 41
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccountResult
JSON SCHEMAAccountResult
JSON SCHEMACampaignRecipient
JSON SCHEMACampaign
JSON SCHEMACampaignRecipient
JSON SCHEMACompanyEnrichment
JSON SCHEMACompanyGeoLocation
JSON SCHEMACompanyEnrichment
JSON SCHEMACompanyGeoLocation
JSON SCHEMADiscoverRequest
JSON SCHEMADiscoverResult
JSON SCHEMADiscoverRequest
JSON SCHEMADiscoverResult
JSON SCHEMADomainEmail
JSON SCHEMADomainSearchResult
JSON SCHEMADomainEmail
JSON SCHEMADomainSearchResult
JSON SCHEMAEmailCountResult
JSON SCHEMAEmailFinderResult
JSON SCHEMAEmailVerifierResult
JSON SCHEMAEmailCountResult
JSON SCHEMAEmailFinderResult
JSON SCHEMAEmailVerifierResult
JSON SCHEMAError
JSON SCHEMAGeoLocation
JSON SCHEMAGeoLocation
JSON SCHEMALeadInput
JSON SCHEMALead
JSON SCHEMALeadInput
JSON SCHEMALeadsList
JSON SCHEMALeadsList
JSON SCHEMAMeta
JSON SCHEMAPaginationMeta
JSON SCHEMAPaginationMeta
JSON SCHEMAPersonEnrichment
JSON SCHEMAPersonEnrichment
JSON SCHEMASource
JSON SCHEMAUsageCounter
JSON SCHEMAUsageCounter
JSON SCHEMAVerificationStatus
JSON SCHEMAVerificationStatus
JSON SCHEMAScroll within the panel for all 41 ·
JSON Structure 24
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Hunter Account Result Structure
JSON STRUCTUREHunter Campaign Recipient Structure
JSON STRUCTUREHunter Campaign Structure
JSON STRUCTUREHunter Company Enrichment Structure
JSON STRUCTUREHunter Company Geo Location Structure
JSON STRUCTUREHunter Discover Request Structure
JSON STRUCTUREHunter Discover Result Structure
JSON STRUCTUREHunter Domain Email Structure
JSON STRUCTUREHunter Domain Search Result Structure
JSON STRUCTUREHunter Email Count Result Structure
JSON STRUCTUREHunter Email Finder Result Structure
JSON STRUCTUREHunter Email Verifier Result Structure
JSON STRUCTUREHunter Error Structure
JSON STRUCTUREHunter Geo Location Structure
JSON STRUCTUREHunter Lead Input Structure
JSON STRUCTUREHunter Lead Structure
JSON STRUCTUREHunter Leads List Structure
JSON STRUCTUREHunter Meta Structure
JSON STRUCTUREHunter Pagination Meta Structure
JSON STRUCTUREHunter Person Enrichment Structure
JSON STRUCTUREHunter Source Structure
JSON STRUCTUREHunter Structure
JSON STRUCTUREHunter Usage Counter Structure
JSON STRUCTUREHunter Verification Status Structure
JSON STRUCTUREScroll within the panel for all 24 ·
Examples 23
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Hunter Campaign Example
EXAMPLEHunter Domain Email Example
EXAMPLEHunter Error Example
EXAMPLEHunter Geo Location Example
EXAMPLEHunter Lead Example
EXAMPLEHunter Lead Input Example
EXAMPLEHunter Leads List Example
EXAMPLEHunter Meta Example
EXAMPLEHunter Source Example
EXAMPLEHunter Usage Counter Example
EXAMPLEScroll within the panel for all 23 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Sales Prospecting
Find and verify email addresses for sales outreach by searching company domains and building prospect lists.
Lead Qualification
Enrich leads with company and personal data to qualify prospects and prioritize outreach efforts.
Email List Cleaning
Verify large email lists to reduce bounce rates and improve email deliverability.
Account-Based Marketing
Discover key contacts at target accounts using domain search and build targeted outreach campaigns.
Recruitment Outreach
Find professional email addresses for passive candidates at target companies for recruitment campaigns.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Salesforce
Push verified leads and enriched contacts directly to Salesforce CRM for pipeline management.
HubSpot
Sync leads and contact data with HubSpot CRM for unified sales and marketing workflows.
Pipedrive
Export leads to Pipedrive CRM with enriched contact and company information.
Zapier
Connect Hunter with thousands of apps through Zapier for automated lead processing workflows.
Google Sheets
Export domain search results and verified emails directly to Google Sheets for analysis.
Zoho CRM
Integrate lead data with Zoho CRM for end-to-end sales pipeline management.
Resources
Every other property we hold for Hunter — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hunter · machine-readable index on apis.io