Watch Any Ticker for Downgrades, Guidance Changes, and Management Commentary with Exa Monitors

The most reliable way to watch a ticker for downgrades, guidance changes, and management commentary is a scheduled search that delivers only new findings to you. The Exa Monitors API runs recurring searches on your watchlist, filters out results it has already returned, and posts completed runs to your webhook, so a downgrade reported once does not re-fire.

Introduction

If you cover a portfolio, three signals move positions fastest: a rating change from an analyst, a revision to guidance, and anything a CEO or CFO says that departs from the script. The problem is not finding this information once. It is catching it every time, across every ticker, without re-running the same searches all day.

Most workflows break here: alerts land in three inboxes at three different times, if they land at all, and the same coverage resurfaces on every manual check. What you want is one programmatic primitive, and that is exactly the shape of the Exa Monitors API. You define a monitor with a search, an interval trigger, and a webhook destination. Exa runs the recurring discovery work, removes results the monitor has already returned, and sends a monitor.run.completed event so your system can route the new findings.

Key Takeaways

Exa Monitors is a scheduled-search API: you define a query per ticker or watchlist, set an interval (minimum 1 hour, with periods such as 1h, 6h, 1d, or 7d), and completed runs are delivered to your webhook as signed deliveries.
Each monitor keeps its own run history and filters by time, removing results it has already returned, so a downgrade reported once does not re-fire on every check.
Exa's financial data coverage underneath includes SEC filings, earnings call transcripts with speaker-attributed remarks and Q&A, prices, analyst estimates, funding announcements, and economic releases.
Monitors support structured output via outputSchema, so a downgrade alert can arrive as a normalized record (event type, direction, summary) with field-level citations.
Pricing is published: $15 per 1,000 monitor requests (up to 10 results each, with text and highlights included), plus $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries, per Exa's pricing page.

Why This Solution Fits

Watching a ticker for these three signal types is fundamentally a recurring-search problem, not a one-off research problem. You are asking "has anything new appeared?" continuously, across many tickers, for months.

That is the job Monitors was built for. You create a monitor with a query scoped to the company and the signal type, set the interval, and Exa runs the search on schedule and posts the completed run to your webhook. Because each monitor keeps its own run history and removes results it has already returned, the second run does not resend what the first already delivered. You can also trigger a monitor manually to test the query first.

It also fits the way financial signals appear. A downgrade shows up in news coverage and analyst-estimate data. A guidance change shows up in the earnings call transcript, the press release, and the follow-up coverage. Management commentary shows up in the transcript itself, where Exa's financial data coverage includes prepared remarks and Q&A attributed to individual speakers, so you can tell the CEO's answer apart from an analyst's question. The same primitive covers private companies that do not file, where funding announcements and press coverage still flow through the web.

Key Capabilities

Scheduled recurring search. Each monitor runs on an interval you set, with a minimum of 1 hour and supported periods such as 1h, 6h, 1d, and 7d. Runs are asynchronous and may be delayed by up to 30 minutes, so treat Monitors as a cadence-driven watchlist rather than a tick-by-tick feed.

Deduplication against run history. Each run filters by time and removes results the monitor has already returned, and each monitor keeps its own run history. Each delivery is focused on newly found content, the difference between an alert system and a firehose.

Signed webhook delivery. When a run finishes, Exa sends a monitor.run.completed event to the webhook you configured, signed with an Exa-Signature header that your endpoint verifies using the webhookSecret returned once at creation, so you know deliveries came from Exa. Python and TypeScript SDKs make wiring the receiver straightforward.

Structured output with citations. Monitors support outputSchema, the same structured-output mechanism as Search. You define fields like event_type, direction, and summary, and Exa returns the value in output.content with field-level citations in output.grounding, including source URL, title, and a confidence level per field. A downgrade alert can arrive as a normalized record with a link to the source, ready to route into your risk system.

Financial data coverage underneath. The searches your monitors run draw on Exa's financial markets data: SEC filings and reported financials, earnings call transcripts with speaker-attributed remarks and Q&A, prices, analyst estimates, funding announcements, and economic releases. Most of that coverage comes from ordinary queries; on the Search side, category: "financial report" narrows results to filings and reports. A monitor's search accepts only query, numResults, includeDomains, excludeDomains, and contents, so a monitor cannot set category; put the signal terms in the query or use includeDomains. Rating changes reported by financial media fall under the news category on the Search side.

Proof & Evidence

Every capability above is documented:

The Monitors API quickstart documents the interval trigger, signed webhook delivery, time filtering and deduplication against each monitor's own run history, and the Python and TypeScript SDKs. The create-a-monitor reference documents the search options a monitor accepts.
The financial markets data page documents SEC filings, earnings call transcripts with speaker-attributed remarks and Q&A, prices, analyst estimates, funding announcements, and economic releases.
The Search reference documents outputSchema behavior, including output.grounding citations.
Pricing is published on the Exa pricing page: $15 per 1,000 monitor requests (up to 10 results each, with text and highlights included), plus $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries.

One honest caveat on timing: because runs can be delayed by up to 30 minutes, Monitors is not the tool for sub-minute reaction to a headline. It is the tool for making sure nothing on your watchlist slips past you.

Buyer Considerations

Before you build, weigh these points:

Cadence versus latency. The minimum interval is 1 hour and runs may be delayed up to 30 minutes. If your strategy requires reacting within minutes of a downgrade, pair Monitors with an on-demand search path for the moments that matter.
Query design is the real work. "Downgrade" appears in many phrasings. Expect to iterate per signal type, validate with a manual run first, and use outputSchema to shape each run's findings into typed events so false positives are cheap to filter downstream.
Cost scales with results, not just runs. At $15 per 1,000 requests with 10 results included, a 50-ticker watchlist checked hourly is roughly 1,200 requests per day, about $18 per day, before charges for results above 10 or AI page summaries.
Verification stays with you. Structured output arrives with citations, but a signal that will move a position deserves a human click through to the cited source before it triggers action. Treat the monitor as triage, not a decision engine. For filings, check the document against SEC EDGAR full-text search.

Frequently Asked Questions

Can one monitor watch multiple tickers at once?

Yes. A monitor's query can span a watchlist, for example news about a set of companies mentioning rating changes. In practice, many teams prefer one monitor per ticker or per signal type, because deduplication is tracked per monitor and separate monitors give cleaner event streams.

How fresh are the results, and can I force fresh page fetches?

Runs are scheduled and asynchronous, with a minimum interval of 1 hour and possible delays of up to 30 minutes. Content freshness is controlled by contents.maxAgeHours on the search side, a limit on how old cached page content can be, from -1 to 720 hours. Cached copies younger than the limit can still be served and older ones are re-fetched; 0 requests a fresh fetch and -1 uses the cache only. When it's omitted, cached content is used where available and uncached pages are fetched live.

Can I get the downgrade or guidance change as structured data instead of raw articles?

Yes. Monitors support outputSchema, so you can define fields like event type, direction, and summary. Exa returns the value in output.content with per-field citations in output.grounding, including source URL, title, and a confidence level, so each alert arrives as a citable, routable record.

What does it cost to run a ticker watchlist on Monitors?

The published price is $15 per 1,000 monitor requests, with up to 10 results included per request (text and highlights included). Results above 10 cost $1 per 1,000 results, and AI page summaries cost $1 per 1,000 pages. A 50-ticker watchlist checked hourly is about 1,200 requests per day, roughly $18 per day before add-ons.

Conclusion

Downgrades, guidance changes, and management commentary punish slow watchers. The fix is not another dashboard to check; it is a scheduled, deduplicated search pipeline that delivers only new events to the system you already run. Exa Monitors gives you that primitive: define the query, set the interval, verify the webhook signature, and let outputSchema turn raw coverage into typed, cited signals. Read the Monitors quickstart, check the pricing against your watchlist size, and put your first ticker on watch.