# Hunter Email Count

> Hunter Email Count is a paid API for AI agents from Hunter at hunter.mpp.paywithlocus.com, paid per call via MPP, $0.003/call, status unknown (last checked 2026-10-12).

Returns the total count of email addresses found for a domain, broken down by seniority, department, and email type (personal vs generic).

## Facts

- Endpoint: POST https://hunter.mpp.paywithlocus.com/hunter/email-count?utm_source=zero.xyz
- Price: $0.003/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Provider: Hunter
- Docs: https://hunter.io/api-documentation/v2
- Website: https://hunter.io
- Tags: email, verification, enrichment, outreach, data
- Canonical page: https://www.zero.xyz/c/hunter-email-count-93e4e851
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bIDwXIKkAZwJsJ9ESCF8B

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability hunter-email-count-93e4e851 -d '<json body>'
```

Example prompt: How many personal emails does Hunter have on file for stripe.com, and can you break them down by department and seniority?

## When to prefer this

Use this endpoint when you need a quick summary of how many emails Hunter has indexed for a domain before committing to a full domain search. Ideal for gauging outreach list size, checking coverage by department or seniority, or deciding whether a domain is worth pursuing without consuming credits for a full email list pull.

## Known failure modes

- Domain not found or no emails indexed — returns zero counts
- Invalid domain format — returns validation error
- Missing both domain and company fields — returns parameter error
- Rate limit exceeded — returns 429 error

## How this service works

Get the number of email addresses found for a domain, broken down by type, department, and seniority.

## Output

Returns a JSON object with the total count of emails for the queried domain, split into personal and generic email counts, plus a seniority breakdown (junior, senior, executive) and a department breakdown (HR, IT, legal, sales, design, finance, support, marketing, management, operations, etc.).

## Example request

```json
{
 "type": "personal",
 "domain": "example.com"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "allOf": [
  {
   "anyOf": [
    {
     "required": [
      "domain"
     ]
    },
    {
     "required": [
      "company"
     ]
    }
   ],
   "description": "domain or company is required"
  }
 ],
 "properties": {
  "type": {
   "type": "string",
   "description": "Filter by type: 'personal' or 'generic'"
  },
  "domain": {
   "type": "string",
   "description": "Domain to check (e.g. \"stripe.com\")"
  },
  "company": {
   "type": "string",
   "description": "Company name to check"
  }
 },
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hunter-email-count-93e4e851/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hunter.mpp.paywithlocus.com](https://www.zero.xyz/host/hunter.mpp.paywithlocus.com/llms.txt)