Salary and jobs APIs you can pay per call

What a salary and jobs API does, and who calls it

Two kinds of product answer a request about pay and work. A salary route returns pay figures for a job title, sometimes for a location or a single employer: a range, a median or an estimate, depending on the provider. A job-postings route returns open positions: title, employer, location, a link to apply and, where the employer published it, the advertised pay. Postings show what employers offer today for specific openings; salary figures summarize what a role pays, from whatever source the provider uses.

An agent calls a salary route to benchmark an offer, price a role before hiring or check whether a candidate's expectation is in range. It calls a postings route to find openings for a candidate, follow a competitor's hiring or measure demand for a skill in a city. The two answers are easy to confuse: an advertised pay range in a posting is the employer's statement for one opening, not a market benchmark.

The table covers 5 services with a matching priced salary or job endpoint as of October 26, 2026: 1 service lists a salary route for a job title, 3 services search job postings by keyword and location and 1 service reads the open roles of one employer. Services that pass the listing checks but list no matching priced endpoint are left out (0 candidates as of October 26, 2026).

What the 5 salary and jobs services actually return

The classification follows each endpoint's documented product. A service with more than one product appears in more than one row, and each quote comes from the cheapest priced endpoint of that type, with its route attached.

Each price is the cheapest endpoint of that service for that kind of data: the same number wherever this page quotes it.

A salary figure and an advertised pay range answer different questions, so they are separate types even when a posting carries a salary field. A route documented only by its path is classified from the path and the service description together, and its service note says so. A LinkedIn tool with a job-listing mode is listed as its own type: its quote cannot be tied to that mode, so it never sets a service's price in the main table. Source and coverage notes report what a description states, such as LinkedIn, named job boards or applicant-tracking systems. They are provider statements, not audits by x402-list.

The 5 salary and jobs APIs and their matching endpoint prices

One row per service, ordered by measured buyers. The price is the cheapest salary, job-search or employer-roles endpoint of the service, named under the price, never an unrelated tool on the same host.

$/CALL is the price of the endpoint named under it: the cheapest salary figures for a job title (route named by its path), salary figures for a job title at one employer (route named by its path), job postings searched by keyword and location, open roles of one employer, from its applicant-tracking system and roles matched to a candidate profile, with a tailored cv and cover letter (route named by its path) endpoint of the service or, for a service without one, its cheapest salary or job endpoint. Never the cheapest tool of a gateway. Other kinds of data have their own price in the tables below. SALARY OR JOB ENDPOINTS counts the salary or job endpoints out of all the endpoints the service lists. BUYERS 30D counts distinct wallets that paid the whole service on-chain in 30 days, not only its salary or job endpoints. "Generalist" marks a gateway that sells more than three unrelated kinds of tools: it is never called the cheapest.

The buyer figure counts wallets that paid the whole service, so for a gateway it does not show demand for salary or job data. Where a provider states a price per record, the cost of a search depends on how many results it returns, and the captured quote is only the starting point.

How to choose a salary or jobs API

Salary figures or job postings

Decide which question you are answering. To price a role or check an offer, you need salary figures with a stated method, period and currency. To find openings or follow hiring, you need postings with apply links and dates. Advertised pay in postings can supplement a benchmark, but only if you know how many postings carried a figure and from which boards they came. Do not compare these prices as if they bought the same answer.

Where the data comes from

As of October 26, 2026, 2 services name LinkedIn as a source of job listings: Linked Panda and Hirescrape.

1 service names several job boards for one call, and 1 service reads employer applicant-tracking systems. A posting read from an employer's own system is closer to the source than a copy on a job board, while a board covers many employers at once. Ask how the provider collects postings and whether its terms allow your use, especially if you republish them.

Salary inside postings

As of October 26, 2026, 1 service lists salary as a returned field of each posting. Employers publish pay for some openings and not for others, and pay-transparency rules in some jurisdictions require a range in the posting. An advertised range is a statement for one opening: it can be wide, it can exclude bonuses and equity, and it says nothing about what the person hired was finally paid.

Per call, per page or per record

Read what one call buys before you compare prices: every match for a query, one page of results, or a price per record returned. A route that sells one page needs several calls to cover a broad search, and a per-record price grows with the size of the result. Check how the provider caps or paginates results and what an empty result costs.

Freshness and duplicates

A posting can close the day after you read it, and the same opening often appears on several boards with different wording. Store the posting date and the apply link, deduplicate on employer, title and location, and re-check an opening before you send a candidate to it. Salary figures change more slowly; record the date of each answer and refresh it on a schedule you can defend.

Personal data

Job data can carry personal data: recruiter names, hiring managers or the profiles around a posting. Collect only the fields you need, and handle the rest under your own data-protection rules and the terms of the provider and the source.

Which endpoint fits which job

Start with the job, then compare the candidates whose classified endpoints match it. The price in a job list is tied to those types and can differ from the service's price in the main table.

Benchmark pay for a role

Send the exact job title and location you are pricing, and check that the response states the currency, the period, whether the figure is base or total pay, and how many data points stand behind it. Keep the date of the answer with any offer or report built on it.

Candidates today, most buyers first: OpenWeb Ninja ($0.003/call, 42 buyers)

Find open jobs for a keyword and a place

Compare the boards each route reads, how many results one call returns and whether the price is per call, per page or per record. Store the apply link and the posting date, deduplicate across boards and re-check a posting before acting on it.

Candidates today, most buyers first: Linked Panda ($0.05/call, 34 buyers) · Hirescrape ($0.21/call, 15 buyers) · freeq x402 Gateway ($0.002/call, generalist, 13 buyers)

Watch one employer's hiring

A route that reads an employer's applicant-tracking system returns that company's own openings, with fields such as department and posted date where the route documents them. Confirm which systems it supports, and compare snapshots over time to see roles opened and closed.

Candidates today, most buyers first: Zinin M2M Hub ($0.02/call, generalist, 3 buyers)

Service details and limits to check

The notes below are read from each provider's description and endpoint list captured on October 22, 2026. They attribute advertised capabilities; x402-list has not checked the returned figures or postings against their sources. Prices, uptime and buyers come from the current page model.

OpenWeb Ninja

OpenWeb Ninja lists GET /job-salary-data/job-salary at $0.003 and GET /job-salary-data/company-job-salary at $0.003. Judging by the paths, the first returns salary figures for a job title and the second for a title at one employer. The endpoint list gives both paths without a description, and the service description names job salary data among product, local business, review and search tools. The listing therefore does not state the inputs, the currency or period of the figures, or where they come from. Request a sample for a role and place you already know, and check whether the response separates base pay from total pay and says how many data points stand behind a figure, before you quote it to anyone.

2 salary or job endpoints of 22 · $0.003/call (GET /job-salary-data/job-salary) · ARB/Base/POL · uptime 30d 100% · 229 ms · 42 buyers in 30 days

freeq x402 Gateway

freeq x402 Gateway lists POST /tools/jobs at $0.002. The description says it searches live job postings by keywords and locations and returns title, company, location, apply link, work types, employment type, seniority, industry, salary and description, with onsite, remote or hybrid preferences. It also claims that one call covers the whole market for a keyword and location pair; that is the provider's statement, and the description does not name the boards or sites it reads. A salary field in a posting holds the pay the employer chose to publish and can be missing where it published none, so do not average it into a benchmark without saying so. The host is a generalist gateway with token prices, wallet tools and rendering utilities.

1 salary or job endpoint of 16 · $0.002/call (POST /tools/jobs) · Base · uptime 30d 99.9% · 221 ms · 13 buyers in 30 days

Zinin M2M Hub

Zinin M2M Hub lists POST /api/job-postings-aggregator at $0.02. For one company, it pulls every open role from the public applicant-tracking system, naming Greenhouse, Lever and Ashby, and normalizes the result into one row per posting with title, location, department, URL and posted date. That suits watching a known employer's hiring; it does not search the market by keyword, so check that the employer you follow uses one of the systems it names. The service description also mentions real-estate and job listings across 15 countries, while the endpoint list read for this page shows this company route for jobs. Zinin is a generalist gateway with company, sanctions, filing and crypto tools.

1 salary or job endpoint of 12 · $0.02/call (POST /api/job-postings-aggregator) · Base · uptime 30d 100% · 178 ms · 3 buyers in 30 days

Hirescrape

Hirescrape lists POST /api/tools/jobs at $0.21, described as scraping jobs from LinkedIn, Indeed, Glassdoor, Google Jobs, ZipRecruiter, Bayt, BDJobs and Naukri in one call. The service description says the price per record is declared in the 402 response, so read the payment requirement for your exact request to see whether the captured amount covers a call or a record before you budget a search. The same host lists a LinkedIn tool, at $0.00225, whose modes include job listings beside people, companies and posts; that quote cannot be tied to the job mode, so it is listed as a separate type and does not set the price in the table. Results gathered from several boards can repeat the same opening; deduplicate on employer, title and location.

2 salary or job endpoints of 5 · $0.21/call (POST /api/tools/jobs) · Base · uptime 30d 100% · 162 ms · 15 buyers in 30 days

Linked Panda

Linked Panda lists POST /agent/v1/jobs/search at $0.05, described as a LinkedIn job search results page, so one call buys one page of results rather than every match. The same host lists a GeoID lookup for LinkedIn location identifiers; it helps build a search but returns no job data, so it is not part of this comparison. The service describes itself as a read-only API over LinkedIn data, with profile and company enrichment, work email lookup and ad search, paid per single request. Postings and the profiles around them can carry personal data such as recruiter names; handle that under your own data-protection rules.

1 salary or job endpoint of 10 · $0.05/call (POST /agent/v1/jobs/search) · Base · uptime 30d 100% · 152 ms · 34 buyers in 30 days

What the calls cost at different volumes

The median selected endpoint costs $0.02 per call. At that same request shape, 100,000 calls would cost $2,000.00. This is a comparison aid, not an invoice: a search that pages through results is several calls, and a per-record price grows with the number of results.

Each service at the price of its main salary or job endpoint, the one named in the table above.

Budget for refreshes as well as first reads. Postings change daily, so a watch on a market or an employer is a recurring cost; salary figures change far less often and can be cached with their date. Keep the route, the query and the price of each call in your job record.

Inspect a request and its payment evidence

For a market search, freeq x402 Gateway documents POST /tools/jobs, with a postings quote of $0.002. The description names keywords and locations as inputs and lists the returned fields, including salary where the posting has one; check the provider's schema for the exact body before sending a search.

The listed method and description establish the advertised contract. This explanation does not reproduce an HTTP 402 challenge or certify a paid response. Open the service page's payment evidence and request the challenge for the exact body before authorizing payment. Compare resource, method, network, asset and amount together, and do not reuse a challenge obtained for a different route on the same host.

What this comparison measures

The listing requires an online, payment-ready service, a usable description, an advertised price and at least 90% measured uptime over 30 days. Task selection then reads the endpoint list and keeps salary routes, job searches and routes that read an employer's open roles. A LinkedIn tool with a job-listing mode is shown as a separate type and does not qualify a service alone. A location lookup, a profile or company enrichment and a job product named only in a service description are not priced as job data.

Uptime and average latency come from monitoring checks. Buyer counts are distinct paying wallets observed for the whole service in the window. A successful unpaid HTTP 402 response shows a payment requirement, not a correct salary figure or a live posting after payment. Test with a role, a place and an employer you know before putting a recurring workflow on any endpoint.

Questions

How to pay

Each service answers an unpaid call with HTTP 402 and its price; your agent signs a USDC payment on the listed network and retries. No API key, no account, no subscription. See what x402 is.