Email Verifier API
Email Verifier API is a real-time email verification service offering a 16-point engine that validates deliverability through syntax checking, DNS / MX lookups, real-time SMTP handshakes, mailbox existence probing, catch-all and greylisting detection, disposable address detection, role-account flagging, spam-trap and complainer detection, gibberish and offensive-language scanning, B2B / B2C classification, typo correction, and SMTP provider identification. The service is delivered as a single REST endpoint that accepts GET or POST requests, returns JSON or XML, and meters usage against a credit-pack balance that never expires. The product targets growth teams, ESPs, and lead-generation operators that need to eliminate hard bounces and protect sender reputation before they send.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Email Verifier API the way a machine reads it — 39 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Email Verifier API scores 64.6/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Email Verifier API
Each block below is one kind of artifact we hold for Email Verifier API. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Email Verifier API Verification API
Real-time email-address verification operations.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Email Verifier API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Email Verifier Api Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 12
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
16-Point Verification Engine
Composite engine combining syntax, DNS, MX, SMTP handshake, mailbox existence, catch-all, greylisting, disposable, role, spam-trap, gibberish, offensive, B2B, typo, complainer, ...
Real-Time SMTP Verification
Live RCPT TO probe against the destination MX to confirm mailbox existence in real time.
Disposable Detection
Match against 50,000+ known disposable / burner email providers.
Role-Account Detection
Flag departmental aliases such as info@, sales@, support@, marketing@.
Catch-All Detection
Identify domains whose MX accepts all addresses regardless of mailbox existence.
Greylisting Handling
Distinguish temporary SMTP defenses from outright rejections so they can be retried.
Typo Suggestion
Detect domain misspellings (gmial.com -> gmail.com) and return a corrected address.
Spam-Trap and Complainer Detection
Identify honeypots and chronic spam-complainer addresses before they damage sender reputation.
B2B / B2C Classification
Classify addresses as corporate (B2B) versus consumer (B2C) free-mailbox providers.
Credit-Based Metering
Pay-as-you-go credit packs that never expire; only Paid (mailbox-level) events consume credits.
JSON or XML Response
JSON by default; XML available with `xml=true`.
GET or POST
Both GET and POST supported on the single endpoint for ad-hoc and server-to-server use.
Scroll within the panel for all 12 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Email Verifier Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Email Verifier API API Rules
SPECTRALEmail Verifier API API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
VerificationResult
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Email Verifier Api Verification Result Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Signup Validation
Block disposable, role, and invalid addresses at registration to keep user lists clean.
Pre-Send List Cleaning
Run marketing lists through verification before a send to lower bounce rate and protect IP / domain reputation.
Lead Quality Scoring
Score inbound leads on B2B vs B2C, role-account, and disposable signals to prioritize sales follow-up.
ESP Bounce Prevention
Reduce hard bounces on transactional and marketing sends to maintain ISP reputation.
Typo Recovery at Form Submit
Use `emailSuggested` to prompt users with the corrected address inline at signup.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Salesforce
Apex HTTP-callout integration for lead validation inside Salesforce.
Google Sheets
Spreadsheet workflow for ad-hoc list verification.
Microsoft Excel
Spreadsheet workflow for ad-hoc list verification.
HubSpot
Marketing-platform integration for list cleansing.
Pipedrive
CRM integration for inbound lead validation.
Resources
Every other property we hold for Email Verifier API — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/email-verifier-api · machine-readable index on apis.io