Track Hiring Surges and Layoffs at Specific Companies with the Exa Monitors API

The practical answer is the Exa Monitors API: schedule a recurring search over job postings, news, and company pages, and Exa filters each run by time and removes results the monitor has already returned, so only new findings reach your webhook. That turns hiring surges and layoffs at specific companies into a continuous, automated leading indicator.

Introduction

Headcount moves before revenue does. A company that quietly opens dozens of engineering roles is signaling expansion months before it appears in a filing, and a company whose job listings vanish while local news reports layoffs is signaling contraction before the next earnings call. For analysts, investors, and go-to-market teams, hiring activity is one of the few company-level signals that updates continuously and is visible even for private companies where there are no filings to subscribe to.

The problem is that checking this manually does not scale. Job boards change daily, layoff coverage appears in outlets you do not read, and by the time a trend is summarized in a report, the leading indicator has already become a lagging one. What you need is a system that watches your list of companies on a schedule and tells you only what changed.

Key Takeaways

Hiring surges and layoffs show up in job postings and news coverage before they show up in financial statements, making them useful leading indicators, especially for private companies.
The Exa Monitors API turns this into a managed primitive: schedule a recurring search, get deduplicated new results delivered to a webhook, no scraping infrastructure required.
Exa's core index includes job postings, news, and company data across 70M+ businesses and 1B+ people records, so company-level watchlists are covered by one API.
Structured output with outputSchema returns fields like "layoffs reported this week" with field-level citations, so every signal is traceable to its source.
The Monitors API is priced at $15 per 1k requests (up to 10 results each, text and highlights included), plus $1 per 1k results above 10 and $1 per 1k AI page summaries, with a minimum interval of 1 hour and runs that may be delayed by up to 30 minutes.

Why This Solution Fits

Most approaches to tracking headcount signals fall into one of three buckets, and each breaks down at the monitoring step.

Manual checking does not scale past a handful of companies. Generic news alerts fire on keywords, not on companies, and they re-send the same article repeatedly. Point solutions built on scraped job-board data lock you into their coverage and their refresh cadence, and they rarely let you define what "surge" means for your own thesis.

The Exa Monitors API fits because it treats recurring search as the product. You write the query that defines the signal, for example "new engineering job postings at Acme Corp" or "layoffs or workforce reduction news at companies in my watchlist," set the interval, and Exa handles the rest. Each run filters by time and removes results the monitor has already returned, and each monitor keeps its own run history, so your webhook receives newly found content rather than the same results over and over (Monitors API quickstart). Each delivery is a digest of what is genuinely new, which is precisely what a leading-indicator workflow needs.

It also works for private companies. Because the signal comes from the open web (job postings, company pages, news) rather than from regulatory filings, you can watch a Series B startup as easily as a public company.

Key Capabilities

Scheduled recurring search. Monitors run on an interval you set, with a minimum interval of 1 hour anchored to creation time. Runs are asynchronous and each scheduled run may be delayed by up to 30 minutes, which is a reasonable cadence for signals that develop over days and weeks rather than seconds (create a monitor).

Deduplication against monitor history. Each run filters by time and removes results the monitor has already returned, so webhook deliveries focus on newly found content (Monitors API quickstart). Your downstream system sees deltas, not repeats.

Signed webhook delivery. Each run posts results to your webhook with an Exa-Signature header, so you can verify the payload came from Exa. SDKs are available in Python and TypeScript, so wiring a monitor into an existing pipeline is a small integration.

Structured output with citations. Pass an outputSchema and each run returns generated fields in output.content, with field-level citations in output.grounding including source URL, title, and a confidence level. Instead of a pile of links, you get a field such as "layoffs reported: yes" with its sources read from output.grounding, which an analyst or a downstream model can act on.

Company, people, and news coverage in one index. Exa's core index spans 70M+ businesses, 1B+ people records, job postings, pricing pages, news, and funding rounds (Go-to-market use case page). The Companies & People data page and News data page describe that coverage in detail. For public companies you can complement hiring signals with a separate Search API call using category: "financial report", which narrows results to filings and reports (Financial Markets data).

Proof & Evidence

The capability claims here come from Exa's own documentation. The Monitors API quickstart documents the interval trigger, signed webhook delivery, deduplication behavior, and the Python and TypeScript SDKs. Exa names news, competitor announcements, funding rounds, and regulatory changes as intended use cases on that page, and its GTM use case page shows a monitor demo built around a "Head of RevOps" search alongside job-posting monitoring, confirming that hiring signals are a designed use, not an off-label hack.

On cost and cadence, Exa's pricing documentation lists the Monitors API at $15 per 1k requests, with up to 10 results per request including text and highlights (the same content treatment as /search), $1 per 1k results above 10, and $1 per 1k AI page summaries. Exa's free tier gives you $10 in credits every month (up to 2,500 Lite searches), plus a one-time $10 onboarding bonus, with no payment method required (see Exa's pricing page). That $10 covers about 666 base-priced Monitors runs, enough to prototype a small watchlist before committing budget.

One honest caveat: a monitor is only as good as its query. "Layoffs" coverage can lag actual events, and job postings can be stale on some boards. Treat monitor output as a signal to investigate, not a verdict, and use the citations in output.grounding to read the underlying sources before acting.

For an independent primary source on layoffs, WARN Act notices from a state labor department and 8-K filings on SEC EDGAR can be used to cross-check what a monitor surfaces.

Buyer Considerations

Cadence fit. The minimum interval is 1 hour and runs can be delayed up to 30 minutes. If you need sub-hour alerting on a single breaking event, a one-off search may fit better; for ongoing watchlists, the cadence is appropriate.
Query design is your job. The API monitors whatever you ask it to. Budget time to write and refine the queries that define "hiring surge" and "layoff signal" for your universe of companies.
Volume pricing. At $15 per 1k requests, a daily monitor across 100 companies costs roughly $45 per month in request costs, before result and summary overages. Model your company count and interval before scaling.
Verification workflow. Plan for a human or automated step that reads the cited sources. Structured output with grounding makes this cheap, but it does not remove the need to confirm a signal before trading or acting on it.
Complementary products. For one-off deep dives after a monitor fires, Exa's Search API and the Agent API cover ad hoc research; Monitors covers the always-on watch.

Frequently Asked Questions

Can this track private companies that do not publish filings?

Yes. The signal comes from the open web: job postings, company pages, and news coverage. Exa's core index includes job postings and company data across 70M+ businesses, so private-company watchlists work the same way as public ones.

How quickly do I find out about a layoff or hiring surge?

Scheduled monitors can run as often as every hour, and each run may start up to 30 minutes late, a cadence that suits signals that develop over days, such as a batch of new postings or a wave of layoff coverage.

Will I get the same results delivered repeatedly?

No. Each run filters by time and removes results the monitor has already returned, and each monitor keeps its own run history. Each webhook delivery is focused on what is new since recent runs.

How much does it cost to run a company watchlist?

The Monitors API is priced at $15 per 1k requests, with up to 10 results per request including text and highlights, plus $1 per 1k additional results and $1 per 1k AI page summaries. Exa's free tier gives you $10 in credits every month (up to 2,500 Lite searches) plus a one-time $10 onboarding bonus. $10 covers about 666 base-priced Monitors runs, enough to prototype before committing budget.

Conclusion

Hiring surges and layoffs are among the earliest company-level signals you can observe from the outside, and they are visible for private companies that never file anything. The gap has never been the existence of the data; it has been the monitoring. The Exa Monitors API closes that gap with scheduled search, deduplication, and cited structured output delivered straight to your systems, at $15 per 1k requests. Define the signal, set the interval, and let the leading indicators come to you. Start with the Monitors API quickstart and put your first watchlist live today.