Openpath vs LinkedIn Jobs 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. Openpath is an open directory of real-world listings built for AI agents: each result is one listing, with the employer’s Apply link for a job or an Openpath inbox address for a business’s owner. It needs no key.
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.
- Openpath: Giving an agent a job to apply for or a local business to message, with no key.
LinkedIn Jobs and Openpath, side by side
| LinkedIn Jobs | Openpath | |
|---|---|---|
| Searches | Not a search API: it posts jobs into LinkedIn on behalf of customers. | Live jobs from employers’ own job boards (Austin, Texas, and remote) and local businesses in Austin |
| Returns | – | Plain Markdown, one listing per result: its facts, its source and the day it was checked. Typed JSON on request. |
| 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). | One empty request to /v1/connect, which returns a token. No account, email or card. |
| Free | – | Free: 600 searches a minute and 20,000 a day for each connected agent |
| Paid | – | Free for agents |
| Acting on a result | – | A job has the employer’s Apply link; a business, and every listing its owner added, has an Openpath inbox address. An agent writes to it and the owner answers there. Openpath doesn’t notify owners who haven’t joined yet, so a message to them waits 30 days. |
| 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. | Agents read listings and act on them; the terms say reading a listing doesn’t give the right to reuse it freely. |
| AI in its terms | – | Built for AI agents. An agent may act only with its owner’s permission, and the terms don’t let Openpath train AI models on what owners post. |
| Coverage | – | Jobs in Austin, Texas, and remote; businesses in Austin, for now |
| MCP server | – | https://api.openpath.sh/mcp/search, with no sign-in |
Try Openpath
Connect, then search:
curl https://api.openpath.sh/v1/connect \
-H 'Content-Type: application/json' \
--data-binary '{}'
curl -G https://api.openpath.sh/v1/search \
-H "Authorization: Bearer $OPENPATH_TOKEN" \
--data-urlencode "q=remote analytics engineer jobs over 130k"Or let the JavaScript client connect for you. The Python client, openpath-sh, works the same way.
npm install @openpath/sdk
import { search } from "@openpath/sdk";
console.log(await search("remote analytics engineer jobs over 130k"));Agent apps that take MCP servers can add https://api.openpath.sh/mcp/search, which needs no sign-in. The jobs docs have the full code, every parameter and each line of the answer.
One result, as it read on October 15, 2026:
## Analytics Engineer at Ontic
Pay: $135,000–$145,000 a year.
Full-time.
Remote.
Apply: https://jobs.ashbyhq.com/ontic/27d32707-54e2-47be-be62-376df6d2b0f3/application
Source: Ontic’s job board on Ashby, checked yesterday.
Link: https://api.openpath.sh/v1/listings/369348e4-b3d0-490f-82b4-a666041243cfWhat Openpath doesn’t do yet
- Jobs come from the job boards of a growing list of companies, in Austin and remote.
- Businesses are in Austin, Texas, for now.
- It shows no phone numbers or websites: owners are reached through their Openpath inbox.
Questions people ask
What do I need before I can use Openpath?
One empty request to /v1/connect, which returns a token. No account, email or card.
Is Openpath free?
Free: 600 searches a minute and 20,000 a day for each connected agent.
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”