NeverBounce API
Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey11 EndpointsREST
For Agents
Verify a single email in real time or run bulk email verification jobs against lists, returning per-address deliverability classifications.
Use for: Verify a single email address with NeverBounce, Create a bulk verification job for a list of emails, Get the status of an existing NeverBounce job, Retrieve results for a finished verification job
Not supported: Does not handle email sending, marketing automation, or list management - use for email address deliverability verification only.
NeverBounce is an email verification service that classifies addresses as valid, invalid, accept-all, disposable, or unknown to protect sender reputation and reduce bounce rates. The API supports both single-address checks for real-time form validation and bulk verification jobs for cleaning lists with millions of addresses. Authentication uses a single API key passed as a query string parameter and account usage is exposed through a dedicated endpoint.
Install Jentic One Beta
Connect the NeverBounce API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NeverBounce 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%2Fneverbounce.com%2Fneverbounce" | 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%2Fneverbounce.com%2Fneverbounce" | 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 NeverBounce API.
Verify a single email address in real time and receive a deliverability classification with confidence flags
Create a bulk email verification job from an uploaded list or supplied input data
Start, search, and inspect status of bulk verification jobs by job id
Retrieve per-address results once a bulk job has finished processing
Download finished job results as a file for archival or import into other systems
Delete a finished verification job to remove the address list from NeverBounce storage
Fetch current account credit balance and usage figures through the account info endpoint
Use Cases
Patterns agents use NeverBounce API for, with concrete tasks.
★ Real-Time Sign-Up Email Verification
SaaS sign-up forms call GET /single/check the moment a user submits an email and reject the form when NeverBounce returns 'invalid' or 'disposable'. This catches typos and throwaway addresses at capture, lowering hard-bounce rates on welcome emails and protecting sender reputation.
Call GET /single/check?email=<submitted email>&key=<api key>; reject the sign-up if result is 'invalid' or 'disposable' and accept otherwise.
Pre-Send Email List Cleaning
Email marketing teams clean CSV exports before each campaign send by uploading the list through POST /jobs/create, kicking off the run with POST /jobs/start, polling GET /jobs/status until complete, and downloading clean results via GET /jobs/download. This lifts deliverability rates and reduces ESP throttling.
POST /jobs/create with the address list, POST /jobs/start with the returned job_id, poll GET /jobs/status every 30 seconds until status is 'complete', then GET /jobs/download to fetch the cleaned results.
Credit Balance Monitoring
Operations teams call GET /account/info on a schedule to track NeverBounce credit consumption and trigger an alert when the balance drops below a threshold. This avoids campaign sends being blocked because the verification step ran out of credits mid-job.
Schedule GET /account/info hourly, parse credits_remaining, and post an alert to the operations Slack channel when the value drops below 10000.
AI Agent Lead Verification
An AI lead-routing agent uses Jentic to discover NeverBounce operations and verifies each new lead's email through GET /single/check before writing the contact into the CRM. This keeps lead lists clean automatically without the developer hand-coding the NeverBounce client.
Use Jentic to search 'verify a single email address', load GET /single/check, and execute it for each inbound lead before any CRM write; quarantine leads where the result is 'invalid' or 'disposable'.
Key Endpoints
11 endpoints — neverbounce is an email verification service that classifies addresses as valid, invalid, accept-all, disposable, or unknown to protect sender reputation and reduce bounce rates.
METHOD
PATH
DESCRIPTION
GET
/account/info
Get account info and credit balance
GET
/single/check
Verify a single email address
POST
/jobs/create
Create a bulk verification job
POST
/jobs/start
Start a created job processing
GET
/jobs/status
Get job processing status
GET
/jobs/results
Get per-address job results
GET
/jobs/download
Download job results as a file
POST
/jobs/delete
Delete a job
GET
/account/info
Get account info and credit balance
GET
/single/check
Verify a single email address
POST
/jobs/create
Create a bulk verification job
POST
/jobs/start
Start a created job processing
GET
/jobs/status
Get job processing status
GET
/jobs/results
Get per-address job results
GET
/jobs/download
Download job results as a file
POST
/jobs/delete
Delete a job
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the NeverBounce API by hand means appending its key as a query parameter, targeting the api.neverbounce.com/v4.2 host, and polling the create, start, status, and results steps of a bulk job yourself. Through Jentic you install once, import NeverBounce from the API Directory, store the key once, and your agent calls it.
Permission scoping
NeverBounce drives its jobs through the request rather than as path resources, so limit the agent to the operations it needs, such as checking a single email or creating a job, and leave out the ones it should not run, such as deleting a job.
Credential isolation
Your NeverBounce API key is stored once, encrypted, by your own Jentic One instance and injected as the query key at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'verify a single email address' or 'run a bulk verification job', and Jentic returns the matching NeverBounce 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 NeverBounce API through Jentic.
What authentication does the NeverBounce API use?
NeverBounce uses an API key passed as a 'key' query string parameter on every request. Through Jentic, the API key is stored in the encrypted Jentic One instance and appended to outbound requests so the raw key never reaches the agent's context.
Can I verify a single email address in real time with the NeverBounce API?
Yes. GET /single/check accepts an email and returns one of valid, invalid, accept-all, disposable, or unknown along with confidence flags. This is the call to wire into sign-up forms and lead capture forms.
How do I run a bulk verification job through Jentic?
Search Jentic for 'create email verification job', load POST /jobs/create, supply the address list and execute. Then call POST /jobs/start with the returned job_id, poll GET /jobs/status until complete, and finally GET /jobs/download for the cleaned file.
What are the rate limits for the NeverBounce API?
Single verifications are tiered by plan with paid plans typically allowing tens of requests per second. Bulk jobs are queued server-side and processed at NeverBounce's pace - check the dashboard for the current concurrency and per-second cap on your plan.
How long do verification jobs stay available?
Job results remain accessible until you call POST /jobs/delete or until NeverBounce's retention window expires. Download results promptly and delete the job once they are imported into your own systems if data minimisation is a concern.
Is the NeverBounce API free?
NeverBounce offers free trial credits for new accounts; ongoing usage is metered per-verification and tracked through GET /account/info. There is no separate API tier - every paid plan includes API access.
Can I limit what my agent is allowed to do with the NeverBounce API?
Yes. Because you run Jentic One yourself, your own rules decide which NeverBounce operations and credentials the agent may use, and NeverBounce drives its jobs through request parameters rather than path resources. You can allow only the operations the agent needs, such as GET /single/check to verify one address or POST /jobs/create to start a bulk job, while withholding operations it should not run, such as POST /jobs/delete. The stored API key is injected at execution time only for the calls you permit, so the agent never gains open access to the full endpoint set.
GET STARTED