LinkedIn Jobs vs JSearch for AI agents
LinkedIn documents no public job search API; its jobs API is for approved partners (ATS systems, job distributors) to post jobs to LinkedIn, and it is closed to new partners. JSearch is a commercial job search API that returns live job postings and salary estimates gathered from Google for Jobs.
The short answer
- LinkedIn Jobs: ATS vendors and job distributors that already partner with LinkedIn and need to publish jobs to it; not for finding jobs.
- JSearch: Broad, Google-for-Jobs-style job search across many boards from one API.
Side by side
| LinkedIn Jobs | JSearch | |
|---|---|---|
| Searches | Not a search API: it posts jobs into LinkedIn on behalf of customers. | Aggregated postings via Google for Jobs, covering LinkedIn, Indeed, Glassdoor, ZipRecruiter and other public job sites. |
| Returns | – | JSON jobs with job_id, job title, employer_name, job_publisher, job_city, job_country, job_min_salary, job_apply_link and apply_options; endpoints search-v2, job-details, company-job-salary, estimated-salary. |
| Before the first call | LinkedIn approval, a signed API agreement with data restrictions, and Talent Solutions partner status; currently not accepting new partnerships (points to Apply Connect instead). | An account and API key from the OpenWeb Ninja developer portal (also sold on RapidAPI). |
| Acting on a result | – | job_apply_link is the primary apply link; apply_options lists links from other publishers, each flagged is_direct. |
| Limits on keeping or showing results | LinkedIn API Terms forbid caching or storing Content except as needed to run your application, and bar content obtained by scraping or crawling outside the APIs. | Not stated on its pages |
| MCP server | – | Official OpenWeb Ninja MCP server (npm @openwebninja/mcp-server) includes a jsearch tool: https://github.com/OpenWeb-Ninja/openwebninja-mcp |
Where Openpath fits
If the agent needs a job to apply for in Austin, Texas, or a remote one, Openpath returns the listings themselves, free and with no key. See Openpath vs LinkedIn Jobs and Openpath vs JSearch.
Questions people ask
What do I need before I can use JSearch?
An account and API key from the OpenWeb Ninja developer portal (also sold on RapidAPI).
Is JSearch free?
Its pages listed no free use when we read them on October 15, 2026.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
LinkedIn Jobs, read on October 15, 2026:
- learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview: “We are currently not accepting new partnerships for LinkedIn's Job Posting API.”
- learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview: “enables authorized third parties such as clients, ATS systems, and job distributors to post jobs directly to LinkedIn”
- learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview: “The use of these APIs is restricted to those developers approved by LinkedIn.”
- linkedin.com/legal/l/api-terms-of-use: “You must not capture, copy, cache, or store any Content”
- linkedin.com/legal/l/api-terms-of-use: “scraping, crawling, spidering or using any other technology or software to access LinkedIn content outside the APIs”
JSearch, read on October 15, 2026:
- agents.openwebninja.com/manifest.json: “Returns live job postings from Google for Jobs covering LinkedIn, Indeed, Glassdoor, ZipRecruiter and other public job sites”
- agents.openwebninja.com/zcj/v8c3szxamb6i/services/jsearch/openapi.json: “The primary link to apply for the job.”
- agents.openwebninja.com/zcj/v8c3szxamb6i/services/jsearch/openapi.json: “Alternative apply links from other publishers.”
- openwebninja.com/documentation: “Sign up, manage subscriptions, and access API keys”
- github.com/OpenWeb-Ninja/openwebninja-mcp: “Official Model Context Protocol server for OpenWeb Ninja APIs”