Job Opportunities API (JOA) serves job postings taken from employers' own career sites and applicant-tracking systems, not scraped from job boards. Every field on every row says whether the employer published it or we inferred it, so you decide per field what to build on. Roles that disappear are not deleted: their closure history stays, which makes hiring-trend and time-to-fill analysis possible. Free keyless statistics and a browser playground let you check coverage before signing up, and a remote MCP server lets AI agents search postings directly. Live coverage: https://jobopportunitiesapi.org/facts

Hi, I'm Luca, the maker. JOA started from frustration with job data you have to take on trust. Every field says whether the employer published it or we inferred it, closed roles keep their history, and the coverage page lists what we do NOT have. You can try the key-free statistics in the playground before signing up, and AI agents can use the MCP server directly. I'd love feedback from anyone building job boards, market-intelligence tools or agents that need live hiring data: what is missing?

Per-field provenance is the right call. For salary specifically, do you record whether the range was published under a pay-transparency rule (some US states and EU countries now require it) versus volunteered? Anyone comparing ranges across regions would want to know which postings were legally obliged to show one.
This is a really valuable approach to job market data! I especially like the transparency around employer-published versus inferred information and the ability to track job closures over time. The API access and MCP integration also make it useful for developers and AI-powered applications. Great work!

Hi, I'm Luca, the maker. JOA started from frustration with job data you have to take on trust. Every field says whether the employer published it or we inferred it, closed roles keep their history, and the coverage page lists what we do NOT have. You can try the key-free statistics in the playground before signing up, and AI agents can use the MCP server directly. I'd love feedback from anyone building job boards, market-intelligence tools or agents that need live hiring data: what is missing?

Per-field provenance is the right call. For salary specifically, do you record whether the range was published under a pay-transparency rule (some US states and EU countries now require it) versus volunteered? Anyone comparing ranges across regions would want to know which postings were legally obliged to show one.
This is a really valuable approach to job market data! I especially like the transparency around employer-published versus inferred information and the ability to track job closures over time. The API access and MCP integration also make it useful for developers and AI-powered applications. Great work!
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved