For Agents
Validate an email for deliverability and classify it by entity type. One GET endpoint, license-key auth.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Get Email Information 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 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.
What an agent can do with Interzoid Get Email Information API API.
Verify that an email address is syntactically valid and routable
Detect that the domain's mail servers are reachable before sending
Classify an email as generic, vulgar, education, government, or other entity type
Flag form submissions that supply throwaway or non-deliverable addresses
GET STARTED
Use for: Validate the email address user@example.com, Check whether an email is deliverable, Find out if a domain has working mail servers, Classify an email as generic or role-based
Not supported: Does not send verification emails, scrape email addresses from web pages, or check inbox contents — use for syntax, mail-server, and entity-type checks on a single email address only.
Jentic publishes the only available OpenAPI document for Interzoid Get Email Information API, keeping it validated and agent-ready.
The Interzoid Get Email Information API validates an email address for deliverability by checking syntax, verifying that the domain has reachable mail servers, and running additional liveness checks. The response also classifies the address against demographic categories such as generic, vulgar, education, government, or other entity types so downstream systems can suppress low-value or risky contacts. The single GET /getemailinfo endpoint authenticates with a license key passed as a query parameter and returns the validation result as JSON.
Suppress likely-bouncing addresses from a marketing send list before launch
Patterns agents use Interzoid Get Email Information API API for, with concrete tasks.
★ Signup form email validation
Web signup flows pass each submitted email through the Interzoid Get Email Information API and reject submissions whose domain has no reachable mail servers or whose syntax fails. This catches typos like 'gmial.com' before the user completes onboarding and reduces the welcome-email bounce rate.
On form submit, call /getemailinfo with email set to the submitted address and block submission if the response indicates the domain mail servers are unreachable.
Marketing list hygiene
Before a campaign launches, marketing operations runs every address on the send list through the Interzoid Get Email Information API and removes addresses flagged as undeliverable, generic, or vulgar. This protects sender reputation by reducing bounce and complaint rates on the upcoming send.
Iterate the campaign recipients table, call /getemailinfo for each address, and tag rows whose response indicates an undeliverable domain so they are excluded from the next send.
Lead-quality scoring
Inbound lead forms enrich each lead with the Interzoid email classification — distinguishing personal, generic, education, and government addresses. Lead scoring rules then weight personal-domain addresses higher than role-based ones such as info@ or support@ when prioritising sales follow-up.
On lead create, call /getemailinfo and add 10 points to the lead score if the classification is 'personal' and 0 points if 'generic'.
AI agent contact validation
An AI agent processing a contact import discovers the Interzoid Get Email Information API through Jentic and validates each email inline before writing rows into the CRM. Jentic stores the Interzoid license key in the credential vault and injects it as the license query parameter at execution time, so the agent never sees the raw key.
Search Jentic for 'validate an email address for deliverability', load the Interzoid Get Email Information operation, and execute it for each email in the import file.
1 endpoints — the interzoid get email information api validates an email address for deliverability by checking syntax, verifying that the domain has reachable mail servers, and running additional liveness checks.
METHOD
PATH
DESCRIPTION
/getemailinfo
Validate an email address and return deliverability and classification info
/getemailinfo
Validate an email address and return deliverability and classification info
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Interzoid license key is stored encrypted in the Jentic vault and injected as the license query parameter on each call to /getemailinfo, so the raw key never enters the agent's context.
Intent-based discovery
Agents search Jentic with intents like 'validate an email address'. Jentic returns the Interzoid Get Email Information operation with its parameter schema for direct execution.
Time to first call
Direct Interzoid integration: 1-2 hours including license registration and HTTP wiring. Through Jentic: a few minutes via search, load, and execute.
Alternatives and complements available in the Jentic catalogue.
Interzoid Get Address Match Similarity Key API
Generates similarity keys for street addresses, useful alongside email validation in full contact-record cleansing
Use alongside email validation when contact records also include physical addresses that need fuzzy matching.
Interzoid Get Full Name Match Similarity Key API
Fuzzy-match key for full names, useful alongside email validation when deduping contacts
Use when email validation alone is insufficient and you also need to dedup by person name.
Interzoid Get Global Phone Number Information API
Validates phone numbers, parallel to email validation for full contact-record verification
Use alongside email validation when phone numbers in the same record also need verification.
Specific to using Interzoid Get Email Information API API through Jentic.
What authentication does the Interzoid Get Email Information API use?
The API uses a license key passed as the license query parameter on every call to /getemailinfo. Through Jentic the license key is held in the credential vault and injected at execution time, so the agent never handles the raw key.
Can the Interzoid Get Email Information API tell me if an email is from a free or disposable provider?
The response classifies addresses across categories including generic, vulgar, education, government, and other entity types, which helps distinguish business addresses from generic or low-value ones. For finer-grained disposable-domain detection, combine the result with your own deny-list.
What are the rate limits for the Interzoid Get Email Information API?
The OpenAPI spec does not publish a numeric rate limit. Interzoid enforces per-license-tier quotas on the account dashboard, so check your account before running list-cleansing batches.
How do I validate an email through Jentic?
Install the SDK with pip install jentic, search for 'validate an email address for deliverability', load the Interzoid Get Email Information operation, and execute it with the email parameter set to the address you want to check.
Does the Interzoid Get Email Information API send a verification email to the address?
No. /getemailinfo performs syntax checks and verifies that the domain's mail servers are reachable but does not deliver a verification message. For double-opt-in flows you still need to send a confirmation email yourself.