Email Verifier API

Name: Email Verifier API
Brand: Email Verifier API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST

For Agents

Verify whether an email address is deliverable through syntax, MX, disposable, and mailbox checks, individually or in bulk.

Install Jentic One Beta

Connect the Email Verifier API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Email Verifier API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Email Verifier API.

Verify a single email address with syntax, domain, and mailbox checks in one call

Submit a batch of addresses for bulk verification and read aggregate deliverability scores

Detect disposable, role-based, and free webmail addresses to filter sign-up forms

GET STARTED

Start building with Email Verifier API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Email Verifier API for, with concrete tasks.

★ Sign-Up Form Email Gating

Validate an email address inline at sign-up so disposable, mistyped, or undeliverable addresses never enter the user database. The API returns a single JSON object with deliverability status and category flags such as disposable or role. Product teams use this to cut bounce rates on welcome emails and reduce noise in product analytics.

POST /v2 with the candidate email and an apiKey query parameter, then accept the sign-up only when the response indicates a deliverable, non-disposable address.

Bulk List Hygiene

Run a CSV of historical contacts through bulk verification to remove undeliverable and risky addresses before a re-engagement campaign. The bulk endpoint accepts the list and returns per-address verdicts so the sender list can be filtered to deliverable addresses only. Marketing operations teams typically run this monthly or before major sends to protect sender reputation.

POST /v2/bulk with the array of addresses and partition the response into deliverable, risky, and undeliverable buckets.

Disposable Address Detection

Reject disposable inbox providers at the point of sign-up to discourage abuse on free trials and gated downloads. The single-verify endpoint surfaces a disposable flag alongside its main deliverability verdict. Growth and trust teams enforce this on free-tier flows where one user per address matters.

POST /v2 for the address, read the disposable flag, and surface a 'use a permanent email' error when it is true.

Agent-Driven Verification at Form Submission

An agent inside an onboarding workflow takes the user-provided email, verifies it through Email Verifier API, and writes the verdict back to the customer record so downstream emails can be conditionally routed. Through Jentic the agent searches by intent, loads the schema, and executes the call without a hand-coded client. Integration takes under an hour rather than a day of bespoke wiring.

Search Jentic for 'verify an email address', execute POST /v2 with the address, and update the customer record with the deliverability verdict.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for email verifier api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2

Verify a single email address

POST

/v2/bulk

Verify a batch of email addresses

POST

/v2

Verify a single email address

POST

/v2/bulk

Verify a batch of email addresses

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Email Verifier API key is stored encrypted in the Jentic vault. Agents receive a scoped token — the raw key never enters the agent's context, and Jentic injects it as the apiKey query parameter at execution time.

Intent-based discovery

Agents search by intent (e.g., 'verify an email address') and Jentic returns matching Email Verifier operations with their input schemas, so the agent calls the right endpoint without reading docs.

Time to first call

Direct Email Verifier integration: half a day for client code, key handling, and bulk job orchestration. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Email Verifier API through Jentic.

Why is there no official OpenAPI spec for Email Verifier API?

Email Verifier API does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Email Verifier API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Email Verifier API use?

The API uses an API key passed as the apiKey query parameter on each request. Through Jentic, the key is stored encrypted in the vault and the agent never sees it directly — Jentic injects it at execution time.

Can I verify multiple addresses in a single call with the Email Verifier API?

Yes. POST /v2/bulk accepts an array of addresses and returns per-address verdicts in one response, which is the recommended path for list hygiene jobs.

How do I verify a sign-up email through Jentic?

Search Jentic with the query 'verify an email address', load the schema for POST /v2, and execute it with the candidate address. Jentic injects the API key, so the agent reads only the deliverability verdict.

What are the rate limits for the Email Verifier API?

The OpenAPI spec does not declare quantitative rate limits; limits are enforced by plan tier on emailverifierapi.com. Treat HTTP 429 responses as authoritative and back off using the Retry-After header where present.

Does the Email Verifier API detect disposable addresses?

Yes. POST /v2 returns category flags including disposable and role-based, so sign-up flows can reject temporary inbox providers before the account is created.

Email Verifier API

Connect the Email Verifier API to your agent

Capabilities

Start building with Email Verifier API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs