Use case, Job postings

Job postings 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 - https://looot.ai/skill.md

The job

What the Job postings 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 four 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

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 steps across 4 providers.
  • Runs on demand, whenever you ask.
Prompt: Job postings 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 - https://looot.ai/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

Give your agent a title and a place. It runs a postings search and returns one row per posting with the company, the location and the link. Narrow by company or by date to cut the noise.

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

Try Job postings with your own agent.

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