canonical: https://jentic.com/apis/mailboxvalidator.com/mailboxvalidator-disposable

# MailboxValidator Disposable Email Checker

MailboxValidator Disposable Email Checker is a single-purpose endpoint that determines whether an email address belongs to a disposable provider such as 10minutemail.com, mailinator.com, or guerrillamail.com. The API returns a JSON or XML verdict for one email at a time and is typically wired into signup forms and trial-abuse pipelines. The OpenAPI spec exposes one operation: GET `/v1/email/disposable.`

## For AI agents

Detect disposable, throwaway, or temporary email addresses on a single GET - block trial abuse and signup spam at the form layer.

## Scope

Does not detect free-provider domains, verify SMTP existence, or send email - use for disposable-address detection only.

## Capabilities

- Classify an email address as disposable or persistent in one call
- Return JSON or XML output controlled by a format query parameter
- Detect short-lived inboxes from providers like 10minutemail and mailinator
- Operate on a credit-based usage model with an API key query parameter

## Use cases

### Trial Signup Abuse Prevention

Stop free-trial abuse by checking the signup email against the disposable provider list before provisioning a workspace. The Disposable Email Checker returns a single boolean-style verdict per address, which can be wired into a SaaS signup handler with sub-second latency. Blocking disposable addresses typically removes a meaningful percentage of trial signups that never convert.

Example prompt: Call GET `/v1/email/disposable`?email=trial@10minutemail.com&key={key} and if is_disposable is true, reject the signup with a corporate email prompt.

### Newsletter List Hygiene

Clean a newsletter list by removing disposable addresses that drag open rates and click-through rates down. The endpoint can be batched from a worker queue against existing subscribers and the verdict written back to the email service provider as a suppression flag. Running this monthly removes addresses that have already been abandoned by their owners.

Example prompt: For every Mailchimp subscriber created over 90 days ago with zero opens, call `/v1/email/disposable` and add an is_disposable=true tag for suppression.

### Agent-Driven Signup Validation

An AI agent that processes onboarding flows can call the Disposable Email Checker through Jentic before creating a user record. Combined with a free-provider check, the agent makes a high-confidence accept/review/reject decision at signup time without operator involvement.

Example prompt: Before creating a Stripe customer for a new trial signup, call `/v1/email/disposable`; if is_disposable is true, route the signup to manual review.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/email/disposable` | Check whether an email is from a disposable provider |

## Key resources

- **Disposable Email Check** — Single endpoint that returns a disposable verdict for one email address

## Why Jentic

- **Setup:** Wiring the MailboxValidator Disposable Email Checker by hand means attaching your API key to each request, targeting the api.mailboxvalidator.com host, and interpreting the disposable flag yourself. Through Jentic you install once, import the checker from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API offers a single disposable-address check with the address carried in the request, so limit the agent to the operation it needs, the disposable lookup, and nothing more. You decide which operations are in scope.
- **Credential handling:** Your MailboxValidator API 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 'is this a disposable email address', and Jentic returns the matching MailboxValidator operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **MailboxValidator Free Email Checker** — Companion endpoint that detects free webmail providers (gmail, yahoo, outlook).
- **MailboxValidator Email Validation** — Full single-email validation with MX, SMTP, syntax, and deliverability scoring.
- **Kickbox** — Email verification that returns a disposable flag alongside a deliverability verdict.

## FAQ

### What authentication does the Disposable Email Checker use?

The endpoint takes an API key passed as the key query parameter alongside the email being checked. The OpenAPI spec does not declare a securityScheme component; documentation lives at https://www.mailboxvalidator.com/api-email-disposable. Through Jentic the key is stored encrypted and injected at execution time.

### Can I check disposable status in JSON and XML?

Yes. GET `/v1/email/disposable` accepts a format query parameter that selects either JSON or XML output. JSON is the default and is recommended for SDK and agent consumers.

### What are the rate limits for the Disposable Email Checker?

MailboxValidator uses a credit-based usage model rather than per-second throttling. Each call against `/v1/email/disposable` consumes credits from your subscription, and the free tier provides a fixed monthly allowance. The spec does not encode an explicit per-second cap.

### How do I detect a disposable address through Jentic?

Search Jentic for "detect disposable email" to load the GET `/v1/email/disposable` operation, then execute with email and key parameters. The response is a JSON object whose is_disposable field is the verdict to act on.

### Is the Disposable Email Checker free?

MailboxValidator publishes a free tier with a monthly credit allowance for the disposable endpoint. Paid plans raise the credit cap and unlock parallel access to the free-provider checker and the full validation API.

### Can I limit what my agent is allowed to do with the MailboxValidator Disposable Email Checker?

Yes. This API exposes a single operation, GET `/v1/email/disposable`, and because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. You can scope the agent to the disposable-address lookup alone, so it can only submit an email and read back the is_disposable verdict. Your stored MailboxValidator key is injected at execution time and is never exposed to the agent, keeping the agent inside the exact boundary you set.