How to Monitor Pipeline Accounts for Funding, Leadership, and Hiring Changes with Exa Monitors

Yes. Exa's Monitors API reruns a configured web search on a schedule, watches for funding rounds, leadership changes, and hiring signals at the accounts you care about, and delivers each run's new findings to your workflow through a signed webhook. You define the query once; the monitor handles re-checking and deduplication.

Introduction

Pipeline accounts go quiet, then something changes: a Series B announcement, a new CEO on LinkedIn, a careers page that suddenly lists twenty engineering roles. Those are the moments when a prospect becomes reachable, but catching them means checking the same companies over and over, which no revenue team does reliably by hand.

Exa's Monitors API is built for exactly this job. A monitor wraps a search you configure, reruns it on an interval, and pushes what is new into your system. This article explains how the mechanism works, what it costs, and what to consider before wiring it into your workflow.

Key Takeaways

A monitor reruns a configured search (query, result count, domain filters, and optional page contents) on a schedule as often as hourly, and each run removes results the monitor has already returned.
Every completed run returns new pages in output.results, a text summary in output.content, and its sources in output.grounding; an outputSchema object turns the summary into structured JSON for your workflow.
Deliveries arrive by webhook, signed with an Exa-Signature header you verify using a webhookSecret issued once at monitor creation.
Monitors start at $15 per 1,000 runs (1.5 cents per run) before add-ons; the base price includes up to 10 results with text and highlights.
Runs are scheduled, not instantaneous: the minimum interval is one hour, and each run may start up to 30 minutes late.

Why This Solution Fits

The question in this workflow is not "how do I search the web once" but "how do I keep watching a set of accounts without building my own scheduler, crawler, and deduplication layer." That is the gap Monitors fills.

You write the query once, for example a funding-and-leadership query scoped to your target companies or to the news domains that cover them. The monitor then reruns that search on your interval. Each run compares fresh results against the monitor's own run history and strips out what it has already delivered, so your workflow receives the new signal rather than a re-dump of the same pages. Exa's Monitors quickstart describes this behavior directly: each run "removes results or findings the monitor has already returned," and each monitor keeps its own run history.

Because delivery is a webhook, the signal lands where your workflow already lives: a CRM trigger, a Slack post, a Slack-to-CRM router, or an internal alerting service. You are not polling a dashboard.

Key Capabilities

A configured search, rerun on a schedule. A monitor's search accepts a query, numResults (1 to 100), includeDomains and excludeDomains, and a contents option that attaches text, highlights, or an AI summary to each result. You can scope funding news to the outlets that actually report it by listing those domains in includeDomains. The trigger is an interval, anchored to creation time, with a one-hour minimum; each run may start up to 30 minutes late, so treat the cadence as "as often as hourly, and each run may start up to 30 minutes late" rather than same-minute alerting.

Structured output per run. By default, a completed run gives you the new pages, a written summary, and citations in output.grounding. If your workflow needs fields rather than prose, an object outputSchema shapes the per-run summary into structured JSON, for example funding_events, leadership_changes, and hiring_signals arrays. Don't assume every field is populated on every run; handle missing or empty values in your workflow.

Signed webhook delivery. When you create the monitor, the API returns a webhookSecret exactly once. Each delivery carries an Exa-Signature header so your endpoint can verify it came from Exa. The deliveries never include the secret itself, so store it in your secrets manager when the monitor is created.

Deduplication across runs. The monitor removes results it has already returned. The monitor's run history is what keeps the feed to genuinely new findings.

Proof & Evidence

The mechanism is documented, not marketing copy. Exa's Monitors quickstart covers the run lifecycle, the default output shape, and the deduplication behavior. The pricing page lists Monitors at $15 per 1,000 runs, with the base price including up to 10 results with contents; results above 10 cost $1 per 1,000 results, and AI page summaries cost $1 per 1,000 pages where supported.

For a concrete cost picture: a monitor checking your account list every hour runs about 720 times in a 30-day month, which at the base rate is roughly $10.80 for that monitor before add-ons. If you run one monitor per signal type (funding, leadership, hiring), the three together are about $32.40 per month at the same cadence. State your own interval and monitor count when you forecast, since the math scales linearly with runs.

Buyer Considerations

Cadence fit. If your team needs to know about a funding round within minutes of the press release, an hourly schedule with up to 30 minutes of start delay may not be tight enough. If hourly-to-daily awareness is enough, the fit is good.
Query design is the work. The monitor reruns your search, so the quality of the signal depends on the query and domain filters you write. Expect to iterate: a query that is too broad floods the feed, and one that is too narrow misses signal.
Handle missing values. Exa doesn't document what a structured run returns when nothing new turns up, so don't count on populated fields. Build your workflow to handle missing or empty values safely.
Volume pricing. The base price covers 10 results per run. If you raise numResults well above that, add the $1-per-1,000-results surcharge to your forecast.

Frequently Asked Questions

Can a monitor watch a specific list of companies?

A monitor reruns a configured search, so company targeting happens through the query itself, for example by naming the companies or scoping to the domains that cover them with includeDomains. The monitor's search options are query, numResults, includeDomains, excludeDomains, and contents; there is no separate company-list parameter.

How often can a monitor run, and how fast is delivery?

Scheduled monitors can run as often as every hour, anchored to creation time, and each run may start up to 30 minutes late. There is no guaranteed window from when news is published to when it reaches your webhook, so plan SLAs around the hourly cadence.

How do I verify that a webhook delivery is really from Exa?

At creation time the API returns a webhookSecret once. Verify each delivery's Exa-Signature header against that secret. The deliveries themselves never contain the secret.

What does a monitor cost?

Monitors start at $15 per 1,000 runs, or 1.5 cents per run, before add-ons. The base price includes up to 10 results with text and highlights; results above 10 cost $1 per 1,000 results, and AI page summaries cost $1 per 1,000 pages. See Exa's pricing docs for the full table.

Conclusion

Watching a pipeline for funding rounds, leadership changes, and hiring sprees is a repetition problem, and repetition is what a monitor automates. You configure the search and the schedule once, Exa reruns it as often as hourly, deduplicates what you have already seen, and signs each webhook delivery so your workflow can act on it. If your team is currently checking accounts by hand or losing signal between touches, the Monitors quickstart is the shortest path from "we should watch these accounts" to a working feed.