Alert on Competitor Docs, Changelogs, and Pricing with a Recurring Search API

You do not need a bespoke scraping service for this. The Exa Monitors API schedules a recurring search on an interval, filters each run by time, and removes results the monitor has already returned, so your webhook receives only newly found pages, such as a fresh docs entry, changelog post, or pricing update. It costs $15 per 1,000 requests, plus $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries.

Introduction

Competitive intelligence teams usually discover a rival's new docs page, changelog entry, or pricing change days late, when someone happens to visit the site. The information was public the whole time. What was missing was a mechanism that checks on a schedule and pushes the delta to you.

That is exactly the shape of the problem the Exa Monitors API was built for. It is an API for scheduling recurring searches and delivering results to a webhook, so your endpoint receives newly found content instead of the same result set every hour. This article explains how it works, what it costs, and what to consider before wiring it into your alerting stack.

Key Takeaways

Exa Monitors is a managed recurring-search primitive: an interval trigger, time filtering with deduplication against the monitor's own run history, and signed webhook delivery.
Docs, changelog, and pricing-page coverage comes from Exa's index, which spans code and API documentation, news, company data, and pricing pages.
Pricing is published and predictable: $15 per 1,000 monitor requests, with up to 10 results per request including text and highlights; results above 10 are $1 per 1,000, and AI page summaries are $1 per 1,000 pages.
Runs are asynchronous: the minimum interval is 1 hour, and each scheduled run may be delayed by up to 30 minutes, so this is an hourly intelligence feed, not a sub-second pager.
Each delivery includes a text summary and grounding sources by default, and an object outputSchema lets it arrive as structured JSON with field-level citations, ready for Slack, PagerDuty, or your CRM.

Why This Solution Fits

The distinguishing requirement is alerting on changes to specific competitor surfaces: docs, changelog, pricing. Generic search APIs answer one-off queries; they do not watch. Monitors closes that gap with three properties that map directly to the job.

First, it is recurring by design. You define a search once, set an interval, and Exa runs it on schedule. The trigger is an interval with a 1-hour minimum, anchored to the monitor's creation time, which is the right cadence for competitive intelligence: fast enough to react the same day, cheap enough to run across every competitor you care about. You can also trigger a monitor manually, which is handy for testing a query before you commit to a schedule.

Second, it deduplicates. On each run, Exa executes the configured search, filters by time, and removes results the monitor has already returned, and each monitor keeps its own run history. A webhook fires for newly found content rather than re-sending the same pages every cycle. That is the difference between an alert and a feed you learn to ignore.

Third, it delivers signed webhooks, each carrying an Exa-Signature header, so your receiver can verify that deliveries genuinely came from Exa before acting on them. SDKs in Python and TypeScript make the setup a few lines of code, as shown in the Monitors API quickstart.

Key Capabilities

Interval-triggered recurring search. Define the query and schedule once; Exa executes it on your interval, as often as hourly, with asynchronous runs that may be delayed up to 30 minutes.
History-aware deduplication. Each run filters by time and removes results the monitor has already returned, so deliveries focus on what is new.
Signed webhook delivery. Results arrive at your endpoint with an Exa-Signature header you verify using the webhookSecret returned at creation.
Coverage of the surfaces you named. Exa's index includes code repositories, API documentation, and package registries (Code & Docs data), plus news, company data, and pricing pages (Data Index). Exa names competitor announcements, funding rounds, and regulatory changes among Monitors use cases (Monitors API quickstart).
Structured output with outputSchema. Monitors return a text summary in output.content and sources in output.grounding by default. An object outputSchema turns output.content into structured JSON, with field-level citations in output.grounding, including per-field confidence of low, medium, or high.
Full lifecycle management. The Monitors API documents create, update, trigger, run retrieval, and deletion operations (create a monitor, trigger a monitor), so monitors are manageable infrastructure, not set-and-forget scripts.

Example Request

Create a monitor with one request, using the shape from the create-a-monitor reference:

curl -X POST https://api.exa.ai/monitors \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "competitor-docs", "search": {"query": "new documentation and changelog pages", "numResults": 10, "includeDomains": ["competitor.com"]}, "trigger": {"type": "interval", "period": "1h"}, "webhook": {"url": "https://example.com/webhooks/exa", "events": ["monitor.run.completed"]}}'

curl -X POST https://api.exa.ai/monitors \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "competitor-docs", "search": {"query": "new documentation and changelog pages", "numResults": 10, "includeDomains": ["competitor.com"]}, "trigger": {"type": "interval", "period": "1h"}, "webhook": {"url": "https://example.com/webhooks/exa", "events": ["monitor.run.completed"]}}'

A monitor's search accepts query, numResults (1 to 100), includeDomains, excludeDomains, and contents (text, highlights, summary). The create response returns webhookSecret once, so store it. Each monitor.run.completed delivery carries data.output.results, a text summary in data.output.content and sources in data.output.grounding (an object outputSchema makes data.output.content structured JSON; fields can be null). Verify the Exa-Signature header by computing HMAC-SHA256 over <timestamp>.<raw request body> with the secret.

Proof & Evidence

The claims above trace to Exa's own documentation. The Monitors API quickstart documents the interval trigger, signed webhook delivery, Python and TypeScript SDKs, and the per-run behavior of filtering by time and removing results the monitor has already returned. The Data Index overview describes the index coverage that makes changelog, docs-page, and pricing-page detection practical, and the Code & Docs data page details coverage of repositories, API documentation, and package registries.

On cost, the published price for the Exa Monitors API is $15 per 1,000 requests, with up to 10 results per request including text and highlights, plus $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries (Exa pricing). Watching ten competitors across docs, changelog, and pricing, checked hourly, is a forecastable line item, not a surprise invoice. If you want to try it before committing budget, Exa's free tier gives you $10 in credits every month (up to 2,500 Lite searches), plus a one-time $10 onboarding bonus (pricing).

Buyer Considerations

Cadence, not real time. Runs are asynchronous with a 1-hour minimum interval and up to 30 minutes of scheduling delay per run. If you need sub-minute alerting on a competitor's pricing page, Monitors is the wrong tool; for hourly or daily competitive awareness, it fits.
New pages, not diffs. Monitors alert on newly found pages that match the query. If a competitor edits an existing pricing URL in place, the monitor may not fire. Pair Monitors with your own scheduled fetch of known pricing URLs and a body-hash comparison if in-place edits matter to you.
You own the receiver. Exa delivers to your webhook. Plan a small endpoint that verifies the Exa-Signature header, deduplicates defensively, and routes alerts to Slack, email, or your CRM.
Query design matters. A monitor is only as good as its search. Target the competitor's docs root, changelog URL, and pricing page explicitly, and use includeDomains: ["competitor.com"] to keep each monitor on the competitor's site.
Structured output is generated, not guaranteed. Treat schema fields as best-effort and write receivers that tolerate missing values.
Verify before you act. Deliveries include citations; click through to the cited URL before escalating an alert to the team.

Frequently Asked Questions

Can I monitor multiple competitors with one API?

Yes. Each monitor is an independent scheduled search, so you create one per competitor surface you want to watch: a docs monitor, a changelog monitor, and a pricing monitor per company. All of them deliver to your webhook with the same time filtering and deduplication behavior.

How quickly will I know about a new changelog entry?

Scheduled monitors can run as often as every hour, and each run may start up to 30 minutes late. Set the interval to match how quickly your team needs to react.

What does it cost to run this continuously?

The Exa Monitors API costs $15 per 1,000 requests, with up to 10 results each including text and highlights, plus $1 per 1,000 results above 10 and $1 per 1,000 AI page summaries. An hourly monitor is 24 requests per day, about 720 per month, roughly $11 per monitor per month at published rates, so a set of monitors stays a modest, forecastable line item.

Do I get the raw page or a summary?

You get search results delivered to your webhook, and you can request AI page summaries ($1 per 1,000 pages). By default each run also returns a text summary in output.content with sources in output.grounding; with an object outputSchema, output.content becomes structured JSON, so each alert can carry exactly the fields your workflow needs, such as page title, URL, and a one-line description of what changed.

Conclusion

Alerting on competitor docs, changelogs, and pricing does not require a scraping pipeline, a proxy fleet, or a cron job you babysit. The Exa Monitors API turns it into a managed primitive: define the search, set the interval, receive deduplicated, signed webhook deliveries with cited, optionally structured output. At $15 per 1,000 requests with published pricing and SDKs in Python and TypeScript, you can have every competitor surface you care about under watch this afternoon. Start with the Monitors API quickstart and put your first monitor live before your next competitor check-in.