Skip to Content
API & MCPPOSTFind a company's decision makers live

REST API

Find a company's decision makers live

For companies where search_people / get_contacts return nobody.

POST/v1/people/live
MCP tool find_people_livescope email:find2 records per company searched, found or not; a weekly ceiling per plan

Parameters

domainsstring[]required
Company websites/domains, e.g. [‘acme.com’]. (up to 10 items)
company_namesstring[]optional
Optional, same order as domains: the company’s name helps tell it apart from namesakes. (up to 10 items)
freshbooleanoptional
Ignore an answer already gathered in the last 30 days and search again (slower).
rolesstring[]optional
Keep only people whose title (or the answer’s section heading) contains one of these words, e.g. [‘ceo’,‘founder’,‘sales’,‘marketing’]. Case-insensitive. (up to 20 items)
only_source_confirmedbooleanoptional
Drop people whose name no cited page confirms (source_confirmed: false). Default false: they are shown, labelled.

What your agent reads

The tool description exactly as an MCP client receives it in tools/list — it doubles as the full behaviour of the endpoint.

For companies where search_people / get_contacts return nobody: searches the web NOW for the company's management, sales and department leaders and returns them with their titles. 1–10 domains per call. Takes ~15–60 s per company; whatever is not ready within ~50 s comes back status 'pending' — call get_live_people_result with the lookup_ids (every 15–30 s). For more companies use start_live_people_job. source_confirmed: true = the name appears in a page the answer cited (source_url); false = named by the AI answer only — AI answers can name people who do not exist, so treat those as leads to check (a mailbox found with find_email confirms them). No e-mail finding happens here: pick the people you want and send them to find_email (one) or start_email_job kind='find' (many: items=[{first_name, last_name, domain, ref}]), charged as those tools are. Beta: each company searched costs 2 records, found or not, and counts toward your plan's weekly live-search limit (see get_usage); re-reading results with get_live_people_result is free.

Errors follow one format.