Verify email addresses via Hunter.io, pay-per-call through Locus MPP on Tempo L2.
What it does
This endpoint provides email verification powered by Hunter.io, exposed through the Locus Micropayment Protocol (MPP). Given an email address, it returns verification results indicating whether the address is valid, invalid, or of unknown status. The endpoint is part of a broader Hunter.io suite available via Locus MPP that also includes domain search, email finder, email/company/combined enrichment, company discovery, and email count — but this specific listing covers the email-verifier path.
The email-verifier endpoint accepts POST requests with a JSON body containing a required `email` field. Payment is handled via the MPP "charge" intent using the Tempo method, settling in pathUSD on Tempo L2. The listed price is 8,000 base units; assuming pathUSD uses 6 decimals, this translates to $0.008 per verification call. The currency contract address is 0x20c000000000000000000000b9537d11c60e8b50.
Note that the probe did not capture a live 402 challenge from the email-verifier endpoint itself (HEAD and GET returned 404, which is expected since the endpoint only accepts POST). The OpenAPI spec is well-structured with clear request schemas, but response schemas are not documented beyond status codes. For full Hunter.io API documentation, refer to https://hunter.io/api-documentation/v2.
Capabilities
Use cases
- —Validating email addresses before sending outreach campaigns
- —Cleaning email lists to reduce bounce rates
- —Verifying lead contact information in sales pipelines
- —Automated email hygiene checks in CRM workflows
- —Agent-driven contact verification during prospecting
Fit
Best for
- —Sales and marketing teams verifying prospect emails on a per-call basis
- —AI agents that need programmatic email validation without API key management
- —Low-volume or bursty email verification where pay-per-call is more economical than a subscription
Not for
- —Bulk email list cleaning at very high volumes (subscription plans may be cheaper)
- —Looking up emails by name/domain (use the email-finder endpoint instead)
Quick start
curl -X POST https://hunter.mpp.paywithlocus.com/hunter/email-verifier \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <MPP_TOKEN>" \
-d '{"email": "john@example.com"}'Example
Request
{
"email": "john@example.com"
}Endpoint
Quality
The OpenAPI spec provides a clear request schema and pricing metadata, but response schemas are absent and the probe returned 404 (expected for POST-only endpoints probed with HEAD/GET). No live 402 challenge was captured for this specific path, and crawled pages yielded no additional documentation.
Warnings
- —Probe did not capture a 402 challenge — endpoint only accepts POST, but HEAD/GET were attempted
- —No response schema documented; consumers must infer response structure from Hunter.io API docs
- —Currency contract 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals; if different, the $0.008 price estimate may be incorrect
Citations
- —Hunter.io API documentation is available at https://hunter.io/api-documentation/v2https://hunter.io/api-documentation/v2
- —The email-verifier endpoint charges 8000 base units via Tempo method with currency 0x20c000000000000000000000b9537d11c60e8b50https://hunter.mpp.paywithlocus.com
- —LLM-oriented docs referenced at https://beta.paywithlocus.com/mpp/hunter.mdhttps://beta.paywithlocus.com/mpp/hunter.md