AgentRouter
Sign in
AnyAPIAnyAPI

Search people by professional and company filters

/people_search.quickenrich

Find professionals by job title, employer, industry, headcount, revenue or location. Each profile indicates whether a work email or phone number is on file. Contact values are masked in this search.

Finished calls, last 7 days
0

Cancellations excluded. Execution times cover successful calls.

Use it with your agent

Set up https://www.agentrouter.to/SKILL.md, then use AnyAPI’s /people_search.quickenrich endpoint through AgentRouter.

Inputs

cityOptional
Filter on city name.
pageOptional
One-based result page.
limitOptional
Maximum people to return on this page.
titleOptional
Filter on job title.
countryOptional
Filter on ISO 3166-1 alpha-2 country code, e.g. "US".
revenueOptional
Filter on employer revenue band.
hasEmailOptional
Keep only people with a work email on file. The address itself is not returned here.
hasPhoneOptional
Keep only people with a phone on file. The number itself is not returned here.
industryOptional
Filter on the employer's LinkedIn industry label. Values must match the QuickEnrich industry vocabulary exactly, e.g. "IT Services and IT Consulting".
localityOptional
Filter on locality.
servicesOptional
Filter on the services the employer lists.
companyNameOptional
Filter on employer name.
linkedinBioOptional
Filter on words found in the employer's LinkedIn bio.
companyDomainOptional
Filter on employer website domain.
employeeCountOptional
Filter on employer headcount band. These bands differ from the companyEmployeeCount string returned on a result.
preferLatencyUnderMsOptional
Optional; omit it and routing is unchanged, with the cheapest source serving. Prefer sources whose typical response time (median over the trailing 30 days, as published on this endpoint's lane health) is under this many milliseconds; among those, the cheapest serves. This can raise your price: when the cheapest source misses the target, a faster and dearer one serves, and you are quoted and charged its price. If no source is that fast the request is still served, by whichever source offers the best speed for its price - it is never refused for being slow. Sources we have not timed are tried last. This is a preference, not a guarantee: the median describes past requests and is not a ceiling on this one, and it excludes any wait this request itself asks for. On a paginated walk it applies to the first page only: later pages stay with the source that page chose, at the price it was quoted.
sourceOptional
Optional. Source ids to prefer, in order, taken from this endpoint's `lanes[].source.id` in /catalog or /apis. Omit it and the cheapest source serves, with automatic failover. Listed sources are tried first in the order given, then the others, unless `allowFallbacks` is false. A single source with `allowFallbacks` false is served only by that source at its price, quoted and charged exactly, with no failover. The price is that of the dearest source that may serve. An id that does not serve this endpoint is rejected as invalid input with no charge; a listed source that is not serving right now is refused with no charge, so omit `source` to be served by another. On a paginated walk, later pages must include the source that served page one, or omit `source`.
allowFallbacksOptional
Optional, default true. When false, only the sources listed in `source` may serve; the request is refused with no charge if none of them can. When true, the listed sources are tried first and any other source may serve after them, at the normal price.
ignoreSourcesOptional
Optional. Source ids to skip for this request, taken from this endpoint's `lanes[].source.id`. The cheapest remaining source serves and the price is that of the dearest remaining source. An id that does not serve this endpoint, or that is also in `source`, is rejected as invalid input with no charge; skipping every source is rejected the same way.

Example input

{
  "limit": 2,
  "title": {
    "include": [
      "CEO"
    ]
  },
  "country": {
    "include": [
      "US"
    ]
  },
  "hasEmail": true
}

Output

AnyAPI output: found (boolean), data.people (matching rows) and reason when nothing was found.