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

# EmailKind API

The EmailKind API classifies an email address or domain by its provider and type, labeling it as business, personal, disposable, education, or role, using passive DNS analysis rather than sending any message. A single classify call handles one address or domain, and a batch call classifies up to 100 at once. Two public signup endpoints issue a free key programmatically so an agent can start without a dashboard.

## For AI agents

Classify an email address or domain by provider and type, business, personal, disposable, education, or role, via passive DNS, one at a time or in batches of up to 100.

## Scope

Does not send email, verify mailbox deliverability, or find addresses for a domain. Use for classifying email addresses and domains by provider and type only.

## Capabilities

- Classify a single email address or domain by provider and type
- Label an address as business, personal, disposable, education, or role
- Classify up to 100 emails or domains in one batch call
- Identify a disposable or role-based address before accepting a signup
- Issue a free API key programmatically through the signup endpoints

## Use cases

### Agent signup screening

An AI agent decides what to do with a new signup. Through Jentic the agent classifies the email at registration and reads back its provider and type, so it can wave through a business or personal address and hold a disposable or role account for review. No message is sent to the address during the check.

Example prompt: Classify a new signup's email and flag it when the type is disposable or role

### Batch list classification

A workflow cleans an existing list. The batch operation classifies up to 100 emails or domains in one call and returns each one's provider and type, so an agent can segment a list into business, personal, education, and role buckets, or drop disposable addresses, in a few requests. The analysis is passive DNS, so nothing is emailed.

Example prompt: Classify a batch of up to 100 addresses and group them by the returned type

### Role and disposable filtering

A signup flow keeps role and throwaway accounts out. The classify call identifies disposable providers and role addresses such as info or support, so an agent can apply a different rule to them, like requiring extra verification. Business and education addresses are labeled distinctly for onboarding logic.

Example prompt: Classify an address and require extra verification when it is labeled disposable or role

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/classify` | Classify one email address or domain |
| POST | `/classify/batch` | Classify up to 100 emails or domains |
| POST | `/signup` | Start a programmatic signup for a free key |
| POST | `/signup/confirm` | Exchange the confirmation code for a key |

## Key resources

- **Classify** — Classify a single email address or domain by provider and type
- **Batch** — Classify up to 100 emails or domains in one call
- **Signup** — Public endpoints to start a programmatic signup and confirm a free key

## 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:** 55 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 30 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 81 / 100
- **View full report:** https://jentic.com/apis/emailkind.com/emailkind/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 the EmailKind API by hand means handling its bearer key, minting one through the public signup endpoints first, and mapping its provider and type labels into your own signup logic. Through Jentic you install once, import EmailKind from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** EmailKind is a small API, so a rule bounds your agent to the classify operations it needs: classifying one address or a batch. The public signup operations that mint a key are not something the agent needs to call at run time.
- **Credential handling:** Your EmailKind 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 'classify an email address' or 'detect a disposable domain', and Jentic returns the matching EmailKind operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Emailable** — Verifies email deliverability and flags risky or disposable addresses
- **Kickbox** — Verifies email addresses and scores their quality
- **Hunter** — Finds and verifies professional email addresses for a domain

## FAQ

### What authentication does the EmailKind API use?

The EmailKind API authenticates the classify operations with a bearer API key per its OpenAPI spec, sent as `Authorization: Bearer sk_live_...`. The two signup endpoints are public so you can mint a free key programmatically. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

### Is there an EmailKind MCP server?

You don't need an MCP server to give your agent the EmailKind API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the classify and batch operations on demand without loading another server's tool definitions into its context.

### Can I detect disposable email addresses with the EmailKind API?

Yes. The classify operation labels an address or domain as business, personal, disposable, education, or role based on passive DNS analysis, and the batch operation applies the same labels to up to 100 inputs at once. No email is ever sent during the check.

### What are the rate limits for the EmailKind API?

The OpenAPI spec does not state specific rate limits. Check the provider's documentation at https://emailkind.com for the limits that apply to your key before classifying large lists.

### Can I limit what my agent is allowed to do with the EmailKind API?

Yes. Write a rule that allows your agent only the classify and batch operations, so it can label addresses but the key-minting signup operations stay out of its reach. Every call it makes is logged.

### How do I classify an email address with the EmailKind API through Jentic?

Search Jentic for 'classify an email address' and it returns the classify operation with its input schema; your agent passes an address or domain and reads back its provider and type. To run it on your own infrastructure, install Jentic One from its GitHub repo.