Get the count of publicly available email addresses for any domain or company via Hunter.io.
What it does
The Hunter Email Count endpoint returns the number of email addresses Hunter.io has indexed for a given domain or company. You can optionally filter results by email type (personal or generic). This is useful for qualifying leads, estimating outreach potential, or triaging domains before committing to more expensive email-finding or enrichment calls.
This endpoint is part of a broader Hunter suite exposed through the Locus MPP (Micropayment Protocol) gateway, which also includes Domain Search, Email Finder, Email Verifier, Email Enrichment, Company Enrichment, Combined Enrichment, and Discover Companies. Each call is settled per-request via Tempo (pathUSD on Tempo L2). The Email Count endpoint is priced at 3,000 base units of pathUSD (6 decimals), which works out to $0.003 per call — the cheapest endpoint in the Hunter suite.
The endpoint accepts POST requests with a JSON body containing a domain (e.g. "stripe.com") or company name, plus an optional type filter. Payment is handled via the MPP 402 challenge/response flow using the Tempo settlement method. Note that the probe returned 404 on HEAD/GET, which is expected since this endpoint only accepts POST. The OpenAPI spec from the provider confirms the endpoint exists and documents its schema.
Capabilities
Use cases
- —Estimate the number of reachable email addresses at a target company before running a full domain search
- —Qualify domains for outreach campaigns by checking email volume
- —Filter domains by personal vs. generic email availability
- —Triage a list of companies to prioritize those with the most discoverable contacts
- —Pre-screen domains before spending on email finder or enrichment calls
Fit
Best for
- —Sales and marketing teams qualifying outreach targets
- —AI agents building lead-generation pipelines
- —Developers integrating lightweight email intelligence into workflows
Not for
- —Retrieving actual email addresses (use Domain Search or Email Finder instead)
- —Verifying whether a specific email address is valid (use Email Verifier)
- —Bulk email list cleaning or validation
Quick start
curl -X POST https://hunter.mpp.paywithlocus.com/hunter/email-count \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <MPP_TOKEN>" \
-d '{"domain": "stripe.com"}'Example
Request
{
"type": "personal",
"domain": "stripe.com"
}Endpoint
Quality
The OpenAPI spec provides clear request schema, pricing, and endpoint metadata. However, no response schema or example response is documented, the probe returned 404 because only POST is supported (not a liveness failure), and crawled pages returned no useful documentation. Pricing is clear from the spec.
Warnings
- —Probe returned 404 on HEAD and GET — endpoint only accepts POST, so liveness could not be confirmed via the probe alone
- —No response schema or example response is available in the OpenAPI spec
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on the Tempo method context; if decimals differ, the $0.003 price would be incorrect
- —Crawled documentation pages all returned 404; refer to https://beta.paywithlocus.com/mpp/hunter.md or https://hunter.io/api-documentation/v2 for full docs
Citations
- —Email Count endpoint is priced at 3000 base units via Tempo settlementhttps://hunter.mpp.paywithlocus.com
- —Hunter API documentation is available at hunter.iohttps://hunter.io/api-documentation/v2
- —LLM-oriented docs are at beta.paywithlocus.com/mpp/hunter.mdhttps://beta.paywithlocus.com/mpp/hunter.md
- —The endpoint accepts domain, company, and type parameters in a POST bodyhttps://hunter.mpp.paywithlocus.com