MillionVerifier API

Name: MillionVerifier API API
Brand: MillionVerifier API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST

For Agents

Verify whether an email address is deliverable, risky, disposable, or catch-all in real time and check remaining MillionVerifier credits.

Connect the MillionVerifier API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MillionVerifier 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.

Install Jentic One Beta (Self-Hosted)

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

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 MillionVerifier API API.

Verify a single email address in real time and receive a deliverability classification

Distinguish deliverable inboxes from risky, disposable, or catch-all addresses before sending

Pre-screen newly captured leads at sign-up to keep an email list clean

Check remaining MillionVerifier credits before queuing a verification batch

GET STARTED

Start building with MillionVerifier API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for MillionVerifier API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for MillionVerifier API, keeping it validated and agent-ready. MillionVerifier is a real-time email verification service that classifies email addresses as deliverable, risky, disposable, or part of a catch-all domain to protect sender reputation. The v3 API exposes two endpoints — a single-email verification call and a credit balance check — both authenticated by an API key passed as the api query parameter.

Use Cases

Patterns agents use MillionVerifier API API for, with concrete tasks.

★ Sign-Up Form Email Verification

Before accepting a new sign-up, an agent calls MillionVerifier on the submitted email address and rejects disposable or undeliverable entries at the door. The user gets immediate feedback and the database stays clean of bounce-prone records.

On form submit, call GET / with email=<submitted_email> and reject the form when the result is 'disposable' or 'invalid'.

Outbound Campaign List Cleaning

Before sending a marketing or transactional campaign, an agent verifies each address through MillionVerifier and drops invalid or risky entries. Sender reputation stays high and bounce rates stay below ESP thresholds.

For each email in the campaign list, call GET / with the email and drop the row if result is anything other than 'ok'.

Credit Monitoring

An agent watches the credit balance on the account and pings the team when it falls below a threshold so verification jobs do not stall mid-campaign. The credits endpoint returns the remaining balance for the API key in a single call.

Call GET /credits daily and post a Slack alert when the remaining count is below 10000.

Agent Email Verification via Jentic

Through Jentic, an agent verifies addresses by intent rather than by hand-coding the API call. The MillionVerifier API key sits in the Jentic vault and is injected as the api query parameter so an agent never holds the credential.

Use Jentic search 'verify an email address', load the schema for GET /, and execute with the email address in the query string.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

Verify a single email address

GET

/credits

Check remaining credits

GET

Verify a single email address

GET

/credits

Check remaining credits

Why though Jentic?

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

Credential isolation

The MillionVerifier API key is stored encrypted in the Jentic vault (MAXsystem) and appended to the request's 'api' query parameter at execution time. The raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'verify an email address') and Jentic returns the matching MillionVerifier operation with its input schema, so the agent calls GET / without parsing docs.

Time to first call

Direct MillionVerifier integration: half a day to wire the call, error handling, and credit monitoring. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ZeroBounce API

Email verification competitor with similar real-time and bulk surfaces.

Choose ZeroBounce when the team already has ZeroBounce credits or wants its activity-data add-ons; choose MillionVerifier when pricing per credit is the priority.

Alternative

NeverBounce API

Real-time email verification with strong ESP integrations.

Pick NeverBounce when integrating directly with marketing platforms it natively supports; pick MillionVerifier for a simple key-based real-time call.

Complementary

Hunter.io API

Finds emails by domain and verifies them — pairs well as a discovery layer above MillionVerifier.

Use Hunter to discover candidate emails for a domain, then run them through MillionVerifier for an independent verification check before sending.

FAQs

Specific to using MillionVerifier API API through Jentic.

Why is there no official OpenAPI spec for MillionVerifier API?

MillionVerifier does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MillionVerifier 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 MillionVerifier API use?

The API uses an API key passed as the 'api' query parameter on each request (the apiKeyQuery security scheme). Through Jentic, the key is held in the encrypted vault and appended to the query at execution time so it never enters the agent's context.

Can I distinguish disposable emails from catch-all domains?

Yes. The single GET / verification call returns a result classification that separates deliverable, undeliverable, risky/catch-all, and disposable addresses, which lets you treat each class differently in your sign-up or campaign flow.

What are the rate limits for the MillionVerifier API?

MillionVerifier scales by purchased credits rather than a hard request rate; each verification consumes one credit. Use GET /credits to monitor remaining balance and contact MillionVerifier support if you need negotiated throughput limits.

How do I verify an email address through Jentic?

Run pip install jentic, search for 'verify an email address', load the schema for GET /, and execute with email=<address>. Jentic injects your stored API key into the api query parameter automatically.

Can I verify multiple emails in one call?

Not on this real-time v3 endpoint. GET / verifies one address at a time. For batch verification, MillionVerifier offers a separate bulk file upload product that is not part of this real-time API.