Use case, Job search

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

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

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

The short answer

The short answer

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

Updated

  • Job title
  • Company and domain
  • Location
  • Posted date and link
  • Salary when the provider has it

The job

What the Job search API gives your agent

Job postings tell you what a company is about to build. A firm that hires five data engineers is not planning the same year as one that hires none. Your agent searches postings by title and place, or pulls the roles one company has open.

The providers here sit at different depths. The cheapest returns a thin index of title, company, location, date and link. The deeper ones add the description, the salary, the cities and when the posting closed. A job-board sweep needs the thin one. A market study needs the deep one.

You give

a job title and a location, or a company

data engineer in Berlin

You get

  • Job title
  • Company and domain
  • Location
  • Posted date and link
  • Salary when the provider has it

Providers, cheapest first

What actually differs between providers

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

  1. AnyAPI logoAnyAPI

    Returns a thin index of title, company, location, posted date and URL, with a flat price per request.

    anyapi-run-linkedin-jobs-thin
    $0.0005 / call
  2. PredictLeads logoPredictLeads

    Lists one company's job openings from its domain, with category, contract type and the dates a role was first and last seen.

    predictleads-companies-job-openings
    $0.0100 / call
  3. Sumble logoSumble

    Returns the fields you select from a jobs search, with filters, a limit and an offset.

    sumble-jobs
    $0.0200 / call
  4. TheirStack logoTheirStack

    Searches postings from company career sites and job boards, and returns the company domain, cities, salary and the date a posting closed.

    theirstack-jobs-search
    $0.0327 / result
  5. Any Site API

    Filters by keywords, location, company, industry, job type, work type and experience level.

    anysite-api-linkedin-search-jobs
    price on request

Cost

What 100 Job search runs cost

$0.0500

100 searches cost about $0.0500 through the cheapest endpoint, at AnyAPI, and about $3.27 through the dearest. Each run is one call.

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":"anyapi-run-linkedin-jobs-thin","input":{"query":"data engineer","location":"Berlin"},"wait":30}
ResponseSample output
// POST /v1/runs, then read run.status and run.result
// result: returns a thin index of title, company, location, posted date and URL, with a flat price per request

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 5 providers.
  • Runs on demand, whenever you ask.
Prompt: Job search API
Use looot to search job postings for data engineer in Berlin, return title, company, location, posted date and link, and flag any posting with a salary. 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 Job search API - https://looot.ai/use-cases/job-postings-api/skill.md

Before you start

Settle these before the first run

  • Decide whether you need the description. The thin index has none, and a second call per posting costs more than a deeper provider would have.
  • Set a result limit. Several of these providers bill per result, so an open query on a common title gets expensive fast.
  • Dates matter. Ask for a posting window, because a posting that closed last year says little about this quarter.

FAQ

Questions people ask

Yes. Give your agent a title and a place, and it runs a postings search across the providers on this page. Each row is one posting with the company, the location and the link. Narrow by company or by date to cut the noise.

Only from providers that hold it. One returns an average annual salary in US dollars when it has one, and the thin index has no salary field. Check the endpoint page of the provider you use.

Yes. PredictLeads lists one company's openings from its domain, with the dates each role was first and last seen. Other providers here filter a search by company. Your agent returns the roles it finds with the dates.

One provider returns the date a posting closed, so you can see which roles are gone. The thin index has no closing date.

Run the company openings call for each account and compare the roles with the last answer you stored. A company that opens new roles often needs the tools around them. Misses are common, so read an empty answer as unknown, not as not hiring.

Yes. Two endpoints here search LinkedIn job postings: a thin index with title, company, location, date and link, and a search with filters for company, industry, job type and experience level.

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.

More ways to run this job

For agents
use case
Job search API
run
search
schedule
on demand
step
Search job postings: anyapi anysite theirstack sumble predictleads
setup
https://looot.ai/use-cases/job-postings-api/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04

Try Job search with your own agent.

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