find_email_backup
A second source for find_email: a person's work email from their name and company domain. ₹0.53 per email found; a result that finds nothing is ₹0.
What it does
A second source for find_email, from a different data provider: a person's work email from their name and company domain. The answer is this provider's own, so its field names differ from find_email's: read the example answer, not find_email's docs.
Use it when find_email fails or finds nothing; find_email stays the first choice. It searches its own data, so it can find what the first source missed. It is a separate call at its own price: you pay only when it finds something; a miss is free.
India: works for Indian companies and names; use the company's real domain (tcs.com, not tata.com).
Inputs
Generated from the contract captured from staging on 2026-11-18.
| Field | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Company domain or website URL. e.g. "example.com" |
company | string | no | Corrects a domain that doesn't receive mail |
full_name | string | no | Instead of first_name and last_name |
last_name | string | no | e.g. "Doe" |
first_name | string | no | e.g. "Jane" |
What drives the cost
Flat price per call. A result that finds nothing is class: "ok_free", ₹0. The timeout is 49 seconds.
Price today
| Price today | ₹0.53 per email found (cost_paise: 53) at ₹93.93 per US dollar on 17 November 2026 |
| Hold before the call | ₹0.80 (hold_paise: 80); 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 | 49 s, then upstream_timeout (₹0, retryable) |
| Over MCP | run_tool with tool: "find_email_backup" |
| Over REST | POST https://api.parel.si/v1/run with "tool": "find_email_backup" |
| Confirmation | not 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":"find_email_backup","input":{"domain":"zomato.com","full_name":"Deepinder Goyal"}}'
What comes back
data, as the live check of 2026-11-18 recorded it, trimmed:
{
"found_email": "jane@example.com",
"status": "found",
"confidence": 90,
"pattern_used": "first",
"domain": "cred.club",
"domain_intelligence": {
"mx_provider": "Google Workspace",
"catch_all": true,
"deliverability_index": "moderate",
"patterns": [
{
"pattern": "first"
},
{
"pattern": "first.last"
}
]
},
"diagnosis": "Email address verified",
"credits_list": 25
}
Notes
- Second source for find_email: call find_email first, this one after a failure or an empty answer.
- Field names differ from find_email's; inputs keep find_email's names where they mean the same thing.
Siblings
This page as Markdown: /docs/tools/find_email_backup.md. Something wrong or missing: hello@parel.si.