canonical: https://jentic.com/apis/bulkemailchecker.com/bulkemailchecker # Bulk Email Checker API The Bulk Email Checker API verifies a single email address in real time and returns a deliverability verdict drawn from more than seventeen checks. It runs RFC syntax validation, DNS and MX record lookups, disposable and role account detection, catch-all server identification, spam trap screening, anti-greylisting, and a full SMTP handshake. You pass the address to verify along with your key, optionally request an XML response or attach a label, and read back the verification result. ## For AI agents Verify a single email address in real time and get a deliverability verdict from syntax, DNS, MX, SMTP, and risk checks. Authenticates with an API key passed as a query parameter. ## Scope Does not handle email sending, inbox monitoring, or contact data enrichment. Use for verifying a single email address in real time only. ## Capabilities - Verify a single email address in real time - Run RFC syntax, DNS, and MX record checks on an address - Detect disposable, role, and catch-all addresses - Screen for spam traps and run an SMTP deliverability handshake ## Use cases ### Agent Email Verification An AI agent connected through Jentic verifies an email address before it is used, reading back a deliverability verdict so the agent can decide whether to send or ask for a correction. Because the check runs in real time, the agent gets the result within the same step rather than queuing a batch job. Example prompt: Verify the address user@example.com and return whether it is deliverable, disposable, or a role account ### Signup Form Validation A signup flow verifies each address as it is entered, rejecting disposable domains and catch-all traps before a record is created, so a list stays clean at the point of capture. The verdict distinguishes a safe address from a risky one using the syntax, DNS, and SMTP checks. Example prompt: Check the address from the signup form and reject it if it is disposable or fails the SMTP handshake ### List Hygiene Before a Send A messaging pipeline verifies each recipient individually before a campaign, filtering out spam traps and undeliverable addresses to protect sender reputation. Running the checks address by address keeps the send list current right before dispatch. Example prompt: Verify each recipient address and drop any that are flagged as spam traps or undeliverable ## Key resources - **Real-time verification** — Verify a single email address and read back a deliverability verdict with risk flags ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 50 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 81 / 100 - AI-Readiness & Agent Experience: 62 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/bulkemailchecker.com/bulkemailchecker/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Bulk Email Checker API by hand means passing your key as a query parameter, choosing between the GET and POST verification shapes, and parsing the verdict and risk flags yourself. Through Jentic you install once, import Bulk Email Checker from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The API has one real-time verification operation, so a rule can allow just that operation and leave nothing else exposed. The address and options travel as parameters, so your rule bounds the operation rather than which address is verified. - **Credential handling:** Your Bulk Email Checker key is stored once, encrypted, by your own Jentic One instance and injected 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 address' or 'check if an email is deliverable', and Jentic returns the matching Bulk Email Checker operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **NeverBounce API** — Real-time and batch email verification with deliverability scoring - **ZeroBounce API** — Email validation with spam trap and abuse detection - **Kickbox API** — Email verification with a Sendex quality score ## FAQ ### Is there a Bulk Email Checker MCP server? You don't need an MCP server to give your agent the Bulk Email Checker API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can verify addresses straight away, with no extra server to run and no tool definitions loaded into the agent's context. ### Can I limit what my agent is allowed to do with the Bulk Email Checker API? Yes. The API exposes a single real-time verification operation, so a rule can allow just that one operation and nothing else, and every call the agent makes is logged. The address to verify travels as a parameter, so your rule bounds the operation rather than which address is checked. ### What authentication does the Bulk Email Checker API use? The Bulk Email Checker API authenticates with an API key passed as a query parameter per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs. ### What checks does the Bulk Email Checker API run on an address? A verification runs more than seventeen factors, including RFC syntax validation, DNS and MX record lookups, disposable and role account detection, catch-all identification, spam trap screening, anti-greylisting, and a full SMTP handshake, and returns a single deliverability verdict an agent can act on. ### What are the rate limits for the Bulk Email Checker API? The OpenAPI spec does not specify rate limits for the Bulk Email Checker API. For current limits and throughput guidance, see the Bulk Email Checker documentation at https://bulkemailchecker.com. ### How do I verify an email address with the Bulk Email Checker API through Jentic? Import the Bulk Email Checker API from the Jentic API Directory, then have your agent issue a request such as 'verify this email address'. Jentic matches the intent to the verification operation and returns its input schema so the agent builds a valid request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.