TheirStack Pricing: Two Credit Types, One-Time or Monthly

TheirStack sells two different credits and prices them on two different clocks. A company credit is bought once, in packs from 1,000 to 200,000, and reveals one company inside the app for ninety days. An API credit is bought monthly, in plans from 1,500 to 5,000,000, and is spent per record the API or a webhook returns. Both roll over for twelve months. A buyer who reads the page as one ladder will price the wrong product, because the two tabs answer two different questions: how many companies a team wants to look at, and how many records it wants a machine to pull.

This page walks both ladders as published, the third tab where the vendor sells whole datasets without a price, the credit rules that decide what each unit buys, and the free plan's limits from the vendor's own documentation. Every figure is as published on TheirStack's pricing page and docs on 4 September 2026, read from the pages' own bytes. The page served US dollars to this read, and its structured data carries a euro ladder beside the dollar one, so the currency a visitor sees may differ from the one below.

The app tab: company credits bought once

The default tab is the app, and its control is a slider of credit packs. Each pack is a one-time purchase.

The page states the per-credit rate at the first stop itself, $0.109 per credit for 1,000 credits, and the other rates in that column are division on the published prices rather than figures the page prints. The curve is steep: the 200,000 pack costs a little over nine times the 1,000 pack for two hundred times the credits.

A line beneath the slider offers a monthly subscription for buyers who need credits every month, at what the page states as ten percent off the one-time figure. The visible page prints only the offer. The page's structured data carries the resulting monthly prices, from $98.10 a month for the 1,000 pack to $899.10 for the 200,000 pack, each exactly ninety percent of the one-time figure beside it. That is a subscription that renews a credit pack rather than a separate ladder, and a buyer who wants the subscription rate should confirm it in checkout, since it is in the page's markup rather than its visible text.

Every app pack includes the same product surface as the page lists it: job search across career sites, applicant tracking systems and job boards; company search by the technologies a company uses and what it hires for; company lookup by domain; enrichment of an uploaded list with technologies and buying intent; exports to CSV or Excel or into a connected tool; saved-search email alerts; and no page limits, with 500 results a page, unlimited pages and unlimited team members.

What a company credit buys

The vendor's credits documentation defines the unit precisely, and the definition changes how a pack should be sized.

Revealing or exporting a company consumes one credit. That company, and any of its job postings, can then be viewed or exported an unlimited number of times for ninety days. Unused paid credits roll over and stay in the account for up to twelve months after purchase.

One cap sits inside that definition. Each export is limited to 200 jobs per company. The documentation explains the reasoning in its own words: a company credit is meant for accessing a company's postings rather than for bulk-extracting its entire job history for a single credit, and without the cap one credit could pull tens of thousands of jobs from one employer. The cap applies per company per export, so an export spanning many companies takes up to 200 from each, keeps the most recent 200 where a company has more, and says so in the export dialog. A company's full job history is routed to the API, webhooks or the MCP server instead, billed in API credits at one per job.

1. Step 1Reveal or export a company

   One company credit is consumed the first time

2. Step 2Ninety days of access

   That company and its postings can be viewed or exported again without a further credit

3. Step 3Export cap per company

   Each export carries at most the two hundred most recent jobs from any one employer

4. Step 4Full history goes to the API

   Every posting for a company is pulled through the API, webhooks or the MCP server and billed in API credits

The API tab: credits bought monthly

The second tab prices programmatic access as a monthly subscription with its own slider.

A final slider position reads 5M+ and carries no price. The page prints the per-thousand rate at the first stop, $32.67 per 1,000 credits, and translates the 1,500-credit plan as 1,500 jobs, or 500 companies, their tech stacks or their buying intents, or any mix.

That translation comes from the API credit rules. The documentation charges one credit per job returned by the job search endpoint or sent in a job webhook event, three per company returned by the company search endpoint or sent in a company webhook event, and three per company's full set of technologies in the technographics endpoint. Credits are consumed only when the API returns data or a webhook fires. Each call is processed independently, so repeating a request for the same data consumes credits again, which is the opposite of the ninety-day re-access rule on the app side and worth knowing before a pipeline is written to poll.

Every API plan includes the job search, company search, technographics and buying-intents endpoints, webhooks for new jobs, closed jobs and new companies, an MCP server for AI assistants, a rate limit of four requests a second, 500 results a page with unlimited pages, and unlimited team members sharing one credit balance. Unused credits roll over for twelve months here too.

The datasets tab: a price the page does not print

The third tab sells the underlying data as a delivered feed rather than as credits, and it is the only part of the page with no figure on it. Every dataset option routes to a talk-to-sales button.

The page publishes the scale instead. The jobs dataset is described as 225 million records with 305 thousand new a day, the technographics dataset as 51 million records with about 69 thousand new a day, and the buying-intents dataset as 388 million records with about 526 thousand new a day. A buyer chooses history plus updates, history only, or updates only from a chosen start date. The jobs dataset lists forty or more fields per posting including salary, seniority and location plus the hiring company's domain, industry and size, history back to 2021 across 195 countries and 352 thousand sources, closed jobs with the date each went offline, JSON, CSV or Parquet delivery, hourly to monthly refresh, and delivery to S3, GCS, Azure Blob, Snowflake or an HTTPS endpoint, with unlimited seats and no per-record fee.

Those counts are the vendor's own figures about its own data, presented here as the page presents them and not audited. The pricing fact is the absence: a dataset buyer gets a conversation, and the two credit ladders are the only published prices on the page.

AppCompany credits

• Bought once in packs, or monthly at a discount
• One credit reveals one company for ninety days
• Exports capped per company
• Twelve-month rollover

API, webhooks and MCPAPI credits

• Bought monthly on a slider
• One credit per job, three per company or technographic lookup
• Every call billed independently
• Twelve-month rollover

DatasetsDelivered feeds

• No price printed
• History, updates or both from a chosen start date
• Delivered to cloud storage or a warehouse
• A sales conversation is the checkout

The free plan, from the documentation

The pricing page marks a free position on both sliders. The vendor's plans documentation states what it holds: 50 company credits and 200 API credits every month, free indefinitely, for users who have never paid for credits. Once a first payment is made the account becomes a paid plan member from that moment.

The free plan's limits sit in a comparison table on that page. Search results are capped at 25 a page and five pages, against 500 a page and unlimited pages on a paid plan. Workspace invitations are capped at ten in total against unlimited. The rate limit is two requests a second against four. Technographics results are unlimited on both. Paid plans keep the monthly 50 company credits and 200 API credits on top of whatever was purchased.

That table answers the question a trial is for. Five pages of 25 results is 125 rows a search, which is enough to see whether the filters produce the companies you want and too few to build a list from, which is presumably the point.

What the credit terms commit to

• ✓Yes: Unused paid credits of both types roll over for twelve months
• ✓Yes: A revealed company stays open for ninety days without a further company credit
• ✓Yes: Team members are unlimited on paid plans and share one balance
• ✓Yes: Cancel any time, no commitment, stated at the top of the page
• ✕No: A repeated API request for the same record is free the second time
• ✕No: One company credit exports a company's entire job history

Sizing the two ladders against a real motion

The two credit types map onto two different jobs, and most teams need one of them far more than the other.

A team that works signals by hand, opening a company that just posted a relevant role, reading its stack and deciding whether to approach, spends company credits at the rate it reads companies. A pack of 1,000 covers a thousand companies over as long as it takes to read them, since the credits roll over for a year, and the monthly subscription only earns the ten percent discount the page states if a thousand new companies a month are actually being opened.

A team that pipes signals into a system spends API credits at the rate the system pulls records, and the three-to-one ratio between a company and a job decides the bill. Pulling every new job matching a filter costs one credit a posting. Pulling the company behind each costs three more. A pipeline that asks for the company on every job triples its consumption, so the cheaper design pulls jobs, deduplicates by employer, and looks the company up once. The vendor's own sizing hint on the page is to run the filter in job search for the last thirty days and read the result count as an approximation of monthly volume.

The wider argument for treating a hiring or technology signal as a filter rather than a message is in this site's B2B prospecting guide, and TheirStack sits in the hiring and tech signal category of this site's sixty-tool stack sheet, which says on the page itself that it publishes no per-unit prices because they move. This page is the dated exception to that rule, and the date is the point.

What the page does not answer

Three things a buyer would reasonably want are not on the pricing page or in the two documentation pages read for this article.

There is no published figure for the datasets. There is no published statement of what happens to app-side rollover credits at the twelve-month mark beyond their expiry, such as a notice period. And the monthly subscription for company credits is described in prose and priced only in the page's structured data, so a buyer should confirm the renewal terms at checkout rather than infer them from the ten percent line.

For the competitive set, the generated TheirStack alternatives page carries the comparison table, and this page does not repeat it. Where a data purchase scales per record rather than per seat, this site's cold email tool stack guide sets out which categories of a stack behave that way and why they get under-priced at planning time.

The short version

TheirStack publishes two credit ladders and one unpriced tab. Company credits are bought once, from $109 for 1,000 to $999 for 200,000, with a monthly subscription at ten percent off carried in the page's structured data; one credit reveals a company for ninety days and exports at most 200 of its jobs. API credits are bought monthly, from $49 for 1,500 to $5,500 for 5,000,000, at one credit a job and three a company or technographic lookup, with every call billed independently. Both roll over for twelve months. Datasets are sold by conversation. The free plan, per the docs, is 50 company credits and 200 API credits a month with 25 results a page over five pages.

If you would rather have the signal read and the list built for you, start a free campaign and we will build the targeting, the copy and the sending infrastructure around your market.

Pricing and features verified as of September 2026. Verify current terms with the vendor before relying on them.