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

# MailboxValidator Free Email Checker

MailboxValidator Free Email Checker is a single-purpose endpoint that determines whether an email address comes from a free email provider (gmail.com, yahoo.com, outlook.com and similar). The API returns a JSON or XML response indicating the free-provider verdict for one email at a time and is typically used as a lead-quality signal in CRM pipelines. The OpenAPI spec exposes one operation: GET `/v1/email/free.`

## For AI agents

Check whether a single email address belongs to a free webmail provider - useful for filtering personal addresses out of B2B lead routing.

## Scope

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

## Capabilities

- Classify an email address as free-provider or business via a single GET
- Return JSON or XML output controlled by a format query parameter
- Distinguish gmail, yahoo, hotmail, outlook and similar consumer domains
- Support a credit-based usage model with a per-key API key parameter

## Use cases

### B2B Lead Quality Filter

Filter out free webmail addresses from inbound lead forms so sales reps focus on prospects with corporate domains. The Free Email Checker returns a simple boolean-style verdict per address, which can be wired into a Marketo or HubSpot workflow as a routing condition. A typical setup adds the free-provider flag to the lead record at create time.

Example prompt: For each new HubSpot contact, call GET `/v1/email/free`?email={email}&key={key} and write the is_free boolean to a custom property.

### Trial Abuse Reduction

Reduce trial abuse by flagging or limiting accounts created with free webmail providers. Combined with a disposable-email check, the free-provider flag is a strong signal that a signup will not convert to a paid customer. This is a single GET per signup and adds negligible latency.

Example prompt: Call `/v1/email/free` for trial@gmail.com and if is_free is true, gate the trial behind manual review.

### Agent-Driven Lead Scoring

An AI agent that scores incoming leads can call the Free Email Checker through Jentic to add an is_free signal to its scoring vector. Combined with company enrichment, the agent can autonomously route corporate leads to AEs and free-mail leads to a self-serve nurture track without human intervention.

Example prompt: Run `/v1/email/free` on a batch of 200 lead emails and tag each lead in Salesforce with a free_email custom field for routing rules.

## Key endpoints

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

## Key resources

- **Free Email Check** — Single endpoint that returns a free-provider verdict for one email address

## Why Jentic

- **Setup:** Wiring the MailboxValidator Free Email Checker by hand means attaching your API key to each request, targeting the api.mailboxvalidator.com host, and reading the free-provider result 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 free-provider check with the address carried in the request, so limit the agent to the operation it needs, the free-email lookup, and nothing more. The operation set is your choice.
- **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 free email provider', 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 Disposable Email Checker** — Companion endpoint that detects disposable email providers from the same vendor.
- **MailboxValidator Email Validation** — Full single-email validation with MX, SMTP, syntax, and deliverability scoring.
- **mailboxlayer** — Real-time email validation with a free_provider flag plus deliverability score.

## FAQ

### What authentication does the Free 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; the key is documented at https://www.mailboxvalidator.com/api-email-freem. Through Jentic the key is stored encrypted and injected at execution time.

### Can I get JSON or XML back from this endpoint?

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

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

MailboxValidator uses a credit model rather than a fixed per-second rate limit. Each call against `/v1/email/free` consumes credits from your subscription, and the free tier provides a fixed monthly allowance. The OpenAPI spec does not encode a per-second throttle.

### How do I check whether an email is free through Jentic?

Search Jentic for "check free email provider" to load the GET `/v1/email/free` operation, then execute with email and key parameters. The response is a JSON object whose is_free field is the verdict you want.

### Is the Free Email Checker available on a free plan?

Yes. MailboxValidator publishes a free tier with a monthly credit allowance for the Free Email Checker. Paid tiers raise the credit cap and unlock other MailboxValidator products such as the disposable checker and full single-validation API.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API exposes only the single free-provider lookup, GET `/v1/email/free`, so you can grant the agent that one operation and nothing else. Your MailboxValidator API key stays with your instance and is injected at execution time, so the agent can run the free-email check without ever seeing the key.