Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey, bearer5 EndpointsREST
For Agents
Detect disposable email addresses, validate email format, check a domain's MX records, and screen bulk email lists through Disify.
Use for: Check whether an email address is disposable, Validate an email address before creating an account, I need to verify a domain can receive mail, Look up the MX configuration for a domain
Not supported: Does not handle sending email, inbox hosting, or mailbox-ownership verification. Use for email and domain validation and disposable-address detection only.
The Disify API checks whether an email address is disposable, validates its format, and inspects a domain's MX records for deliverability signals. It validates a single email or domain by path or POST body, and returns bulk validation results by session so you can screen large lists. A successful check confirms format and mail configuration, not mailbox ownership or guaranteed delivery.
Install Jentic One Beta
Connect the Disify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Disify 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdisify.com%2Fdisify" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdisify.com%2Fdisify" | 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.
Capabilities
What an agent can do with Disify API.
Detect disposable or throwaway email addresses before accepting a signup
Validate an email address and read its MX-record deliverability signals
Validate a domain's mail configuration by domain name
Run bulk email and domain checks and retrieve results by session
Screen signup and marketing lists to drop disposable or malformed addresses
Use Cases
Patterns agents use Disify API for, with concrete tasks.
★ Agent Signup Screening
An AI agent handling signups checks each email through Disify before creating the account, rejecting disposable or malformed addresses. Disify exposes the email-validation operation the agent calls, and Jentic injects the credential at call time so the agent never holds the key.
Validate a new user's email with Disify and reject the signup if the address is disposable or malformed
List Hygiene Before Outreach
Marketing teams clean a list before sending by checking each address and its domain. The Disify API validates emails, flags disposable providers, and inspects domain MX records so undeliverable addresses are removed before a send.
Validate every address on a list with Disify and return only the deliverable, non-disposable addresses
Bulk Domain Validation
Teams onboarding many accounts validate domains in bulk and read the results by session. The Disify API accepts domain checks and returns bulk validation results keyed by session, so an agent can submit a batch and collect the outcome.
Submit a batch of domains to Disify and retrieve the validation results for the returned session
Key Endpoints
5 endpoints — the disify api checks whether an email address is disposable, validates its format, and inspects a domain's mx records for deliverability signals.
METHOD
PATH
DESCRIPTION
GET
/email/{email}
Validate an email address
POST
Validate an email address from a POST body
GET
/domain/{domain}
Validate a domain
POST
/domain
Validate a domain from a POST body
GET
/view/{session}
View bulk validation results
GET
/email/{email}
Validate an email address
POST/email
Validate an email address from a POST body
GET
/domain/{domain}
Validate a domain
POST
/domain
Validate a domain from a POST body
GET
/view/{session}
View bulk validation results
Jentic AI Readiness Score
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.
D
Disify API
- AI-Aware (B+)67/100
87
Foundational Compliance70
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability55
Security70
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
70
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
56%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
45%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
70
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
70%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Disify by hand means deciding when to send the `X-Api-Key` header or a bearer token and handling the anonymous-versus-keyed limit tiers yourself. Through Jentic you install once, import Disify from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Disify validates whatever email or domain you pass in, so there is no account resource to pin to. Limit the agent to the operations it needs, such as validating an email or checking a domain, so it cannot reach beyond validation.
Credential isolation
Your Disify credential 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.
Intent-based discovery
Agents search Jentic by intent such as 'check if an email is disposable' or 'validate a domain', and Jentic returns the matching Disify operation with its input schema so the agent calls the right endpoint directly.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Disify API through Jentic.
What authentication does the Disify API use?
Core checks work anonymously. For higher account limits the Disify API accepts either an API key in the `X-Api-Key` header or a bearer token, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.
Can I detect disposable email addresses with the Disify API?
Yes. The API flags whether an email uses a disposable or throwaway provider, validates the address format, and reports MX-record signals for the domain. You can check a single address or submit a batch and read the results by session.
Is there a Disify MCP server?
You don't need an MCP server to give your agent the Disify API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the email and domain validation operations. Operations load on demand, so your agent's context is not filled with another server's tool definitions.
Can I limit what my agent is allowed to do with the Disify API?
Yes. Write a rule that allows only the email-validation and domain-validation operations, so the agent can check addresses and domains and cannot retrieve bulk result sessions it did not create. Every call the agent makes is logged.
What are the rate limits for the Disify API?
Per-minute limits count HTTP requests and daily or monthly quotas count validation inputs, per the Disify spec, but it does not publish exact numbers. Check the Disify documentation at https://disify.com for current limits before running large batches.
How do I validate an email with the Disify API through Jentic?
Search Jentic for an intent like 'validate an email address', add the Disify API from the directory, and store your credential once if you need higher limits. Your agent then calls the validation operation and reads the disposable and MX signals. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED