Email Verifier API
Agent-ready OpenAPI document · curated by JenticData EnrichmentContact EnrichmentapiKey2 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Verify whether an email address is deliverable through syntax, MX, disposable, and mailbox checks, individually or in bulk.
Use for: I need to verify an email address before accepting a sign-up, Check whether an address is disposable or role-based, Validate a list of customer emails for deliverability, Find all undeliverable addresses in an uploaded CSV
Not supported: Does not handle email sending, contact storage, or marketing automation - use for email address verification only.
Jentic publishes the only available OpenAPI specification for Email Verifier API, keeping it validated and agent-ready. Email Verifier API performs syntax checks, MX record lookups, disposable address detection, and SMTP-level mailbox verification on individual addresses or batches. Results indicate whether an address is deliverable, risky, or invalid, with a confidence signal usable in form gates and list hygiene jobs. Use it before pushing new sign-ups to your sending platform or before re-engaging an aged list.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Femailverifierapi.com%2Femailverifierapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Femailverifierapi.com%2Femailverifierapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Confirm MX records exist for the address domain before accepting a registration
Score addresses as deliverable, risky, or undeliverable to drive list segmentation
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?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Email Verifier API by hand means handling its API key passed as a query parameter, formatting single and bulk verification calls, and managing your own retries against https://emailverifierapi.com. Through Jentic you install once, import Email Verifier API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Email Verifier API works through two POST operations (/v2 for a single address and /v2/bulk for a list) with no resource id in the URL path, so scope it by operation: limit the agent to the operations it needs, such as single-address verification, and leave bulk verification out of the allowed set unless you add it.
Credential isolation
Your Email Verifier API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check if an email address is deliverable' or 'verify a list of addresses', and Jentic returns the matching Email Verifier operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the Email Verifier API?
Yes. Because you run Jentic One yourself, your own rules decide which Email Verifier API operations and credentials the agent may use. This API exposes just two operations, single-address verification at POST /v2 and bulk verification at POST /v2/bulk, so you can scope by operation: allow only single-address verification and leave bulk verification out of the agent's permitted set. The stored API key is injected at execution time under those same rules, so the agent can call only what you have approved.
GET STARTED