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.

Email Verifier API publishes 1 API contract indexed on the APIs.io network: Verification API. Tagged areas include Email Verification, Deliverability, SMTP Check, Bounce Prevention, and Lead Validation.

The Email Verifier API catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Email Verifier API’s developer surface includes authentication, documentation, signup flow, pricing, engineering blog, support, API reference, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

52.8/100 developing ▬ flat Agent 33/100 agent ready Front door AI 1/6 silent Heartbeat 83/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 3 Agent Skills 12 Features 5 Use Cases

Email Verification DeliverabilitySMTP CheckBounce PreventionLead ValidationDisposable DetectionSpam Trap DetectionCatch-All DetectionGreylistingRole Account DetectionTypo SuggestionB2B Lead Scoring

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 52.8/100 · developing

Contract Quality 11.5 / 19

Developer Ergonomics 6.9 / 15

Access Clarity 11.6 / 15

Operational Transparency 0.8 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/email-verifier-api/"><img src="https://apis.io/badge/email-verifier-api/card.svg" alt="Email Verifier API on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Operational Transparency scores 7.9 — up to +12.0 composite points
Developer Ergonomics scores 45.8 — up to +10.8 composite points
Contract Quality scores 61.2 — up to +9.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/email-verifier-api/apis.yml: open an issue on github.com/api-evangelist/email-verifier-api to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Email Verifier API Verification API

Real-time email-address verification operations.

Postman Collections 1

Ready-to-run Postman collections for exercising this provider's APIs.

Email Verifier Verification API

POSTMAN

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Email Verifier Verification API

OPEN COLLECTION

Email Verifier API

OPEN COLLECTION

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Clean a marketing list before a send

AGENT SKILL

Gate a signup form with real-time verification

AGENT SKILL

Verify a single email address

AGENT SKILL

Email Verifier API pricing

Prices published by Email Verifier API, read 2026-10-28 from emailverifierapi.com/pricing/.

Plan	Price
100 Credits	FREE Includes: 100 credits, no credit card required
1,000 Credits	$9.95 Includes: $0.0099 per email
5,000 Credits	$34.95 Includes: $0.0070 per email
10,000 Credits	$49.95 Includes: $0.0050 per email
25,000 Credits	$124.95 Includes: 1 Email = $0.0050
50,000 Credits	$249.95 Includes: $0.0050 per email
100,000 Credits	$399.95 Includes: 1 Email = $0.0040
250,000 Credits	$749.95 Includes: $0.0030 per email

All 14 plans, limits and sources →

Rate limits

Credit balance (paid events): customer balance credit
Free tool daily checks: 5 request
Per-request execution time: sub-500ms typical seconds

Compiled by API Evangelist, not yet checked against Email Verifier API's documentation. Rate-limit details →

Billed by: 1,000 credits · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Email Verifier Api Plans Pricing

14 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Email Verifier Api Rate Limits

3 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Email Verifier API

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Email Verifier Api Finops

FINOPS

Features 12

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 for all 12

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Email Verifier Api Context

18 classes · 3 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Email Verifier API — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

Email Verifier API API Rules

9 rules · 6 errors 3 warnings

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Email Verifier Api Verification Api Overlay

7 actions · update · email-verifier-api-verification-api-openapi.yml

DERIVED

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

VerificationResult

18 properties

JSON SCHEMA

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Email Verifier Api Verification Result Structure

18 properties

JSON STRUCTURE

Examples 4

Example request and response payloads for these APIs.

Email Verifier Api Disposable Example

18 fields

EXAMPLE

Email Verifier Api Mailbox Does Not Exist Example

18 fields

EXAMPLE

Email Verifier Api Mailbox Exists Example

18 fields

EXAMPLE

Email Verifier Api Typo Suggest Example

18 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Email Verifier Api Authentication

apiKey · 1 scheme

SECURITY

Email Verifier Api Domain Security

TLSv1.3 · HSTS

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Email Verifier Api Agentic Access

2 operations · 1 acting

AGENTIC

Use Cases 5

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 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

Get Started 2

Portal, sign-up, and the first successful call

Signup

Signup

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

LlmsText

LLMsTxt

AgentSkill

WellKnownProbe

MCPCandidate

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Lifecycle

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

FreeTool

FreeTool

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Directory

Source (apis.yml)

aid: email-verifier-api
url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/apis.yml
name: Email Verifier API
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  probe_state: blocked
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/email-verifier-api.png
description: '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.'
created: '2026-05-06'
modified: '2026-08-13'
specificationVersion: '0.23'
tags:
- Email Verification
- Deliverability
- SMTP Check
- Bounce Prevention
- Lead Validation
- Disposable Detection
- Spam Trap Detection
- Catch-All Detection
- Greylisting
- Role Account Detection
- Typo Suggestion
- B2B Lead Scoring
url-source: https://emailverifierapi.com/
apis:
- aid: email-verifier-api:email-verifier-api-verification-api
  name: Email Verifier API Verification API
  description: Real-time email-address verification operations.
  humanURL: https://emailverifierapi.com/api-docs/
  baseURL: https://emailverifierapi.com/v2/
  tags:
  - Verification
  properties:
  - type: OpenAPI
    url: openapi/email-verifier-api-verification-api-openapi.yml
  - type: Documentation
    url: https://emailverifierapi.com/api-docs/
  - type: Signup
    url: https://emailverifierapi.com/register/
  - type: Pricing
    url: https://emailverifierapi.com/pricing/
  - type: TermsOfService
    url: https://emailverifierapi.com/terms-of-service/
  - type: PrivacyPolicy
    url: https://emailverifierapi.com/privacy-policy/
  - type: Login
    url: https://emailverifierapi.com/login/
  - type: Blog
    url: https://emailverifierapi.com/blog/
  - type: Integrations
    url: https://emailverifierapi.com/integrations/
  - type: FreeTool
    url: https://emailverifierapi.com/free-email-verifier/
  - type: Directory
    url: https://emailverifierapi.com/verify-company-emails/
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/json-schema/email-verifier-api-verification-result-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/json-structure/email-verifier-api-verification-result-structure.json
  - type: JSONLD
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/json-ld/email-verifier-api-context.jsonld
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/rules/email-verifier-api-rules.yml
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/vocabulary/email-verifier-api-vocabulary.yml
  - type: Plans
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/plans/email-verifier-api-plans-pricing.yml
  - type: RateLimits
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/rate-limits/email-verifier-api-rate-limits.yml
  - type: FinOps
    url: https://raw.githubusercontent.com/api-evangelist/email-verifier-api/refs/heads/main/finops/email-verifier-api-finops.yml
common:
- type: Plans
  url: plans/email-verifier-api-plans-pricing.yml
- type: RateLimits
  url: rate-limits/email-verifier-api-rate-limits.yml
- type: FinOps
  url: finops/email-verifier-api-finops.yml
- type: Website
  url: https://www.emailverifierapi.com/
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/email-verifier-api/overview
- type: AgenticAccess
  url: agentic-access/email-verifier-api-agentic-access.yml
- type: DomainSecurity
  url: security/email-verifier-api-domain-security.yml
- type: Authentication
  url: authentication/email-verifier-api-authentication.yml
- type: Documentation
  url: https://emailverifierapi.com/api-docs/
- type: Signup
  url: https://emailverifierapi.com/register/
- type: Login
  url: https://emailverifierapi.com/login/
- type: Pricing
  url: https://emailverifierapi.com/pricing/
- type: Blog
  url: https://emailverifierapi.com/blog/
- type: TermsOfService
  url: https://emailverifierapi.com/terms-of-service/
- type: PrivacyPolicy
  url: https://emailverifierapi.com/privacy-policy/
- type: Integrations
  url: https://emailverifierapi.com/integrations/
- type: FreeTool
  url: https://emailverifierapi.com/free-email-verifier/
- type: Directory
  url: https://emailverifierapi.com/verify-company-emails/
- type: Support
  url: mailto:support@emailverifierapi.com
- type: Authentication
  description: API key passed as the `apiKey` query parameter on every request.
- type: Features
  data:
  - name: 16-Point Verification Engine
    description: Composite engine combining syntax, DNS, MX, SMTP handshake, mailbox existence, catch-all, greylisting, disposable,
      role, spam-trap, gibberish, offensive, B2B, typo, complainer, and SMTP-provider checks.
  - name: Real-Time SMTP Verification
    description: Live RCPT TO probe against the destination MX to confirm mailbox existence in real time.
  - name: Disposable Detection
    description: Match against 50,000+ known disposable / burner email providers.
  - name: Role-Account Detection
    description: Flag departmental aliases such as info@, sales@, support@, marketing@.
  - name: Catch-All Detection
    description: Identify domains whose MX accepts all addresses regardless of mailbox existence.
  - name: Greylisting Handling
    description: Distinguish temporary SMTP defenses from outright rejections so they can be retried.
  - name: Typo Suggestion
    description: Detect domain misspellings (gmial.com -> gmail.com) and return a corrected address.
  - name: Spam-Trap and Complainer Detection
    description: Identify honeypots and chronic spam-complainer addresses before they damage sender reputation.
  - name: B2B / B2C Classification
    description: Classify addresses as corporate (B2B) versus consumer (B2C) free-mailbox providers.
  - name: Credit-Based Metering
    description: Pay-as-you-go credit packs that never expire; only Paid (mailbox-level) events consume credits.
  - name: JSON or XML Response
    description: JSON by default; XML available with `xml=true`.
  - name: GET or POST
    description: Both GET and POST supported on the single endpoint for ad-hoc and server-to-server use.
- type: UseCases
  data:
  - name: Signup Validation
    description: Block disposable, role, and invalid addresses at registration to keep user lists clean.
  - name: Pre-Send List Cleaning
    description: Run marketing lists through verification before a send to lower bounce rate and protect IP / domain reputation.
  - name: Lead Quality Scoring
    description: Score inbound leads on B2B vs B2C, role-account, and disposable signals to prioritize sales follow-up.
  - name: ESP Bounce Prevention
    description: Reduce hard bounces on transactional and marketing sends to maintain ISP reputation.
  - name: Typo Recovery at Form Submit
    description: Use `emailSuggested` to prompt users with the corrected address inline at signup.
- type: Integrations
  data:
  - name: Salesforce
    description: Apex HTTP-callout integration for lead validation inside Salesforce.
  - name: Google Sheets
    description: Spreadsheet workflow for ad-hoc list verification.
  - name: Microsoft Excel
    description: Spreadsheet workflow for ad-hoc list verification.
  - name: HubSpot
    description: Marketing-platform integration for list cleansing.
  - name: Pipedrive
    description: CRM integration for inbound lead validation.
- type: SDKs
  data:
  - name: Node.js
  - name: Python
  - name: PHP
  - name: Ruby
  - name: Go
  - name: Java
  - name: C# / .NET
  - name: Rust
  - name: Kotlin
  - name: Swift
  - name: TypeScript
  - name: Elixir
  - name: Dart / Flutter
  - name: Scala
  - name: Clojure
  - name: F#
  - name: VB.NET
  - name: Perl
  - name: Lua
  - name: Julia
  - name: R
  - name: Crystal
  - name: ObjectiveC
  - name: ColdFusion
  - name: ClassicASP
  - name: PowerShell
  - name: VBScript
  - name: Delphi
  - name: cURL / Bash
  - name: OpenResty / NGINX
- type: LlmsText
  url: https://emailverifierapi.com/llms.txt
- type: APIReference
  url: https://emailverifierapi.com/api-docs/
- type: LLMsTxt
  url: llms/email-verifier-api-llms.txt
- type: Packages
  url: packages/email-verifier-api-packages.yml
- type: Conventions
  url: conventions/email-verifier-api-conventions.yml
- type: ErrorCatalog
  url: errors/email-verifier-api-problem-types.yml
- type: DataModel
  url: data-model/email-verifier-api-data-model.yml
- type: Lifecycle
  url: lifecycle/email-verifier-api-lifecycle.yml
- type: Conformance
  url: conformance/email-verifier-api-conformance.yml
- type: Overlay
  url: overlays/email-verifier-api-verification-api-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnownProbe
  url: well-known/email-verifier-api-well-known.yml
  description: Probe record only. Every /.well-known/ path returned 403 from the provider's firewall; no document is served,
    so no WellKnown / SecurityTxt pointer is emitted.
- type: MCPCandidate
  url: mcp/email-verifier-api-mcp.yml
  description: Derived candidate tool surface. The provider publishes no MCP server, so no MCPServer pointer is emitted.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-13'
  status: minimal
  artifacts_added: 14
  pass: local-v1
x-coverage:
  state: blocked
  reason: bot-challenge
  detail: The origin at 159.65.41.138 answers non-browser clients with its own "403 Forbidden / Access Denied / Firewall Protection"
    interstitial and then drops the connection entirely, and it refused our second egress at the TCP layer (ECONNREFUSED)
    on that egress's very first request — so neither the published llms.txt, the api-docs reference, nor any /.well-known/
    path could be read this pass, and every new artifact had to be derived from the OpenAPI already harvested in an earlier
    round.
  evidence:
  - url: https://emailverifierapi.com/openapi.json
    status: 404
  - url: https://emailverifierapi.com/llms.txt
    status: 403
  - url: https://emailverifierapi.com/.well-known/security.txt
    status: 403
  - url: https://emailverifierapi.com/.well-known/agent-card.json
    status: 403
  - url: https://emailverifierapi.com/api-docs/
    status: 0
  checked: '2026-08-13'

Email Verifier API — frequently asked questions

Does Email Verifier API have an API?

Yes. APIs.io lists 1 API from Email Verifier API, including Email Verifier API Verification API.

Is there an OpenAPI specification for the Email Verifier API?

Yes. APIs.io indexes 1 OpenAPI specification for Email Verifier API, each linked for download from this page.

How do I authenticate with the Email Verifier API?

Email Verifier API uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Email Verifier Api Authentication.

How much does the Email Verifier API cost?

Email Verifier API publishes its prices; its 100 Credits plan is FREE as of 2026-10-28. APIs.io lists 14 pricing plans for Email Verifier API, with each plan's price, limits and inclusions under Pricing on this page.

Is the Email Verifier API ready for AI agents?

Email Verifier API has a Kin Score of 52.8 out of 100 (developing) and an Agent Readiness score of 32.9 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/email-verifier-api"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/email-verifier-api/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/email-verifier-api/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.