canonical: https://jentic.com/apis/bouncify.io/bouncify

# Bouncify Email Verification API

Jentic publishes the only available OpenAPI specification for Bouncify Email Verification API, keeping it validated and agent-ready. Bouncify is a real-time email verification service used to validate addresses before sending campaigns or saving leads. The API has two endpoints: GET `/v1/verify` checks a single email and returns the deliverability result, and GET `/v1/info` reports the account's remaining verification credit balance. Authentication uses an apikey query parameter.

## For AI agents

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

## Scope

Does not handle email sending, list storage, or domain reputation monitoring - use for real-time email address verification and credit balance checks only.

## Capabilities

- 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
- Report the remaining credit balance on a Bouncify account
- Include free email provider and domain detail in the response

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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 your Jentic One instance.

Example prompt: 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

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/verify` | Verify a single email address |
| GET | `/v1/info` | Get remaining credit balance for the account |

## Key resources

- **Verification** — Real-time single email address verification with deliverability and SMTP detail
- **Account** — Remaining credit balance on the Bouncify account

## Why Jentic

- **Setup:** Wiring Bouncify by hand means appending the apikey query parameter to each request and handling the verify and info calls yourself. Through Jentic you install once, import the Bouncify Email Verification API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Bouncify verifies an address through a query parameter rather than a resource path, so scope the agent to the operations it needs, such as verifying an email, and add the credit balance check only if the agent requires it. Every operation you allow is one you have explicitly chosen.
- **Credential handling:** Your Bouncify apikey is stored once, encrypted, by your own Jentic One instance and injected as the query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'verify an email' or 'check Bouncify credit balance', and Jentic returns the matching Bouncify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **ZeroBounce API** — Email verification provider with similar real-time and bulk capabilities to Bouncify.
- **NeverBounce API** — Email verification provider with bulk job and integration features.
- **Kickbox API** — Email verification with deliverability scoring and a free tier.
- **Hunter.io API** — Email finder API that pairs with Bouncify to verify the addresses Hunter discovers.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Bouncify Email Verification API?

Yes. Because you run Jentic One yourself, you decide which Bouncify operations the agent may call, so you can allow only GET `/v1/verify` to check a single email address and withhold the GET `/v1/info` credit balance lookup unless the agent genuinely needs it. Every operation you grant is one you have explicitly chosen, and the agent cannot reach anything you have not enabled. Your own rules also govern the stored apikey, which your Jentic One instance injects as the query parameter at execution time rather than exposing it to the agent.