Bouncify Email Verification API

Name: Bouncify Email Verification API
Brand: Bouncify Email Verification API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST

For Agents

Verify email deliverability and check the Bouncify account credit balance through two endpoints.

Install Jentic One Beta

Connect the Bouncify Email Verification API to your agent

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

Verify a single email address in real time and return its deliverability status

Detect role-based, disposable, and accept-all email addresses

Return SMTP-level reasons such as invalid mailbox or domain not found

GET STARTED

Start building with Bouncify Email Verification API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Bouncify Email Verification API for, with concrete tasks.

★ Signup form email validation

SaaS and e-commerce signup flows verify the email before completing the account so they reject typos, disposable addresses, and undeliverable domains at the front door. GET /v1/verify returns the deliverability status in real time, allowing the frontend to surface a clear message and the backend to skip welcome emails to bad addresses. Most teams ship the integration in under a day.

Call GET /v1/verify with email new@example.com and reject the signup if the result is undeliverable or disposable

List hygiene before sending campaigns

Marketing teams clean their lists before each campaign to protect sender reputation and reduce bounce rates. The team batches addresses through GET /v1/verify and removes anything that comes back undeliverable, role-based, or accept-all when those policies fit the campaign. Teams typically run this nightly or before each major send.

Verify a list of 100 email addresses through GET /v1/verify, log undeliverable and disposable results, and return the cleaned list

Credit balance monitoring for billing alerts

Operations teams monitor Bouncify credit balance so verifications never silently fail when credits run out. GET /v1/info returns the remaining balance, and a daily check feeds an alert into Slack or email when the balance drops below a threshold. The check is a single GET and goes live the same day.

Call GET /v1/info, parse the remaining credits, and post a Slack alert if the balance is under 1000

Agent-driven email validation via Jentic

An AI agent triages inbound leads from a form and verifies each email before pushing it to the CRM. Through Jentic the agent searches for 'verify an email with Bouncify', loads the schema, and executes the call while the apikey query parameter stays inside the Jentic vault.

Search Jentic for 'verify an email with Bouncify', load the GET /v1/verify schema, and execute it for lead@example.com, returning the deliverability result

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/v1/verify

Verify a single email address

GET

/v1/info

Get remaining credit balance for the account

GET

/v1/verify

Verify a single email address

GET

/v1/info

Get remaining credit balance for the account

Why Jentic?

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

Credential isolation

The Bouncify apikey is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access only; the raw key never appears in prompts, logs, or tool outputs even though the API expects it as a query parameter.

Intent-based discovery

Agents search Jentic for intents like 'verify an email' or 'check Bouncify credit balance' and Jentic returns the matching operations with their input schemas, so the agent calls the right endpoint without crawling docs.

Time to first call

Direct Bouncify integration: a few hours for auth and response handling. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using Bouncify Email Verification API through Jentic.

Why is there no official OpenAPI spec for Bouncify Email Verification API?

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

Bouncify uses an API key passed as the apikey query parameter on each request. In Jentic the key is stored in the vault and injected at execution so it never appears in agent prompts or tool outputs.

Can I verify a single email address with the Bouncify Email Verification API?

Yes. Call GET /v1/verify with the email address; the response includes the deliverability result plus signals for disposable, role-based, and accept-all addresses so callers can apply their own acceptance policy.

How do I check my remaining verification credits through Jentic?

Run pip install jentic, then search Jentic for 'Bouncify credit balance', load the GET /v1/info schema, and execute it. Jentic injects the apikey query parameter automatically and returns the credit balance.

What are the rate limits for the Bouncify Email Verification API?

Bouncify does not document explicit per-second rate limits in the spec; verifications are gated by the credit balance on the account. For large list cleans, batch and stagger calls rather than firing thousands in parallel to keep latency predictable.

Is the Bouncify Email Verification API free to use?

Bouncify charges per verification using a credit model rather than a free unlimited plan; GET /v1/info reports the remaining balance. Confirm current pricing on bouncify.io before billing-sensitive integrations.