Prospeo

Use Prospeo for work / professional email and phone finding and for people/company search across 200M+ contacts. Reach for it on BD / work-email flows.

Capabilities

Guidance

• Work email only: route candidate / personal-email flows to FullEnrich, LeadMagic, or Wiza. enrich_person also answers the linkedin_profile capability (dated job history, no contact detail), which is safe on candidate flows; skills[] comes back empty, so treat it as unknown rather than as a gap. Both capabilities are the same enrich_person call at the same 0.4 cr / result, so enriching one person for job history and then for a work email is two charges: keep the profile on the row and reuse it instead of re-running the capability.
• enrich_person needs a locator, and says so as a miss: give it a LinkedIn URL, an email, or a name plus a company name or domain. A name on its own matches nobody to search for, so the call returns a no-result (error_code: INVALID_DATAPOINTS) rather than a match, charges nothing, and a waterfall moves on to the next provider. A person the database simply doesn't hold comes back the same way as NO_MATCH.
• Flow: search_suggestions (free inside a people_search waterfall; 0.1 cr on a direct call) → search_person → enrich the returned person_ids (bulk ≤ 50).
• Choose one search contract: people_search accepts canonical fields (titles, locations, skills, limit) and handles provider selection, location resolution, paging, and dedup. A direct prospeo search_person call accepts Prospeo's native {"filters": {...}, "page": 1} body. Do not send job_title, location, skills, or limit as top-level fields to the direct method; skills has no Prospeo person-search equivalent.
• Search results never include email/mobile: enrich afterward.
• Location filters must use canonical strings from search_suggestions; arbitrary strings are rejected. For "within X km of a city," use the ZONE suggestion (one value covers the metro).
• No person-level skills / profile-keyword filter: person_search matches names/titles, not profiles. For "people with <skill> in their profile," use AI Ark; use Prospeo for title, seniority, department, location, and firmographic scoping (industry, headcount, founded year, technology).
• Enum values must match exactly: e.g. seniority is "C-Suite" (not "C-Level"). On an INVALID_FILTERS error, the response's provider_detail.filter_error names the rejected filter.
• Can't search with exclude-only: need ≥1 positive filter.
• Mobile enrichment (enrich_mobile:true) costs more (3.4 credits vs 0.4), gate it behind an explicit phone ask, don't default to it.
• Don't use Prospeo for job-change detection: schema drift; use FullEnrich.

hyreflow tools execute prospeo search_person \
  --payload '{"filters":{"person_job_title":{"include":["CTO"]}},"page":1}'

For a skill-constrained search, use the waterfall contract:

hyreflow tools execute people_search --payload \
  '{"titles":["Molding Manager"],"locations":["Wisconsin, United States"],"skills":["Liquid Silicone Rubber"],"limit":10}'