canonical: https://jentic.com/apis/disify.com/disify

# Disify API

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.

## For AI agents

Detect disposable email addresses, validate email format, check a domain's MX records, and screen bulk email lists through Disify.

## Scope

Does not handle sending email, inbox hosting, or mailbox-ownership verification. Use for email and domain validation and disposable-address detection only.

## Capabilities

- 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

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

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

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

Example prompt: Submit a batch of domains to Disify and retrieve the validation results for the returned session

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| 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 |

## Key resources

- **Email** — Validate an email address by path or POST body and detect disposable providers
- **Domain** — Validate a domain's mail configuration and MX records
- **Bulk** — Retrieve bulk validation results by session

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/disify.com/disify/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **ZeroBounce** — ZeroBounce is a full email verification and scoring service, while Disify focuses on disposable detection and format and MX checks.
- **NeverBounce** — NeverBounce verifies and cleans email lists, overlapping with Disify's validation checks.
- **Kickbox** — Kickbox provides email verification with a deliverability grade, similar to Disify's checks.
- **AbstractAPI** — AbstractAPI offers a wider validation suite (phone, IP, address) that complements Disify's email focus.

## FAQ

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