verify_email_backup

A second source for verify_email: is this address deliverable? Checked live against the mailbox; catch-all and risky addresses flagged. Free per check; a result that finds nothing is ₹0.

What it does

A second source for verify_email, from a different data provider: is this address deliverable? Checked live against the mailbox; catch-all and risky addresses flagged. The answer is this provider's own, so its field names differ from verify_email's: read the example answer, not verify_email's docs.

Use it when verify_email fails; verify_email stays the first choice. It reads the same platform through another provider, so it helps when the first one is down or blocked, not when the platform has nothing. It is a separate call at its own price: it is free for you; listed free by the source today.

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

Inputs

Generated from the contract captured from staging on 2026-11-18.

FieldTypeRequiredDescription
emailstringyese.g. "name@example.com"

What drives the cost

Flat price per call. A result that finds nothing is class: "ok_free", ₹0. The timeout is 30 seconds.

Price today

Price todayFree per check (cost_paise: 0) 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 whenit fails, or the provider answers but there is nothing in it (an empty list, no email, no page): class: "ok_free", ₹0
Timeout30 s, then upstream_timeout (₹0, retryable)
Over MCPrun_tool with tool: "verify_email_backup"
Over RESTPOST https://api.parel.si/v1/run with "tool": "verify_email_backup"
Confirmationnot needed (the estimate is under the ₹200 threshold)

Request

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

What comes back

data, as the live check of 2026-11-18 recorded it, trimmed:

{
  "status_code": 200,
  "data": {
    "status": "accept_all"
  }
}

Notes

  • Second source for verify_email: call verify_email first, this one after a failure.
  • Field names differ from verify_email's; inputs keep verify_email's names where they mean the same thing.

Siblings

This page as Markdown: /docs/tools/verify_email_backup.md. Something wrong or missing: hello@parel.si.