Use case, People search

People search API for your agent. One call per search.

Send a job title, a company and a location. Read name and job title back. Your agent picks the provider, and you pay per call.

Give this to your agent
set up looot for People search API - https://looot.ai/use-cases/people-search-api/skill.md

The short answer

The short answer

People search API for an agent: it sends a job title, a company and a location to a catalog endpoint and reads name, job title and company back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.

  • Name and job title
  • Company
  • Location
  • LinkedIn profile
  • Headline and seniority

The job

What the People search API gives your agent

You know the kind of person you want to reach, not their names. A people search turns filters such as a job title, a company, an industry and a place into a list of matching people. Each row is a person your agent can then enrich or email.

Two job ids cover it on looot: people.search for filter searches across providers, and people.database.search for the Icypeas people dataset. This page prices both. The providers differ in what they filter on: one searches LinkedIn members, one finds the person who holds a given role at a given company, and several return full profiles with company data.

You give

a job title, a company and a location

heads of data at fintech companies in London

You get

  • Name and job title
  • Company
  • Location
  • LinkedIn profile
  • Headline and seniority

Providers, cheapest first

What actually differs between providers

Today the price runs from $0.00036 to $0.0396 across 6 endpoints. The dearest costs about 110 times the cheapest. Price is only one difference. Each entry below says what that endpoint takes or returns that the others do not.

Sample calls

The request and what comes back

Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.

Request
{"endpointId":"anysite-api-linkedin-search-users","input":{"job_title":"Head of Data","location":"London","count":25},"wait":30}
ResponseSample output
// POST /v1/runs, then read run.status and run.result
// result: searches LinkedIn members by keywords, job title, current or past company, location, industry, school and name, billed per result

The prompt

Copy one prompt, give it to your agent.

Edit the names and numbers, paste it, and the agent runs the job and shows the cost.

  • One run is one search.
  • 1 step across 6 providers.
  • Runs on demand, whenever you ask.
Prompt: People search API
Use looot to find heads of data at fintech companies in London: name, job title, company and LinkedIn profile for the first 25 people, and show me the cost before you fetch a second page. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

Give this to your agent
Setup command
set up looot for People search API - https://looot.ai/use-cases/people-search-api/skill.md

Before you start

Settle these before the first run

  • Set a page size before the first run. Most providers here bill per person returned, and a broad title can match thousands of people.
  • Plan a second call for contact details. Two providers state that their results hold no email or phone, so the email finder or the mobile number finder runs per person afterwards.
  • Filters differ per provider. Anysite filters by LinkedIn company ids, not names, and LeadMagic needs a job title plus a company domain or name.
  • This is a search for people at work, not a consumer people finder. It does not search public records about private individuals.

FAQ

Questions people ask

It is an endpoint that takes filters such as a job title, a company and a location and returns the people who match. Your agent gets a list of names, titles and profiles to work through, and pays per search or per person found.

Yes. Every endpoint on this page takes a job title, and most add company, location and industry filters. LeadMagic answers the narrow case: the one person in a given role at a given company.

Yes. Run the search with your filters, keep the rows you want, then find and verify an email for each person. Your agent can show the cost of each step before it runs the next one.

Yes. The Anysite endpoint searches LinkedIn members by keywords, title, company, location, industry and school, and runs on looot's key, so you need no LinkedIn account of your own.

It finds people at work from public professional data. It is not a consumer people finder and does not search public records about private individuals. Coverage differs per provider, so a search one provider cannot match may work on another.

You pay per call, and the price depends on the provider your agent picks. This page reads the cheapest live price from the catalog and shows no number when the catalog is unreachable.

No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider.

No. One looot key reaches every provider in the catalog. You top up once, and each call is billed at the price shown before it runs.

Send a POST to /v1/runs with the endpoint id, the input and a new idempotency key, and your looot token in the Authorization header. With wait set to 30, the answer comes back in the response when the run ends within 30 seconds. Otherwise poll GET /v1/runs/<runId>.

That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results.

No. looot bills per call, and nothing runs while your agent is idle.
For agents
use case
People search API
run
search
schedule
on demand
step
Search for people: anysite icypeas ai-ark fullenrich prospeo leadmagic
setup
https://looot.ai/use-cases/people-search-api/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04
markdown /use-cases/people-search-api.md

Try People search with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.

Start your workspace See agent recipes