TheirStack pricing: the full rate card, how credits burn, and the cheaper piece

TheirStack deserves a rare compliment in the jobs-data market: the prices are on a public page. Where Lightcast quotes every contract through sales, TheirStack lists one-time credit packs from $109 and monthly API plans from $59. But credit-metered pricing means the sticker tells you very little until you know how the credits burn - and the consumption rules, not the tier prices, are what set your actual bill. This page collects the full rate card as advertised in August 2026, the metering fine print, worked examples, where TheirStack is genuinely the right buy, and where a flat per-request postings API costs a tenth as much.

What TheirStack sells

Three datasets, largely derived from job postings. The core is the postings corpus itself, which TheirStack advertises at 223 million records with about 313k added daily. On top of it sit two derived products: technographics - which companies use which tools, inferred mostly from what their job ads mention - and buying-intent signals built from hiring activity. You buy all of it through two surfaces: a company-centric web app (search, reveal a company, export CSV or Excel) and a REST API. Bulk dataset delivery - historical dumps, streaming - is a third, custom-quoted tier, which is the same shape most job postings datasets are sold in.

The rate card

App plans are one-time purchases of company credits: $109 for 1,000 credits ($0.109 each), sliding through $199 for 5,000, $299 for 10,000, $399 for 20,000, $549 for 50,000 and $749 for 100,000, down to $999 for 200,000 (about half a cent each). Packs include job search, company search, enrichment, CSV and Excel export, email alerts, 500 results per page and unlimited team members, and unused credits stay valid for 12 months. There is no subscription - this is closer to buying a prepaid card than renting software.

API plans are monthly subscriptions, metered in API credits:

The API is rate-limited to 4 requests per second on every tier, there is a free tier for testing both surfaces, and unused API credits also roll over for 12 months, which is more generous than most metered APIs manage.

How the credits actually burn

This is the part the pricing page states plainly but buyers skim, and it is where the bill is really decided.

• Two separate currencies. Company credits (app) and API credits (API) are different meters. A team using both surfaces is managing two balances.
• App: reveals expire. One company credit reveals one company - its postings, detected technologies and firmographics - for 90 days. After that, opening the same company costs a credit again. Exports are also capped at 200 jobs per company, which matters if your targets are large enterprises with thousands of open roles.
• API: you pay per row returned. Every job a response contains consumes 1 credit, every company returned consumes 3, and every technographics or buying-intent lookup consumes 3. The consequence developers discover in the first invoice: the meter has no memory. A polling loop whose result windows overlap pays for the same posting every time it comes back, so date-filter discipline is not a nicety - it is a cost-control feature you have to build.

What it costs in practice

Three buyer shapes, priced honestly from the card above.

A one-off prospect list. A sales team wants every company hiring for Snowflake skills - say 3,000 companies. That is 3,000 company credits: the $199 pack covers it, one-time, no subscription, and the credits left over stay valid for a year. This is TheirStack’s sweet spot, and nothing below undercuts it.

A continuous postings feed. A product that ingests 50,000 new postings a month consumes at least 50,000 API credits - the $400/mo tier - before any overlap re-billing. At a million postings a month you are on the $1,500/mo tier.

Postings analytics. Trend lines over occupations, skills or industries mean touching a lot of rows, and per-row billing makes exploratory analytics the most expensive way to use the product. If this is your actual job, you want aggregates computed server-side, not rows billed per return.

Where TheirStack is the right buy

An honest pricing page should say when to pay the vendor it is examining. Buy TheirStack when the deliverable is company lists with hiring-derived signals: “companies using X, currently hiring for Y” is its native query, the technographics database is a real product (we compared that market in BuiltWith alternatives), and the one-time packs mean a list-building project needs no subscription at all. Non-developers get CSV and Excel straight from the app. For sales and recruiting prospecting workflows, the credit model fits how the work actually happens.

Where a flat per-request API is cheaper

The economics invert the moment you consume postings continuously, because JobsPipe meters the jobs you take. A search call against POST /v1/jobs/search costs one credit per posting returned - page sizes run to 25 on the free tier, 100 on Builder ($49/mo, 25,000 jobs), 500 on Scale ($349/mo, 300,000 jobs), which is $1.16 per 1,000. The free tier is 1,000 jobs a month, no card.

Rerun the feed math. Ingesting 50,000 fresh postings a month runs on Scale at $349, which leaves 250,000 of the allowance unused. Both vendors meter the same unit now, so the comparison is simply the rate: $1.16 per 1,000 on Scale, against $1.50 at TheirStack's top published tier. And because every posting is liveness-checked and closed roles leave the corpus, you are not spending requests re-downloading dead rows to find out they died. Measured against the live database on the day this post published: 908,384 active postings, deduplicated to one record per vacancy, collected from 11 platforms including LinkedIn, Indeed, Workday, Greenhouse and Ashby.

The filters do the row-selection work server-side, so you never pay to discard rows client-side. One request that would cost thousands of per-row credits elsewhere:

curl -X POST https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "skills_or": ["snowflake"],
    "job_country_code_or": ["US"],
    "posted_at_max_age_days": 30,
    "limit": 100
  }'

Every returned posting carries an ISCO-08 occupation code, an ISIC industry code and extracted skills (how the classification layer works), so the analytics case stops being a row-pulling exercise at all. And if what you are really comparing is data depth per dollar across vendors, our Coresignal comparison walks the same evaluation for the enterprise tier.

The summary that fits in one line: buy TheirStack credits when you need company lists and hiring signals in batches; buy a per-request postings API when you need the postings themselves, continuously. Both vendors put their prices on a public page, and that alone puts this comparison ahead of most of the market.