domain_search
Everyone a company is known to have a work email for, from its domain, with roles, seniority and confidence. ₹2.77 per block of ten; a domain with nothing is ₹0.
What it does
Every person a company is known to have an email for, from domain (preferred) or company, in data.data.emails[]: value, first_name, last_name, position, seniority, department, confidence (0 to 100), sources[] and verification (status is null until an address has been checked), with the domain's email pattern and organization in data.data and the total in data.meta.results. Filter with department, seniority, job_titles, type (personal or generic) and decision_maker. It is a directory, not a verified list: a confidence under 50 is a pattern guess and generic rows (info@, sales@) bounce often, so run verify_email on anything you will send to. It does not find one named person (find_email).
India: Indian domains are covered unevenly; expect fewer rows than for a US company.
Inputs
Generated from the contract captured from staging on 2026-11-05. This tool declares one-of sets: domain or company must be present, or it is invalid_input for ₹0 before the source is called.
| Field | Type | Required | Description |
|---|---|---|---|
type | string | no | personal (named people) | generic (info@, contact@). e.g. "personal" |
limit | integer | no | emails to return, default 10, max 100. e.g. 10; max 10 |
domain | string | one of | the company's domain — preferred over company. e.g. "stripe.com" |
offset | integer | no | records to skip, for paging |
company | string | one of | company name, when you don't know the domain |
location | string | no | comma-separated locations to filter results by |
seniority | string | no | junior, senior, executive — comma-separate to combine |
department | string | no | executive, it, finance, management, sales, legal, support, hr, marketing, communication, education, design, health, operations |
job_titles | string | no | comma-separated job titles to match |
aggregations | boolean | no | return aggregate breakdowns (by department, seniority) alongside the results |
decision_maker | boolean | no | |
required_field | string | no | comma-separated fields a result must have, e.g. full_name,position |
verification_status | string | no | filter by deliverability status, e.g. valid |
One of these sets must be complete (anything else is invalid_input, ₹0): domain; company.
What drives the cost
limit, in blocks of ten: the source bills one credit per started ten emails returned, so limit 1 to 10 costs the same as 10 (take 10) and the hold always covers a full block. offset pages through more people; each page is a call. A domain with nothing is class: "ok_free", ₹0.
Price today
| Price today | ₹2.77 per 10 emails (cost_paise: 277) at ₹93.93 per US dollar on 17 November 2026 |
| Hold before the call | ₹4.16 (hold_paise: 416); 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 | 30 s, then upstream_timeout (₹0, retryable) |
| Over MCP | run_tool with tool: "domain_search" |
| Over REST | POST https://api.parel.si/v1/run with "tool": "domain_search" |
| Confirmation | not needed (the estimate is under the ₹200 threshold) |
| Count field | limit: The hold covers the number of results you ask for in limit (billed per started 10); leave it out and the worst case is held. |
Request
curl https://api.parel.si/v1/run \
-H "Authorization: Bearer $PAREL_KEY" \
-H "Content-Type: application/json" \
-d '{"tool":"domain_search","input":{"type":"personal","limit":10,"domain":"zomato.com"}}'
What comes back
data.data.emails[] and data.meta. A real answer recorded during the live check of 2026-10-28, with the people's names and addresses replaced and the list trimmed to two:
{
"data": {
"domain": "zomato.com",
"disposable": false,
"webmail": false,
"accept_all": true,
"pattern": "{first}.{last}",
"organization": "Zomato",
"linked_domains": [],
"emails": [
{
"value": "person1@zomato.com",
"type": "personal",
"source_type": "found",
"provenance": "found",
"confidence": 84,
"sources": [],
"first_name": "Person",
"last_name": "One",
"position": "CEO",
"position_raw": "CEO",
"seniority": "executive",
"department": "executive",
"decision_maker": true,
"linkedin": null,
"twitter": null,
"phone_number": null,
"verification": {
"date": "2026-10-28",
"status": "valid"
}
},
{
"value": "person2@zomato.com",
"type": "personal",
"source_type": "found",
"provenance": "found",
"confidence": 84,
"sources": [],
"first_name": "Person",
"last_name": "Two",
"position": "Chief Operating Officer",
"position_raw": "COO - Logistics",
"seniority": "executive",
"department": "operations",
"decision_maker": true,
"linkedin": null,
"twitter": null,
"phone_number": null,
"verification": {
"date": "2026-10-14",
"status": "valid"
}
},
"… 8 more item(s) truncated"
]
},
"meta": {
"results": 2523,
"results_approximate": false,
"limit": 10,
"offset": 0,
"params": {
"domain": "zomato.com",
"company": null,
"type": "personal",
"seniority": null,
"department": null,
"decision_maker": null
}
}
}
Notes
- limit drives the price in blocks of 10 (1 to 10 here); the hold always covers a full block.
- Rows are a directory listing: verify before mailing. Generic rows (info@, sales@) bounce often.
- offset pages through more people; each page is a call.
Siblings
verify_emailon every row before mailing.find_emailwhen you already know who you want.
This page as Markdown: /docs/tools/domain_search.md. Something wrong or missing: hello@parel.si.