For Agents
Verify email deliverability and check the Bouncify account credit balance through two endpoints.
Get started with Bouncify Email Verification API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"verify an email address with Bouncify"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Bouncify Email Verification API 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
Report the remaining credit balance on a Bouncify account
GET STARTED
Use for: Verify the email user@example.com before adding it to a marketing list, Check whether sales+test@example.org is a valid mailbox, Get the remaining verification credits on our Bouncify account, Find out if newuser@startup.io is a disposable address
Not supported: Does not handle email sending, list storage, or domain reputation monitoring — use for real-time email address verification and credit balance checks only.
Jentic publishes the only available OpenAPI document for Bouncify Email Verification API, keeping it validated and agent-ready.
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.
Include free email provider and domain detail in the response
Patterns agents use Bouncify Email Verification API 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
2 endpoints — jentic publishes the only available openapi specification for bouncify email verification api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v1/verify
Verify a single email address
/v1/info
Get remaining credit balance for the account
/v1/verify
Verify a single email address
/v1/info
Get remaining credit balance for the account
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.
Alternatives and complements available in the Jentic catalogue.
ZeroBounce API
Email verification provider with similar real-time and bulk capabilities to Bouncify.
Use ZeroBounce when the team prefers its scoring and additional data fields; use Bouncify for a simpler two-endpoint integration.
NeverBounce API
Email verification provider with bulk job and integration features.
Use NeverBounce for bulk verification jobs with progress polling; use Bouncify for synchronous single-address checks.
Kickbox API
Email verification with deliverability scoring and a free tier.
Use Kickbox when the team needs a known free tier and Sendex score; use Bouncify for a lean credit-based offering.
Hunter.io API
Email finder API that pairs with Bouncify to verify the addresses Hunter discovers.
Use Hunter to find email addresses for a domain; pipe them through Bouncify to confirm each is deliverable before outreach.
Specific to using Bouncify Email Verification API 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.