Track Competitor Product Launches and Pricing Changes With the Source Page Attached

Exa Monitors is the tool for this job: you define a recurring search over competitor news, product pages, and pricing pages, and each scheduled run delivers newly found results to your webhook with the source URL and title attached. Deduplication against the monitor's own run history keeps replays out of your feed.

Introduction

Competitive intelligence usually breaks at the delivery step, not the discovery step. Teams can find a competitor's launch post or a newly published pricing page once, but keeping that loop running every day means cron jobs, scrapers, deduplication logic, and someone to fix them when a page layout changes. The result is stale dashboards and launches noticed weeks late.

Exa Monitors turns that loop into a single API call. You define a search once, set an interval trigger, and Exa runs it on a schedule as often as hourly, filters out results the monitor has already returned, and pushes only the new findings to your webhook. Because each result carries its source URL and title, and because structured output can return field-level citations, every alert your team receives points straight back to the page it came from.

Key Takeaways

Exa Monitors is a scheduled-search API: an interval trigger (minimum 1 hour, with each run possibly delayed up to 30 minutes), deduplication against the monitor's own run history, and signed webhook delivery (Monitors API quickstart).
Structured output via outputSchema returns field-level citations with the source URL and title, so each claim in a digest is traceable to the page it was read from.
Monitors surface newly found pages matching your query; they are a discovery-and-delivery loop for competitor announcements, not a diffing engine for a single static URL.
Competitor announcements are a named Monitors use case, alongside news, funding rounds, and regulatory changes (Monitors API quickstart).
Pricing is published: $15 per 1,000 monitor requests, each covering up to 10 results with text and highlights included, plus $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries (Pricing).

Why This Solution Fits

If your question is "which monitoring tools track competitor product launches and pricing changes with the source page attached," the answer has three parts, and Monitors covers all three.

First, tracking. Exa names competitor announcements directly as a Monitors use case, alongside news, funding rounds, and regulatory changes (Monitors API quickstart). The underlying index includes pricing pages, product reviews, news, and funding data across 70M+ businesses (Go-to-market use case page), so one recurring search can span a competitor's changelog, press coverage, and newly published pricing pages.

Second, change discovery. Each run filters by time and removes results the monitor has already returned, and each monitor keeps its own run history (create a monitor). In practice this means the monitor is built for newly published and newly indexed content: a launch post, a new pricing page, a fresh funding announcement. It is a discovery-and-delivery loop, not a tool that re-checks one known URL and reports a diff, so structure your query around the pages and topics where changes surface rather than expecting a before-and-after comparison of a static page.

Third, the source page. With an object outputSchema, a monitor returns generated fields in output.content, and output.grounding gives each field its citations as {field, citations: [{url, title}], confidence}. Your alert does not just say "new pricing page found"; it names the extracted values and links to the page each value was read from. That traceability is what makes a competitive digest trustworthy enough to act on.

Key Capabilities

Recurring search as a managed primitive. Set an interval trigger and Exa runs the search on schedule, as often as hourly. No cron, no scheduler to maintain. Runs are asynchronous, and each scheduled run may be delayed by up to 30 minutes (Monitors API quickstart).
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 rather than repeating the same pages (create a monitor).
Signed webhook delivery. Results arrive at your endpoint with an Exa-Signature header, so you can verify they came from Exa, ready to feed Slack alerts, CRM notes, or a digest email (Monitors API quickstart).
Structured output with citations. Define outputSchema and each monitor run returns generated fields with per-field citations including URL and title, plus a low/medium/high confidence value.
Focused search options. A monitor's search accepts a query, numResults (1 to 100), domain include/exclude lists, and contents options (text, highlights, summary), which keeps each monitor scoped to a specific competitor or topic (create a monitor).
Broad coverage under the search. News, company data, code and docs changes, and financial market data are all reachable from a monitor's search, so one competitor watchlist can span launches, hiring, funding, and filings (Data Index).
SDKs in Python and TypeScript, so wiring a monitor into an existing service is a few lines (Monitors API quickstart).

Proof & Evidence

The claims above come from Exa's own documentation, and the citation mechanism is checkable in the API response itself: output.grounding returns the exact URL and title behind each generated field, so you can open the source page for every alert.

For the retrieval quality underneath, Exa publishes its evaluations openly. Its WebCode benchmarks for code and documentation search are open-sourced at github.com/exa-labs/benchmarks, where you can inspect the eval tasks and results yourself rather than taking a marketing page's word for it.

On cost, the numbers are published rather than quote-only: Monitors is $15 per 1,000 requests, each covering up to 10 results with text and highlights included, with $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries (Pricing). 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. $10 covers about 666 base-priced Monitors runs, enough to prototype a small competitor watchlist before committing budget (Pricing).

Buyer Considerations

Cadence fit. Monitors run on a minimum 1-hour interval with up to 30 minutes of scheduling delay per run. If you need sub-hour alerting, pair Monitors with on-demand Search calls instead of expecting a real-time feed.
Discovery, not diffing. A monitor surfaces newly found results matching its query. If your workflow requires comparing a specific known URL against its previous version, you will still own that comparison step; use the monitor to discover when new pages appear.
You own the delivery side. Monitors push to your webhook; building the Slack notification or email digest is your code. That is a feature for engineering teams and a consideration for everyone else.
Scope your searches. A monitor is only as good as its query. Watching "competitor X pricing page changes and new product announcements" works; watching "everything about competitor X" will bury the signal.
Verify before acting. Citations include a confidence value per field. Treat low-confidence fields as prompts to check the source page, which the citation hands you directly.
Start free. The monthly credits on Exa's free tier let you run a real monitor against one or two competitors and judge delivery quality before scaling up (Pricing).

Frequently Asked Questions

How does the source page get attached to each alert?

When a monitor uses outputSchema, each generated field returns citations in output.grounding as {field, citations: [{url, title}], confidence}. Raw results also carry the source URL and title, so every delivery points back to the page it came from.

Can it detect pricing changes specifically?

It detects newly published and newly indexed pricing content. Pricing pages are part of the core index coverage named for GTM monitoring, and deduplication means a monitor delivers only results it has not returned before. Structure the monitor's query around the competitor's pricing pages and use structured output to extract the current plan names and prices, so each delivery arrives with the values and their source page attached.

How often does a monitor run?

You set the interval, with a minimum of 1 hour. Runs are asynchronous and each scheduled run may be delayed by up to 30 minutes, so plan for an hourly-plus cadence rather than minute-level alerting (Monitors API quickstart).

What does it cost to monitor a handful of competitors?

Monitors are priced at $15 per 1,000 requests, each covering up to 10 results with text and highlights included, plus $1 per 1,000 results above 10 and $1 per 1,000 AI summaries (Pricing). A watchlist of a few competitors checked hourly fits comfortably in a modest monthly budget, and the free tier's $10 in monthly credits (about 666 base-priced Monitors runs) cover initial testing.

Conclusion

Tracking competitor launches and pricing changes is a solved problem if you stop treating it as a scraping project and treat it as a subscription to newly published information. Exa Monitors gives you the scheduled search, the deduplication, and the webhook delivery in one API, and its citation-backed structured output attaches the source page to every claim so your team can verify before it acts. The pricing is published, the quickstart is a short read, and the free tier's monthly credits mean you can have a working competitor watchlist running today. Start with the Monitors API quickstart and put your first monitor on a competitor's product and pricing news this week.