Product updates

We just shipped the first set of Agent Skills for the TheirStack MCP. A skill is a ready-made playbook you drop into Claude Code (or any MCP client): you give it a product website or a handful of customers, and it does the GTM research for you — grounded in real TheirStack data, not guesses. Every result comes back as a live company count that links straight into a pre-filtered search.

Three skills are available today:

• Find the sales signals for any product or service — Give it a product or service URL. It reads what the offering does and the problems it solves, then maps them to the TheirStack signals a GTM team should run for outbound (technographics, hiring, buying intent), grouped by the offering each one pitches. This is the Qonto playbook, automated.
• Find look-alike companies from your won customers — Give it 4–5 closed-won customers. It profiles each one on TheirStack — what they run, hire for, and mention — extracts the customer fingerprint they share, and finds new companies that look just like them, saved as ready-to-use searches.
• Keyword research for job-description search — Give it a product or service URL. It derives the pains a buyer would describe in a job post, then iterates against real job postings — reading actual descriptions to learn the exact words companies use — and hands back keyword groups, each tied to a feature with a live job count.

All three run on the TheirStack MCP. Sizing every search is free; you only spend credits if you pull the actual companies. Copy any of them into your own setup and point it at a product URL.

Company Search now returns results noticeably faster. Across the searches we measured in production, queries run roughly 2-3x faster than before — so finding the companies you care about feels quicker, whether you're filtering by the technologies a company uses or by the jobs they're hiring for.

This applies everywhere Company Search runs: in the app, in your saved searches, in exports, and through the API. You don't need to change anything to benefit from it.

We also made the default ordering smarter. Results now come back sorted by relevance automatically, so the most relevant companies show up first:

• Filtering by technology → companies we're most confident use it come first.
• Filtering by jobs → companies hiring the most for what you searched come first.
• Both → most confident technology match first, then by hiring volume.
• Neither → larger companies first.

This new default applies automatically to existing API clients and saved searches too — no changes needed on your side. If you set your own sort order, that still takes priority.

When you look up a location, you no longer have to type it exactly the way our catalog stores it. Common variations — missing punctuation, dropped apostrophes, and plain typos — now resolve to the right city instead of coming back empty.

Before, small differences would return 0 results even when the city clearly existed. Now they just work:

• St Petersburg (no period) → resolves to St. Petersburg
• St. Petersburg, FL → ranks St. Petersburg, Florida first, ahead of the more populous Saint Petersburg in Russia
• coeur dalene (missing apostrophe) → resolves to the right city in Idaho
• los angelos, manchster, san fransico (typos) → resolve to Los Angeles, Manchester, and San Francisco

Adding a state also helps us pick the right match: when two cities share a name, the qualifier you type guides which one comes first.

This applies everywhere location lookup happens — autocomplete in the app, the /v0/catalog/locations API endpoint, and the MCP server. Exact and partial inputs are unchanged; we only step in to catch the variants that used to fall through.

Company Search can already filter companies by their job postings (title, location, posted date, technologies…). You can now also require that those jobs have specific fields set — most notably a hiring team.

This mirrors the property_exists filters we have in Jobs Search, but nested inside job_filters so it applies to the jobs a company is hiring for.

API

Pass property_exists_or (any of) or property_exists_and (all of) inside job_filters. Supported values: hiring_team, final_url, employment_statuses.

{
    "job_filters": {
        "job_title_pattern_or": ["Software Developer"],
        "posted_at_max_age_days": 15,
        "property_exists_or": ["hiring_team"]
    }
}

This returns only companies that have at least one matching job with a hiring team — perfect for finding accounts where you already know who to reach out to.

App

In Company Search add the Job property not empty filter (under Job Posting) and select Hiring Team.

You can now filter job searches by whether a posting is still open or has been closed.

When TheirStack detects a job is no longer live at its source, it records the date it went offline. The Job Closed filter lets you act on that date — show only closed roles, only open ones, or narrow to jobs closed in a specific window.

In the app

Open Job Search, click + Add Filter, and select Job Closed. Toggle between open and closed, or switch to a date range to find roles that went offline between two specific dates. The same filter is available in Company Search.

Try it: closed jobs in the last 15 days

In the API

Use is_closed, closed_at_gte, and closed_at_lte in the Jobs API:

curl -X POST https://api.theirstack.com/v1/jobs/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "is_closed": true,
    "closed_at_gte": "2026-05-01",
    "closed_at_lte": "2026-05-31",
    "posted_at_max_age_days": 30,
    "limit": 10
  }'

Available now in Job Search, Company Search, and the Jobs API.

There's a new dataset for closed job postings. Each record includes the job's standard fields plus closed_at — the date TheirStack detected the posting was no longer live at its source.

Files follow the same Parquet format and API as the existing jobs datasets, partitioned by the day the job closed. Request a specific date, a date range, or pull an incremental feed of jobs that closed today.

• closed_at — the day TheirStack first detected the posting was offline.
• Full job record — same schema as the daily jobs dataset: title, company, location, description, and more.
• Daily and hourly partitions — scope the download to exactly the window you need.

Learn more about how datasets work or how to access them.

You already get a webhook ping when a job matching your search is posted. Now you can get one when it closes.

Add job.closed to any job-search webhook alongside job.new. When a previously matched job goes offline, TheirStack sends a notification with the job ID and the date it closed — use the ID to pull the full job and company details whenever you need them.

More on how webhooks work in the webhooks documentation or see the job.closed reference.

Most MCP clients today don't refresh OAuth tokens transparently, so you end up re-logging in every day. Annoying when you're in the middle of a conversation with Claude or Cursor.

Our MCP server now accepts a TheirStack API key as a Bearer token on the same endpoint. Create one at app.theirstack.com → API Keys. Keys don't expire until you revoke them, so the connection stays stable.

The MCP docs now show both options side-by-side inside every client tab — Claude Code, Claude.ai, Cursor, VS Code, ChatGPT, Windsurf, Cline, Codex, Gemini CLI. Pick OAuth or API key per agent; your choice is remembered across tabs.

{
    "mcpServers": {
        "theirstack": {
            "url": "https://api.theirstack.com/mcp",
            "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
        }
    }
}

OAuth still works — it's just no longer your only option.

The Company Type filter now does a better job of keeping staffing, recruiting, and other hiring intermediaries out of your Company Search results when you select Direct Employer.

That matters because many searches are meant to find final customers, not companies selling staffing or recruiting services. If you are looking for companies hiring data engineers, you usually want the employer building the data team, not an agency posting jobs for someone else. If you are looking for companies using Kubernetes, Salesforce, or Snowflake, a technology mentioned by an intermediary in a job post does not necessarily mean the intermediary uses that technology.

With this update, selecting Company Type → Direct Employer removes more of that intermediary noise from company searches, hiring-intent searches, technographic searches, exports, and API results.

Some recruiting firms were previously listed under broader industries like IT Services and IT Consulting, Business Consulting and Services, Software Development, or Hospitals and Health Care. They could still appear in Direct Employer searches even when their descriptions clearly said they offered staffing, recruitment, executive search, or talent placement services.

We now classify more of those companies as recruiting agencies, including companies that describe those services in English, Spanish, Portuguese, French, German, Dutch, Polish, Swedish, Danish, Norwegian, Finnish, Romanian, Hungarian, Czech, Slovak, Turkish, Korean, Arabic, Afrikaans, Japanese, and Hebrew.

Examples of companies this catches:

In production impact checks, this found 30,846 companies that were previously not marked as recruiting agencies.

Note: we are not changing the company's source industry. If a company is listed as IT Services and IT Consulting on LinkedIn or another source, we keep that industry as-is. This means you can still inspect the original industry, and to exclude third-party staffing and recruiting firms, use our Company Type → Direct Employer filter.

Use it in Company Search by selecting Company Type → Direct Employer.

55 million jobs that you couldn't find before — now you can.

When you searched for jobs in Greater London, Los Angeles County, Tokyo or any other county / borough / region / metro area, you'd get back a tiny fraction of the actual jobs in that area. The region a city belongs to wasn't being recorded correctly on most jobs, so when you filtered by that region, almost nothing came back.

We fixed the ingestion so every new job gets the right region tagged, and we backfilled every historical job in the database. 55.2 million jobs are now discoverable through region / county / metro filters that were previously missing them.

Examples

Jobs that match each filter over a 90-day window — click any row to run the search live:

What you need to do

Nothing. If you're already filtering by region IDs via job_location_or / job_location_not (the admin2_id-typed entries in the location catalog) or via the Job Location filter in the UI, your existing queries will start returning the correct, much higher counts. Historical results refresh automatically.

You can now export company search results in LinkedIn Audiences CSV format.

This export keeps only the columns LinkedIn uses to match uploaded company lists: company name, website, email domain, LinkedIn company page URL, and stock symbol. That means you can build an account list in TheirStack and upload it to LinkedIn Campaign Manager without reshaping the CSV by hand.

Use it when you want to build LinkedIn audiences from:

• Companies using specific technologies, such as Salesforce, Marketo, Snowflake, Databricks, or Kubernetes.
• Companies with hiring intent, such as teams hiring for data engineering, platform engineering, sales operations, or compliance roles.

The new format is available from the export modal in Company Search. See the LinkedIn Audiences integration guide for upload requirements, field mapping, and the official LinkedIn template.

Every row in Export History now has a See search button.

Click it and you land on the search page (jobs or companies) with the exact filters that were used to create that export — pre-applied. From there you can:

• Inspect what the export was built on, instead of guessing from the file name.
• Re-run the same search to get fresh results.
• Tweak a filter (add a country, widen the date range, change the keyword) and export again.

Previously, repeating an export meant rebuilding the entire query by hand. Now it's one click from the history table.

The button only appears when the export was built from a re-runnable search (job and company searches). It's hidden for older exports created before we started snapshotting filters, and for export types that aren't searches (company lists, technographics, keyword exports).

There's a new API entry in the sidebar — a single place to keep an eye on how you're using the TheirStack API.

What you'll find there

• Requests over time. A chart of your API requests with a date range picker, so you can spot spikes, drops, or quota issues at a glance.
• Recent requests. The last requests your account made, with one click to jump to the full request log.
• Popular endpoints. A side panel with the most used endpoints — Job Search, Company Search, Company Technologies, and Buying Intents — each with example use cases and a direct link to the docs.
• Shortcut to API Keys. One click from the top of the page to manage your keys.

If you've ever opened TheirStack just to check "is the API still working for me?", this is the page you wanted.

MCP lets AI assistants talk to TheirStack like any other tool — find companies, search jobs, look up technographics, all from a chat. We've had an MCP server for a while, but installing it meant hunting for the right config snippet for your specific client.

There's now a MCP page in the app that does that for you.

What's inside

• One-click install snippets for Claude Code, Claude Desktop, Claude.ai, Cursor, VS Code, ChatGPT, Windsurf, Cline, Codex, and Gemini CLI. Pick your agent, copy the snippet, paste it where it belongs.
• Example prompts you can copy with one click — things like "find SaaS companies hiring for Rust" or "list companies investing in AI strategy in the US" — so you don't have to figure out from scratch what the assistant is good at.

Open it from the sidebar under MCP, or read more in the MCP documentation.

There's a new Use cases page in the app — a filterable gallery of ready-to-run examples to show you what's possible with TheirStack.

Each card explains the goal of the use case, the filters that power it, and lets you open it as a search in one click. No need to figure out the right combination of filters from scratch — start from a working example and tweak it.

A few examples of what's already in the gallery:

• Find companies in M&A mode — companies actively integrating an acquisition, perfect for selling consulting or post-merger tooling.
• Find companies investing in compliance — GDPR, HIPAA, SOC 2. They have a real, active need.
• Find companies investing in ESG & sustainability — companies hiring around sustainability or net zero goals.
• Find companies scaling HR & benefits — those rolling out health insurance, 401k, or paid time off.
• Find companies using Salesforce / HubSpot / Snowflake — straight technographic targeting on top brands like Salesforce, HubSpot, Snowflake, AWS, or any of 32k+ technologies we track.
• Find companies running trade shows & events, buying safety equipment, trading commodities, working with government bodies… and more.

Each one is a real, tweakable starting point — open it, change a filter, and you've got your own list in a couple of clicks.

If you've ever wondered "what else can I do with TheirStack?", that's the page to start from.

The Webhooks page got a full redesign so you can see how your webhooks are performing without clicking into each one.

What's new

• Executions chart, side by side with the list. The page now has two columns: your webhook list on the left, and an executions chart grouped by webhook on the right. One look tells you which webhooks are firing the most, which ones went quiet, and which ones are erroring.
• Filter by status. A new status filter lets you focus on Active, Inactive, Archived, or All. Defaults to Active so the noisy archived ones stay out of the way.
• Filter by team member. On shared workspaces with many webhooks, filter the list to only the ones a specific teammate created.
• No more gaps in the chart. The chart now plots every day in the range, even days with zero events — so trends are easier to read.

More on how webhooks work in the webhooks documentation.

You can now find people on Instantly.ai directly from TheirStack's company search results.

How it works

1. Select companies in any job or company search on TheirStack.
2. Click Find people → Instantly.ai.
3. A new tab opens on Instantly's Lead Finder with the company domains and job titles already pre-filled.

Configure default roles

The job titles we pre-fill on Instantly come from your integration settings. Change them once and they'll apply across all integrations (Apollo, ContactOut, LinkedIn, and now Instantly).

Check out the full guide in our Find people documentation.