> Parel documentation. Index of every page: https://parel.si/docs/llms.txt. This page in HTML: https://parel.si/docs/tools/verify_email

# verify_email

> Whether an email address is deliverable, checked live against the mailbox: valid, valid-risky, catch-all, invalid or unknown, with the reason. ₹0.25 per check.

## What it does

For one address: `validity` (`valid`, `valid-risky`, `catch-all`, `invalid` or `unknown`), `validIdentity` and `validSMTP`, the `mxDomain` that answered, and a `reason` with a `reasonCode` when the check failed, in `data`. Use it on every address before outreach, including the ones [`find_email`](https://parel.si/docs/tools/find_email.md) and [`domain_search`](https://parel.si/docs/tools/domain_search.md) returned. It does not find addresses and cannot prove a mailbox is read. `valid-risky` means the mailbox answered but the domain accepts risky mail; `catch-all` means the domain accepts anything, so the address could not be proven, not that it is good. `treatAliasesAsValid` accepts alias addresses as valid.

India: works for any domain, including `.in` domains and Indian webmail.

## Inputs

Generated from the contract captured on 2026-11-05.

| Field | Type | Required | Description |
|---|---|---|---|
| `email` | string | yes | e.g. "name@example.com" |
| `treatAliasesAsValid` | boolean | no |  |

## What drives the cost

Nothing: a flat price per completed check, whatever the verdict (catch-all and unknown included). A check the source could not complete is `class: "ok_free"`, ₹0. Usually one to three seconds; a few domains take ten.

## Price today

| | |
|---|---|
| Price today | **₹0.25** per check (`cost_paise: 25`) at ₹93.93 per US dollar on 17 November 2026 |
| Hold before the call | ₹0.38 (`hold_paise: 38`); when the call settles the real price is charged and the unused part is released |
| ₹0 when | it fails, or the provider answers but there is nothing in it (an empty list, no email, no page): `class: "ok_free"`, ₹0 |
| Timeout | 39 s, then `upstream_timeout` (₹0, retryable) |
| Over MCP | `run_tool` with `tool: "verify_email"` |
| Over REST | `POST https://api.parel.si/v1/run` with `"tool": "verify_email"` |
| Confirmation | not needed (the estimate is under the ₹200 threshold) |

## Request

```bash
curl https://api.parel.si/v1/run \
  -H "Authorization: Bearer $PAREL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tool":"verify_email","input":{"email":"jane@example.com"}}'
```

## What comes back

`data` with the verdict. A real answer recorded during the live check of 2026-10-28, with the address replaced:

```json
{
  "jobId": "01M6143S439W5VR662362NGDFR",
  "email": "name@zomato.com",
  "validity": "valid-risky",
  "validIdentity": true,
  "validSMTP": null,
  "displayText": "valid-risky",
  "mxDomain": "alt1.aspmx.l.google.com",
  "reason": null,
  "reasonCode": null
}
```

## Notes

- validity: valid, valid-risky, catch-all, invalid or unknown. catch-all means the domain could not be checked, not that the address is good.
- Usually one to three seconds; a few domains take ten.
- A check that could not complete is free; a completed check is charged whatever the verdict.

## Siblings

- [`find_email`](https://parel.si/docs/tools/find_email.md) to get the address in the first place.
- [`domain_search`](https://parel.si/docs/tools/domain_search.md) for everyone known at a domain.
