Best email validation APIs

An email validation API is judged on latency at the signup form, documented rate limits, webhook support for bulk jobs, and what the response says about an address the service could not resolve.

How this was compared

Figures read from each vendor's own pages in September 2026. Where a vendor is missing from a column, we could not read it rather than estimating.

The short version

  • Real-time single-address latency, which is what decides whether the call fits in a signup form.
  • Documented rate limits, since an undocumented limit surfaces during your launch rather than in testing.
  • Bulk job support with webhooks, because polling a large job is a poor pattern for both sides.
  • Whether the response distinguishes an unresolved address from an invalid one, which is the field that matters most in code.
  • Published pricing read from each vendor's own page in September 2026.

At a glance

10,000 addressesCredit expiryBills unknowns
ZapBounceNot a verification vendor
ZeroBounceSubscription onlyCredits roll over while the subscription is activeNot stated
Bouncer$60Credits never expireNo
HunterPlans from $49 to $299 a monthCredits expire after 12 monthsNot stated
EmailableAbout $0.0076 an address with a subscriptionCredits never expireNo
EmailVerify.io$25 for 20,000Pay-as-you-go credits never expire; subscription credits roll two monthsNot stated
ClearoutNot listedCredits never expire and roll overNot stated

Vendor figures read from their own pricing pages in September 2026. Confirm before purchase, because prices move.

The ranking

Best first, with the situation each one wins and the situation it loses.

ZapBounce

Unresolved comes back as its own result with a reason attached, rather than collapsing into invalid, and those responses carry no charge. One endpoint for an address, one for a list, a webhook when a long job finishes.

Best for:
An integration where a wrong invalid is more expensive than a missing verdict, such as a signup form that would block a real customer.
Not for:
A team that needs production references before it writes against an API. Ours has no operating history yet.

ZeroBounce

The widest API surface here, with activity data and scoring endpoints beyond the validation call itself.

Best for:
Teams who want one API for validation, scoring and deliverability data.
Not for:
Small-scale API use, given the credit minimum at the entry point.

Bouncer

Clear documentation, predictable rate limits, and a stated policy of not billing unknowns that carries through to the API response.

Best for:
Production integrations where predictable behavior under load matters more than feature count.
Not for:
Teams needing address discovery, which is not part of the product.

Hunter

Finding and verifying in one API, which removes a whole integration for teams doing both.

Best for:
Sales tooling that needs to discover an address and check it in one flow.
Not for:
High-volume validation, since verification costs half a credit against a plan built for finding.

Emailable

A straightforward API with a mature integration ecosystem and refunds for results it could not resolve.

Best for:
Teams who want the integration work already done for a common marketing stack.
Not for:
Small jobs, given the 5,000-credit minimum.

EmailVerify.io

Competitive pricing and an MCP endpoint, which puts them ahead of most of this category on agent-facing access.

Best for:
Teams building with AI agents that need a tool rather than a REST client.
Not for:
Buyers who need an accuracy figure with a denominator attached.

Clearout

A real-time API with Form Guard for checking addresses at the signup form, plus catch-all resolution attempts.

Best for:
Signup forms on B2B products where catch-all domains are common among your users.
Not for:
Price comparison, since per-volume rates are not listed on their pricing page.

Our own first place, and what it does not cover

When none of these is the answer

If you are validating at a signup form and can tolerate a DNS lookup instead of a full check, an MX record query is one query, costs nothing, and eliminates typo domains entirely. That covers a large share of real signup errors without an API at all.

Questions people ask

Should a validation API block a signup?

No. Use a short timeout and accept the registration whatever comes back. An unresolved result usually means a server refused the probe, and blocking that person costs you a customer over somebody else's policy.

What latency is acceptable at a signup form?

Under a second, with a timeout that fails open. An SMTP check involves a DNS lookup and a live connection, so a slow receiving server is entirely outside the vendor's control.

Why do some vendors here have no pricing listed?

NeverBounce, Kickbox and MillionVerifier blocked automated checks or did not publish reachable pricing, so they appear here without figures rather than with numbers sourced from somewhere else.

Run the same sample through two of them

100 free checks a month, no card. Compare how many addresses each one declined to judge, which matters more than either accuracy claim.