hyreflow
Integrations

Enrichley

Email validation with strong catch-all / risky-address handling, the final deliverability gate before sending. Provider-metered.

Use Enrichley as the final deliverability gate before a send: validate emails (from Apollo/Lusha/LeadMagic/FullEnrich), drop the undeliverable, and keep the catch-alls it clears.

Managed credits or BYOK: validate_email is 0.25 credits/validation. Auth is the x-api-key header (ENRICHLEY_API_KEY).

Capabilities

ToolDoesCost
validate_emailValidate one email; specialises in catch-all / risky verdicts0.25 credits/validation

Guidance

  • Run it last: as the deliverability gate after sourcing/enrichment, not as a finder.
  • Its strength is catch-all and risky-address handling; trust it to clear catch-alls other validators flag as unknown.
  • Loop per-row deterministically for volume: there's no native bulk method.
  • The provider caps a key at 10 requests/second. For a list of any size, prefer hyreflow enrich over a per-row loop — it paces the calls for you and persists every verdict as a dataset you can download or re-read later.
hyreflow tools execute enrichley validate_email \
  --payload '{"email":"[email protected]"}'

What a validation costs

Every verdict costs the same 0.25 credits — valid, invalid and catch_all alike. A verdict is the product, so an address the provider judges undeliverable is a delivered answer, not a miss.

A call that errors out costs nothing. When the provider fails — a rate limit, an outage, an account problem — the response is an error carrying credits_charged: 0 and the provider's own provider_status, and your balance is untouched:

{
  "detail": {
    "error": "provider_error",
    "provider": "enrichley",
    "method": "validate_email",
    "provider_status": 429,
    "credits_charged": 0.0,
    "run_id": 76271
  }
}

A successful verdict also carries the provider's own credits_consumed field. That is the provider counting its own metering, not yours — what Hyreflow charged you is always _meta.credits_charged.

Place Enrichley after the email-enrichment waterfall: enrich first, then validate the winners here before pushing to a sequencer, see Integrations Overview.

On this page