Enrich an email address or LinkedIn handle into contact and company data via Hunter.io, paid per call on Tempo L2.
What it does
This endpoint provides email enrichment powered by Hunter.io, exposed through the Locus MPP (Micropayment Protocol) gateway. Given an email address or LinkedIn handle, it returns enriched contact information such as name, position, company details, and social profiles. Payment is settled per-call on Tempo L2 using pathUSD at $0.013 per request.
The email-enrichment endpoint is one of eight Hunter endpoints available through this MPP service. Sibling endpoints cover domain search, email finding, email verification, company enrichment, combined enrichment, company discovery, and email counting — with per-call prices ranging from $0.003 to $0.023. All endpoints accept POST requests with JSON bodies and use the MPP charge intent for one-shot payments.
The underlying Hunter.io API is well-documented and widely used for sales outreach and lead generation workflows. The Locus MPP wrapper removes the need for a Hunter API key or subscription; agents simply pay per call via the 402 payment challenge. Note that the probe returned 404 on HEAD/GET — this is expected since the endpoint only accepts POST. The OpenAPI schema is complete for request bodies, though response schemas are not documented in the spec.
Capabilities
Use cases
- —Enrich a lead's email address with full name, job title, and company info before outreach
- —Augment CRM records with social profiles and employment details from an email
- —Resolve a LinkedIn handle to structured contact data for sales automation
- —Build prospect profiles in an agent pipeline without managing API keys
Fit
Best for
- —AI agents needing pay-per-call contact enrichment without API key management
- —Sales automation pipelines that enrich emails on the fly
- —Developers integrating Hunter.io data via micropayments on Tempo L2
Not for
- —Bulk enrichment of millions of records (per-call pricing adds up quickly)
- —Use cases requiring response schema guarantees (response schema not documented in the OpenAPI spec)
Quick start
curl -X POST https://hunter.mpp.paywithlocus.com/hunter/email-enrichment \
-H "Content-Type: application/json" \
-d '{"email": "john@example.com"}'Example
Request
{
"email": "john@example.com"
}Endpoint
Quality
The OpenAPI spec provides clear request schemas and pricing for all eight endpoints, but response schemas are absent, no example responses are available, and the crawl yielded no additional documentation. The probe returned 404 because only POST is supported, which is expected behavior, but we lack a confirmed 402 challenge on POST.
Warnings
- —Probe returned 404 on HEAD and GET — endpoint likely only accepts POST; liveness via 402 challenge not confirmed
- —Response schema is not documented in the OpenAPI spec; actual response structure must be inferred from Hunter.io API docs
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 convention; if incorrect, stated prices would be wrong
Citations
- —Email Enrichment endpoint charges 13000 base units per call via Tempo settlementhttps://hunter.mpp.paywithlocus.com
- —Hunter.io API documentation is available at hunter.io/api-documentation/v2https://hunter.io/api-documentation/v2
- —LLM-oriented docs available at beta.paywithlocus.com/mpp/hunter.mdhttps://beta.paywithlocus.com/mpp/hunter.md
- —Eight Hunter endpoints are available through the Locus MPP gateway with prices from 3000 to 23000 base unitshttps://hunter.mpp.paywithlocus.com