How to Set Up Recurring Monitors for M&A Rumors and Confirmed Deals

Set up recurring M&A monitoring with the Exa Monitors API: create one monitor per target company per signal type, give each a focused query and an interval trigger (minimum one hour), and Exa runs the search on schedule, filters for new content, removes repeats, and delivers a completion event to your webhook. Setup is one API call per monitor.

Introduction

Deal teams lose deals to information lag. By the time a rumor about a target company reaches your morning digest, the arbitrage is gone, and by the time a confirmed transaction shows up in a filing feed, the market has repriced. The fix is not more manual searching. It is a standing watch: recurring searches that run on their own, notice what is new, and push only the new material to you.

The Exa Monitors API is built for exactly this. You define a search, an interval trigger such as 1h, 6h, 1d, or 7d, and a public HTTPS webhook, and Exa runs the recurring discovery work, filters each run by time and removes results the monitor has already returned, and sends a monitor.run.completed event so your system can retrieve and route the new findings (Monitors API quickstart). This article walks through how to structure monitors for M&A work: separating rumor tracking from confirmed-deal tracking, tuning intervals, and shaping the delivered output so it drops straight into your workflow.

Key Takeaways

Create one monitor per target company per signal type (rumors, confirmed deals, regulatory actions) so each monitor's run history stays clean and interpretable.
Each run filters by time and removes results or findings the monitor has already returned, and each monitor keeps its own run history, so deliveries focus on genuinely new coverage (Monitors API quickstart).
Monitors cost $15 per 1,000 requests, with up to 10 results included per request; results above 10 are $1 per 1,000 and AI page summaries are $1 per 1,000 pages (Exa pricing).
The minimum interval is one hour, and a scheduled run may be delayed by up to 30 minutes, so plan for hourly awareness rather than second-level alerts.
Each run returns a text summary and grounding sources by default; use an object outputSchema to shape each delivery into structured JSON (event type, parties, deal value) with field-level citations you can audit.

Why This Solution Fits

M&A monitoring has two hard requirements that most alerting setups handle badly. First, the signal is sparse: a target company may go quiet for months, then produce a burst of coverage when talks leak. Second, the signal is noisy: the same rumor gets republished across dozens of outlets, and a naive feed buries you in duplicates.

The Monitors API addresses both. Each monitor runs its search on a recurring interval, and each run filters by time and removes results or findings the monitor has already returned, with each monitor keeping its own run history (Monitors API quickstart). Your webhook receives newly found content rather than the same articles on every run. That matters especially for private companies, where there are no filings to subscribe to and the web is the primary signal source.

It is also a managed primitive rather than a pipeline you operate. You do not maintain crawlers, parsers, or schedulers. You write a query, pick an interval, and consume a signed webhook event, so the capability does not depend on one engineer's side project.

Key Capabilities

Recurring scheduled searches. Each monitor carries its own trigger, for example trigger: {type: "interval", period: "1h"} for an urgent query and period: "7d" for a weekly sweep. The minimum interval is one hour; sub-hour schedules are not supported. The schedule is anchored to creation time and may include up to 30 minutes of timing jitter, so treat it as a recurring window, not a fixed-to-the-minute alarm (Monitors create-a-monitor reference).

Deduplication against run history. Each run removes results or findings the monitor has already returned, so repeated coverage of the same rumor does not re-fire your webhook (Monitors API quickstart).

Structured output with citations. By default each run returns a text summary with grounding sources. Pass an object outputSchema on the monitor and Exa returns structured JSON instead, with field-level grounding including citations and confidence; fields can come back null. For M&A work, schema fields like event_type (rumor vs. confirmed), acquirer, target, deal_value, and status turn raw coverage into a machine-readable feed. Keep the schema narrow and request only fields your workflow will validate.

Signed webhook delivery. Completed runs send a monitor.run.completed event to a public HTTPS endpoint that must be the final destination, because redirects are not followed. The webhook secret is returned only when the monitor is created: store it immediately and verify the Exa-Signature header before acting on deliveries. Monitor metadata is echoed in deliveries, so you can attach a company ID, owner, or queue name for routing (Monitors API quickstart).

Relevant data coverage. For M&A signals you can draw on Exa's news coverage, funding announcements and financial market data, and SEC filings (focus a monitor on them with includeDomains: ["sec.gov"]) (Financial Markets data, News data). For litigation or sanctions angles on a target, the legal and public records coverage includes US court opinions with docket metadata (Legal & Public Records data).

Lifecycle controls and testing. Monitors can be active, paused, or disabled. Paused monitors stop scheduled runs but still accept manual triggers, which makes them useful for testing a revised query without deleting the configuration. Use a manual trigger to run a complete test before relying on the schedule, and list runs to inspect completed or failed run data (Trigger a monitor).

Proof & Evidence

The concrete, checkable facts behind the setup:

Pricing and operating limits. Monitors cost $15 per 1,000 requests, with up to 10 results and their text and highlights included; results above 10 are $1 per 1,000 and AI page summaries are $1 per 1,000 pages (Exa pricing). Runs are asynchronous, the minimum interval is one hour, and scheduled runs may be delayed up to 30 minutes (Monitors API quickstart). For a 50-company watchlist checked hourly, that is roughly 1,200 monitor runs per day, or about $18 per day at list price before result and summary overages.
Deduplication behavior. Exa's docs state that each run removes results or findings the monitor has already returned and that each monitor keeps its own run history, which is what makes recurring deliveries useful rather than repetitive (Monitors API quickstart).
Data coverage you can verify. The financial markets data page documents SEC filings, reported financials, earnings call transcripts, prices, analyst estimates, and funding announcements (Financial Markets data). The news data page documents news coverage (News data).
Grounded structured output. The grounding format, including per-field citations with confidence levels, is documented in the Search API reference (Search reference), so every "confirmed" classification in your feed can be traced back to a source URL.
Independent primary source. For confirmed transactions by public companies, 8-K merger filings can be found through SEC EDGAR, so you can cross-check a monitor's "confirmed" classification against the filing itself.

Buyer Considerations

Match the interval to the decision. The one-hour minimum interval and up-to-30-minute run delay mean Monitors give you hourly awareness, not real-time ticks. For corporate development and diligence workflows, that is usually the right granularity; for latency-sensitive trading strategies, it is not.
Separate rumor monitors from confirmation monitors. A rumor query ("acquisition talks", "considering a sale", "exploring options") behaves differently from a confirmation query ("announced acquisition", "definitive agreement", "merger completed"). Separate monitors keep deduplication clean and let you route them to different channels: rumors to the analyst queue, confirmations to the deal team immediately.
Test before you schedule. Confirm your webhook is publicly reachable over HTTPS, verify signatures, log deliveries durably, and make processing idempotent. Trigger a manual run first; this is the fastest way to find a routing or processing error before scheduled events matter.
Watch your result budget. Each request covers up to 10 results; results above 10 are billed at $1 per 1,000. Tight, specific queries per company keep deliveries focused and costs predictable.
Verify before you act. Grounding gives you citations and confidence levels per field, but a rumor is still a rumor. Treat monitor output as a triage layer that tells you where to look, and route low-confidence classifications to human review. Assign an owner to each monitor and alert on failed runs so a quiet news cycle is never confused with a broken pipeline.

Frequently Asked Questions

How fast will I hear about a breaking M&A story?

Scheduled monitors can run as often as every hour, and each run may start up to 30 minutes late. Plan for scheduled awareness, not seconds.

Will I get the same article delivered repeatedly?

No. Each run removes results or findings the monitor has already returned, so your webhook receives newly found content. If a story develops with genuinely new coverage, the new items are delivered.

Can I get structured fields like deal value and event type instead of raw articles?

Yes. Monitors return a text summary and grounding sources by default. Pass an object outputSchema on the monitor and Exa returns structured JSON with per-field grounding, including citations and confidence levels, so every classification can be traced back to a source.

What does it cost to monitor a watchlist?

Monitors cost $15 per 1,000 requests, with up to 10 results included; results above 10 are $1 per 1,000 and AI page summaries are $1 per 1,000 pages. A 50-company watchlist checked hourly is roughly 1,200 runs per day, or about $18 per day at list price before overages (Exa pricing).

Conclusion

Recurring M&A monitoring works best as scheduled, deduplicated search delivered to a webhook, not as a scraping project. With the Exa Monitors API, you create one monitor per target company and signal type, set an hourly-or-longer interval, and receive structured, cited, deduplicated findings at your endpoint, priced predictably at $15 per 1,000 requests. Start with your ten most important targets, tune the rumor and confirmation queries against real deliveries, then scale the script across the full list.