Indeed vs LinkedIn Jobs for AI agents
Indeed’s developer docs list no self-serve job search API: third parties get a JavaScript plugin for approved partners, and a beta MCP server that works only as a Claude connector. 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.
The short answer
- Indeed: Job seekers using Claude who want Indeed's own listings and their Indeed resume in one place; not an open data API for developers.
- LinkedIn Jobs: ATS vendors and job distributors that already partner with LinkedIn and need to publish jobs to it; not for finding jobs.
Side by side
| Indeed | LinkedIn Jobs | |
|---|---|---|
| Searches | Jobs from Indeed and Indeed PLUS job boards (aggregated), shown through Indeed's own plugin UI. | Not a search API: it posts jobs into LinkedIn on behalf of customers. |
| Returns | The plugin renders Indeed's own job search UI on your page (no raw data documented). The MCP Job Search tool returns titles, companies, locations, salaries and application URLs. | – |
| Before the first call | Indeed partner status and a partner app ID arranged through an Indeed representative (plugin); an Indeed account sign-in inside Claude (MCP). | LinkedIn approval, a signed API agreement with data restrictions, and Talent Solutions partner status; currently not accepting new partnerships (points to Apply Connect instead). |
| Acting on a result | MCP results include application URLs; the docs do not say whether they point to Indeed or to the employer. | – |
| Limits on keeping or showing results | Plugin rules: HTTPS pages only, explanatory headers, 16px margins, no leading users to click jobs for monetization; Indeed caps each publisher's click revenue. No caching or storage clause found. | 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. |
| AI in its terms | Indeed's Terms of Service define Agentic AI and prohibit bots automating Indeed Apply outside Indeed's official vendors; the MCP server is beta and subject to Indeed's Terms of Service. | – |
| MCP server | Official Indeed MCP server, beta, available only as a Claude connector: https://docs.indeed.com/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 Indeed and Openpath vs LinkedIn Jobs.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
Indeed, read on October 15, 2026:
- docs.indeed.com/publisher-js-plugin: “To use the plugin, you must be an Indeed partner.”
- docs.indeed.com/publisher-js-plugin: “Integrate Indeed features into your job board or publisher site by making only front-end changes.”
- docs.indeed.com/publisher-js-plugin: “Indeed assigns each publisher a cap on how much revenue they can receive from clicks on jobs”
- docs.indeed.com/mcp: “is available only for Claude Connector”
- docs.indeed.com/mcp: “titles, companies, locations, salaries, and application URLs”
- docs.indeed.com/mcp: “Sign in with your Indeed account for first-time use”
- docs.indeed.com/mcp: “offered in beta and subject to Indeed's Terms of Service”
- indeed.com/legal: “Use of any automation, scripting, or bots to automate the Indeed Apply process outside of Indeed's official vendors”
- indeed.com/legal: “Agentic AI: An algorithm which can perform tasks in accordance with a person's instructions.”
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”