AgentRouter
Sign in
AnyAPIAnyAPI

Company Search - Prospeo

/company_search.prospeo

Build an account list from Prospeo by industry, headcount, revenue, location, technology, funding and hiring activity. One flat price per page of 25.

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 /company_search.prospeo endpoint through AgentRouter.

Inputs

pageOptional
Page number, one-based. Prospeo returns 25 results per page and charges one flat price per page.
companyOptional
Filter by company names or websites, e.g. {"names": {"include": ["Stripe"]}, "websites": {"include": ["stripe.com"]}}.
companySicsOptional
Filter by SIC codes.
companyTypeOptional
Filter by ownership type.
companyNaicsOptional
Filter by NAICS codes.
companyFoundedOptional
Filter by founding year range.
companyFundingOptional
Filter by funding stage or amount raised.
companyRevenueOptional
Filter by revenue range.
companyIndustryOptional
Filter by company industry.
companyKeywordsOptional
Filter by keywords found in company data.
companyAttributesOptional
Filter by company characteristics, e.g. B2B, has pricing, has a free trial.
companyTechnologyOptional
Filter by technologies the company uses.
companyEmailProviderOptional
Filter by the company's email MX provider.
companyHeadcountRangeOptional
Filter by Prospeo's predefined employee count bands.
companyLocationSearchOptional
Filter by company headquarters location.
companyHeadcountCustomOptional
Filter by a custom employee count range.
companyHeadcountGrowthOptional
Filter by headcount growth.
companyJobPostingQuantityOptional
Filter by how many roles the company has open.
companyJobPostingHiringForOptional
Filter by the roles the company is currently hiring for.
companyHeadcountByDepartmentOptional
Filter by headcount within a department.
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 and experimental: its behavior may change. We recommend leaving it out and letting automatic routing choose: routing serves the cheapest source, uses cheaper sources as they are added, and fails over to another source when one fails, so your requests are not tied to the uptime of one source. To control cost, set a price ceiling instead: on requests paid from your AnyAPI wallet, the `max_cost_usd` REST query parameter or MCP `run_api` argument skips any source that would charge more, and refuses the request with no charge if none is left. Avoid pinning a single source, especially with `allowFallbacks` false: when that source has an outage your requests fail while others are served. If you send it, list source ids from this endpoint's `lanes[].source.id` in /catalog or /apis; they are tried first in the order given, then the others, unless `allowFallbacks` is false. You are charged for the source that serves, plus any source tried before it that charged for its attempt, and never more than the most this endpoint can cost with the sources 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. We recommend leaving it out. Setting it to false is experimental (its behavior may change) and ties the request to the sources listed in `source`: only they may serve, the request is refused with no charge if none of them can, and no other source rescues it when they fail. To control cost, set `max_cost_usd` instead: the REST query parameter or MCP `run_api` argument, on requests paid from your AnyAPI wallet. 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. You are charged for the source that serves, plus any source tried before it that charged for its attempt, and never more than the most this endpoint can cost with the remaining sources. 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

{
  "page": 1,
  "company": {
    "websites": {
      "include": [
        "stripe.com"
      ]
    }
  }
}

Output

AnyAPI output: found (boolean), data (the record) and reason when nothing was found.