# Job postings API for your agent Job postings 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. ## What this does 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. Example: data engineer in Berlin. ## What differs between providers - AnyAPI (anyapi-run-linkedin-jobs-thin): returns a thin index of title, company, location, posted date and URL, with a flat price per request. - Any Site API (anysite-api-linkedin-search-jobs): filters by keywords, location, company, industry, job type, work type and experience level. - TheirStack (theirstack-jobs-search): searches postings from company career sites and job boards, and returns the company domain, cities, salary and the date a posting closed. - Sumble (sumble-jobs): returns the fields you select from a jobs search, with filters, a limit and an offset. ## Before you start - 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. ## Prompt 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. ## Steps and providers - Search job postings: anyapi, anysite, theirstack, sumble. 1 call per search. ## What comes back - Job title - Company and domain - Location - Posted date and link - Salary when the provider has it ## 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. - AnyAPI: {"endpointId":"anyapi-run-linkedin-jobs-thin","input":{"query":"data engineer","location":"Berlin"},"wait":30} - Any Site API: {"endpointId":"anysite-api-linkedin-search-jobs","input":{"keywords":"data engineer","location":"Berlin","count":20},"wait":30} ## How do I search job postings across companies? 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. ## Can I get the salary of a posting? 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. ## Can I see every job a single company has open? Yes. Filter by company on a provider that supports it, or search by the company's domain. Your agent returns the roles it finds with the dates. ## Does it include closed postings? One provider returns the date a posting closed, so you can see which roles are gone. The thin index has no closing date. ## Can I use postings as a buying signal? Yes. A company that hires for a role often needs the tools around it. Your agent can run the search per account and flag the firms that open new roles. ## How much does one search cost? 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. ## Do I pay when a job postings call fails? No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider. ## Do I need an account with each job postings 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. ## How do I call job postings from code? 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/. ## Can I run job postings on a schedule? That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results. ## Do I pay while my agent is idle? No. looot bills per call, and nothing runs while your agent is idle. ## Related pages - /use-cases/company-list-builder - /use-cases/linkedin-post-search-api - /use-cases/enrich-a-company ## Last reviewed 2026-10-04. The cost per 1,000 search runs is read live from the catalog on the web page.