Combined person + company enrichment from an email address via Hunter, pay-per-call on Tempo L2.
What it does
The Hunter Combined Enrichment endpoint returns both person-level and company-level data for a given email address in a single API call. It is served through the Locus MPP (Micropayment Protocol) gateway, settling payments on Tempo L2 using pathUSD at $0.023 per request. This endpoint is part of a broader Hunter suite available through Locus that includes domain search, email finding, email verification, email enrichment, company enrichment, company discovery, and email count endpoints.
The Combined Enrichment endpoint accepts a POST request with a required `email` field and returns enriched data about both the person behind the email and their associated company. This combines the functionality of the separate Email Enrichment ($0.013) and Company Enrichment ($0.013) endpoints into one call at a slightly lower combined price. The underlying data comes from Hunter.io's enrichment database, which aggregates publicly available professional information.
Payment is handled automatically via the MPP charge intent — each call is a one-shot micropayment settled in pathUSD on Tempo L2. The endpoint is a POST-only route; HEAD and GET probes return 404, which is expected behavior for this API. No API key or Hunter.io account is needed; authentication and billing are handled entirely through the MPP payment layer.
Capabilities
Use cases
- —Enrich a lead's email to get both personal and company details in one call
- —Augment CRM records with person names, titles, and company metadata
- —Pre-qualify sales prospects by enriching email addresses before outreach
- —Build automated lead scoring pipelines that need person + company context
- —Power agent-driven research workflows that start from an email address
Fit
Best for
- —AI agents needing combined person and company data from an email
- —Sales and outreach automation requiring lead enrichment
- —Developers who want pay-per-call enrichment without managing Hunter API keys
Not for
- —Bulk email list verification (use the dedicated email-verifier endpoint instead)
- —Finding an email address when you only have a name and domain (use email-finder)
- —Free-tier or zero-cost enrichment needs
Quick start
curl -X POST https://hunter.mpp.paywithlocus.com/hunter/combined-enrichment \
-H "Content-Type: application/json" \
-d '{"email": "john@stripe.com"}'Example
Request
{
"email": "john@stripe.com"
}Endpoint
Quality
The OpenAPI schema is well-defined with clear request parameters and pricing metadata, but no response schema or example responses are provided. The endpoint returned 404 on HEAD/GET probes (expected for POST-only), so liveness via the probe is unconfirmed. Crawled pages yielded no additional documentation beyond error messages pointing to external docs.
Warnings
- —Endpoint returned 404 on HEAD and GET probes; it is POST-only so this is expected, but direct 402 challenge was not captured
- —No response schema is documented — the shape of successful responses must be inferred from Hunter.io's own API docs
- —Currency address 0x20c0...b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on the Tempo L2 context; if decimals differ, the stated price would be wrong
Citations
- —Combined Enrichment costs 23000 base units via Tempo settlement in pathUSDhttps://hunter.mpp.paywithlocus.com
- —The endpoint accepts a required email field as a POST requesthttps://hunter.mpp.paywithlocus.com
- —Hunter.io API documentation is available externallyhttps://hunter.io/api-documentation/v2
- —LLM-oriented docs are available at the Locus skill filehttps://beta.paywithlocus.com/mpp/hunter.md