Updated . By the Headcount Labs data team. We sell one of the products compared here. Facts about other providers come from their own pages, read on the date above.

This guide covers the job postings slice of Coresignal only. Coresignal also sells company and employee data, and for those the alternatives are different providers (People Data Labs and Crustdata are two we mention below). For job postings alone, the published price for 3 million jobs in one month ranges from $29 (Headcount Labs, which we sell) to $5,500 (TheirStack). Coresignal's cheapest plan that covers 3 million is $3,000. Coresignal stays the better choice when you need years of history or company and employee records from the same vendor.

What Coresignal sells for jobs

Coresignal's pricing page, read on October 19, 2026, shows two ways to buy job data.

  • Database APIs, priced in credits. A full job posting record costs 1 credit. Employee and company records cost 20 credits each. Monthly plans run from Mini at $49 for 2,500 credits up to Elite at $5,000 for 10,000,000 credits. There is a 7-day free trial.
  • Datasets. Its job postings dataset is listed at "482M+ job postings". Dataset prices depend on the agreement length, record count and other factors, with monthly payments on a yearly contract.

Its jobs API page says it adds "1 million new jobs added daily" and that "all active jobs rescraped every 24 hours". It matches each posting to a company, offers an Agentic Search API and an MCP server, and delivers to Snowflake, Databricks or S3.

Why "$0.50 per 1,000" and "$3,000 for 3 million" are both true. The Elite plan works out to $0.50 per 1,000 credits, but only if you buy all 10 million credits for $5,000. If you need 3 million job records in a month, the smallest plan that covers it is Scale: $3,000 for 4,000,000 credits. That is $1.00 per 1,000 for the 3 million you use. The unused million rolls over for three months.

Job postings providers compared

The "3 million jobs in one month" column is the cheapest published way to get 3 million job records in a single month on each provider's own pricing page, read on October 19, 2026. The per-1,000 figure is that price divided by 3,000.

ProviderWhat it sellsFree3 million jobs in one monthPer 1,000 at that volumeHistory and size, as stated
Headcount LabsJob postings API and MCP server100,000 records every month$29$0.018,353,752 open jobs. No archive of closed jobs
HirebaseJob postings API500 jobs a month$1,999 (Scale $999 for 2M, then $1 per 1,000)$0.67230k+ career pages. History back to 2023 on Enterprise
CoresignalCompany, employee and job data7-day trial$3,000 (Scale, 4M credits)$1.00482M+ job postings dataset
TechmapJob postings API, feeds and datasets1,000 jobs$2,999 at the list rate of $1 per 1,000$1.00451M+ jobs since 2020; 12M active a month
JobsPipeJob postings API and MCP server1,000 credits once$3,150 (Business $525 for 500K, then $1.05 per 1,000)$1.0511.5 million active postings, 30+ sources, 12 months of history
Fantastic.jobsJob postings API14-day trial$4,200 ($2,800 for 2M, then $0.0014 a job)$1.403M+ career site and 11M+ job board jobs a month; 6-month backfill
TheirStackJobs and technographics200 API credits a month$5,500 (5,000,000 API credits)$1.83255M jobs across 195 countries since 2021
PredictLeadsCompany signals, including job openings100 API calls a monthNot published per jobNot publishedFlat files with history from 2015
Bright DataDatasets, including LinkedIn and Indeed job listingsA free sample downloadNot published for 3MNot publishedPer-record datasets with a monthly minimum
People Data LabsPerson, company and job posting data (job postings in beta)Not checkedNot publishedNot published28.8 million jobs from 54,000+ companies

Prices are monthly list prices in USD from each provider's own page. Annual plans can be cheaper. Ours: 100,000 records free, then $0.01 per 1,000, so 3,000,000 records cost $29.

What it costs at other volumes

The 3 million column hides how prices scale. Here is the cheapest published way to get each volume in one month, worked out from the same pages. Where a plan has overage, we used it when that was cheaper than the next plan up.

Jobs in one monthHeadcount LabsHirebaseCoresignalJobsPipeTheirStack
100,000$0$249 (Growth)$1,000 (Growth, 150K credits)$149 (Growth)$600
500,000$4$624 (Growth plus overage)$1,500 (Premium, 1M credits)$525 (Business)$1,200
1,000,000$9$999 (Scale)$1,500 (Premium)$1,050 (Business plus extra credits)$1,500
3,000,000$29$1,999$3,000 (Scale)$3,150$5,500 (5M credits)
10,000,000$99$8,999$5,000 (Elite)$10,500 at list ratesNot published

Two things stand out. Coresignal gets relatively cheaper at the top: at 10 million it beats every provider here except us, because the Elite plan's rate is $0.50 per 1,000. JobsPipe says it prices 1 million a month and up with each customer, so its last two rows are list rates for extra credits and a contract may cost less. TheirStack's largest published plan is 5 million credits.

Check what counts as a "record" before you compare. With us, a record is one job returned or one change event, and counts are free. Coresignal charges a credit per job record. JobsPipe charges one credit per job per calendar month, and says a job it already charged you for is free when it comes back that month. That rule makes repeat polling cheap on JobsPipe.

When Coresignal is the better fit

We would point you to Coresignal, not to us, in these cases:

  • You need history. Coresignal sells a dataset of 482M+ job postings. We serve jobs that are open now and have no archive of closed jobs to sell. Techmap (since 2020), TheirStack (since 2021) and PredictLeads (since 2015) also sell history.
  • You need employees and companies with the jobs. Coresignal sells employee profiles and company records next to job postings, linked by company. We have company records for some employers, but no employee data.
  • You already query it with Elasticsearch DSL. Coresignal's APIs accept Elasticsearch DSL. We accept a subset of Elasticsearch-style clauses at POST /v1/jobs/search/es_dsl, which makes a move easier but not automatic.
  • You want files landed in your warehouse. Coresignal delivers to Snowflake, Databricks and S3. We deliver through the API, exports of up to 100,000 jobs each, and an open snapshot on Hugging Face.
  • You need jobs that only appear on job boards. We read employers' own career sites and ATS boards. A job posted only on a job board is not in our data. Several providers in the table read job boards too.

When a jobs-only API is enough

Most job data projects do not need employee profiles or a ten-year archive. They need today's open jobs with clean titles, locations, pay and a working apply link. That is true for a job board backfill, a hiring signal in a sales tool, a labour market dashboard, or an AI assistant that searches jobs. For those, a jobs-only API is simpler and usually much cheaper. At 3 million records a month the gap in the table runs from $29 to $5,500.

Before you switch, decide which of these matters most to you:

  1. Freshness. How soon a closed job disappears. Ask each vendor for the share of jobs whose apply link still works, and test 20 yourself.
  2. Coverage of your segment. Count jobs for the employers and places you care about. Counts are free with us, so this test costs nothing.
  3. Fields. Pay, location and posted date fill rates differ a lot by source. Pick 100 records and count blanks.
  4. Price at your real volume. Use the column above, not the "from" price.

A Headcount Labs record, side by side

Here is one real job from our API, trimmed. Each value carries a state: known means the source published it, derived means we computed it and says how, and extraction_failed means we could not read it. We do not fill gaps with guesses.

curl -s "https://api.headcountlabs.com/v1/jobs?title=registered%20nurse&state=TX&has_pay=true&limit=1&include=source_data" \
  -H "Authorization: Bearer $HEADCOUNT_API_KEY"
{"data":[{
  "job_id":"a795f0c7-1c1f-4f1e-ab4a-a0edfd53ab6b",
  "currentness":"current","stale":false,
  "employer_name":{"state":"known","value":"AMN Healthcare"},
  "title":{"state":"known","value":"Registered Nurse – Labor & Delivery"},
  "work_arrangement":{"state":"extraction_failed"},
  "locations":[{"state":"known","value":{
    "msa":{"type":"metro","cbsa_code":"41700","cbsa_title":"San Antonio-New Braunfels, TX"},
    "zip":"78229","city":"San Antonio","region":"US-TX","country":"US","county_fips":"48029"}}],
  "job_first_seen_at":"2026-10-12T22:00:35.979Z",
  "postings":[{
    "source":"employer_site","source_posting_id":"3599625","posting_status":"listed",
    "posting_url":{"state":"known","value":"https://www.amnhealthcare.com/job-details/3599625/"},
    "application_url":{"state":"known","value":"https://www.amnhealthcare.com/apply/?jobIds=3599625"},
    "pay":{"state":"known","value":{"max":1865,"min":1774,"currency":"USD","interval":"unknown"}},
    "source_posted_at":"2026-10-13T07:36:07.553Z",
    "last_completed_fetch_at":"2026-10-17T15:37:15.570Z",
    "source_data":{"employment_type":"Travel","source_type":"employer_site","availability":"listed"}}]}],
 "snapshot_watermark":"2026-10-19T15:20:54.671Z"}

This record shows one honest gap. The employer published pay of $1,774 to $1,865 but did not say per what, so the interval is unknown rather than a guessed "week". A Coresignal job record is a different shape: one flat record per posting, matched to a Coresignal company. Map fields by meaning, not by name.

Moving from Coresignal: practical notes

  1. Count first. Run GET /v1/jobs/count with your usual filters. It is free and shows whether your segment is covered.
  2. Map your queries. Simple filters (title, company, country, state, posted date, remote) become query parameters. Elasticsearch-style queries can go to POST /v1/jobs/search/es_dsl, which accepts bool, term, terms, match, match_phrase, range, exists and query string clauses.
  3. Replace full re-pulls with the changes feed. GET /v1/jobs/changes returns created, updated and expired events after a time you give, so you pull only what changed.
  4. Join on your own company keys. Our company_id is our own ID and is null for many jobs. Join on employer name and website in your own system if you need a company link everywhere.
  5. Keep your own IDs stable. Our job_id stays the same across postings of one opening, so a job posted on three boards is one row. If your system expects one row per posting, use the postings array, where each entry has its own posting_id.
  6. Run both for a week. Compare counts and spot-check 50 jobs from each against the employer's page. Then decide.

Here is the Elasticsearch-style route with a real answer from October 19, 2026 at 2:16 PM ET:

curl -s https://api.headcountlabs.com/v1/jobs/search/es_dsl \
  -H "Authorization: Bearer $HEADCOUNT_API_KEY" -H 'Content-Type: application/json' \
  -d '{"query":{"bool":{"must":[{"match_phrase":{"title":"product manager"}}],
       "filter":[{"term":{"country":"US"}},{"term":{"work_arrangement":"remote"}}]}},
       "limit":2,"fields":["title","employer_name","locations"]}'
{"data":[
  {"job_id":"6e75c75f-79c4-46da-a6a4-8f9afb9159b2",
   "employer_name":{"state":"known","value":"Humana"},
   "title":{"state":"known","value":"Lead Product Manager"},
   "locations":[{"state":"known","value":{"msa":null,"region":"US-TX","country":"US","county_fips":null}}]},
  {"job_id":"13efa073-7e73-425e-8c8a-70f734e1631c",
   "employer_name":{"state":"known","value":"Revolut"},
   "title":{"state":"known","value":"Credit Product Manager"},
   "locations":[{"state":"known","value":{"msa":null,"region":"US-NY","country":"US","county_fips":null}}]}],
 "next_cursor":"eyJ2IjoyLCJr...","snapshot_watermark":"2026-10-19T15:20:54.671Z"}

Alternatives for company and people data

If you use Coresignal mainly for employee or company records, a jobs API will not replace it. Two providers whose pages we read: People Data Labs sells person and company data and lists job posting data in beta ("28.8 million jobs" from "54,000+ companies"). Crustdata sells real-time company signals, including hiring, starting with $20 in free credits and enterprise plans "from four figures a month".

Questions

What is the cheapest Coresignal alternative for job postings?

Of the providers that publish a price for 3 million jobs in one month, Headcount Labs is the lowest at $29: 100,000 records free every month, then $0.01 per 1,000. Hirebase is next at $1,999.

How much does Coresignal cost for job data?

On October 19, 2026 its monthly API plans ran from $49 for 2,500 credits to $5,000 for 10,000,000 credits, with one credit per job posting record. For 3 million jobs in a month the smallest fitting plan was Scale at $3,000.

Does Coresignal have a free plan?

It has a 7-day free trial, not a monthly free plan.

Which alternative has historical job postings?

Techmap states 451M+ jobs since 2020, TheirStack 255M jobs since 2021, and PredictLeads flat files with history from 2015. JobsPipe includes 12 months of history on every plan. Headcount Labs covers jobs open now.

Do these alternatives have MCP servers too?

Coresignal, JobsPipe and Headcount Labs all list an MCP server for AI assistants. Ours has a keyless endpoint at https://api.headcountlabs.com/mcp/public with six read-only tools, and a full server with 26 tools after sign-in.

How do I test an alternative before I switch?

Run the same five queries you use today on each provider, compare the counts, and open 20 random jobs from each on the employer's own site. Count how many are still open and how many have pay, location and a working apply link.

Is Headcount Labs a full Coresignal replacement?

No. It replaces the job postings part only. It has no employee data and no archive of closed jobs.

Sources

All read on October 19, 2026.

More guides

Try it on real data

100,000 records free every month, no card.

Get started Pricing MCP setup