find_tools, describe_tool, execute_tool loop, with JSearch behind the
scenes.
What you can ask
- “Open this posting and give me every way to apply.”
- “What do employees say about this employer?”
- “What does a data engineer make in Seattle — hourly and yearly?”
- “Estimated pay for a senior software engineer at Google in New York with eight years of experience.”
- “Compare product manager salaries in London, Berlin and Amsterdam.”
- “Is this posting’s salary above the estimate for similar jobs nearby?”
What’s covered
Posting details- All details of one job posting, including application options and links
- Employer reviews
- Estimated salaries for similar jobs
- Estimated pay for a job title around a location
- Returned for several periods as the data allows — hourly, daily, weekly, monthly or yearly
- Estimated pay at a specific company by job title
- Optional location and experience level in years
How to use it
Pass the request in plain language and let the router pick the tool:describe_tool before executing — the details tool takes a job id from
a search result, and the two salary tools take different combinations of
title, location, company and experience.
Building with code? The same capability is available as fixed-contract
Scenario Methods with automatic provider
failover:
jobs.get for one posting by
the id returned from
jobs.search.FAQ
Where does the job id come from?
Where does the job id come from?
From a search result — see Job search.
Run the search first, then pass the id of the posting you want to open.
Are the salaries actual or estimated?
Are the salaries actual or estimated?
Estimated. Both salary tools return estimates for a title in a location or
at a company, and the periods returned (hourly through yearly) depend on
what data is available and relevant for that query.
Can I estimate pay by seniority?
Can I estimate pay by seniority?
Yes — the company salary tool accepts an experience level in years
alongside the title and an optional location.