Monitor website changes. Get a webhook when they matter.
Watch pages on a schedule and get notified when pricing, content, or pages change.
Powering agents and products with the world's data.
Watch what matters. Hear when it changes.
Pick the pages or data to watch, decide what counts as a change, and get the update delivered to your application.
Watch a page
Re-check a URL on a schedule and diff its visible text. Useful for pricing pages, terms of service, changelogs, and docs.
Watch a sitemap
Get notified when URLs are added or removed. Scope the watch with include and exclude patterns.
Watch a site’s key pages
Describe what matters in plain language. Each run reports relevant changes with a diff, a summary, and evidence.
Set the schedule. Act on the change.
Create the monitor once. Your application receives an event when a scheduled check detects a change.
npm install context.devimport ContextDev from 'context.dev';
const client = new ContextDev({ apiKey: 'YOUR_API_KEY' });
const monitor = await client.monitors.create({
name: 'Linear pricing changes',
mode: 'web',
target: {
type: 'page',
url: 'https://linear.app/pricing',
},
change_detection: { type: 'exact' },
schedule: {
type: 'interval',
frequency: 6,
unit: 'hours',
},
});
console.log(monitor.id);Build with the web as it changes.
Keep your content pipeline current and give users timely updates.
Keep RAG in sync
Re-collect pages when they change, so your retrieval index answers from the current version of the web.
Track the companies you follow
Watch competitor and customer sites, then research what changed in your JSON shape, with sources.
A few things to know.
More details in the API documentation.
How do I monitor a website for changes?
Create a monitor with the target, schedule, and webhook in one API request. Each scheduled run captures the page, sitemap, or key pages, compares them with the previous run, and sends a signed change.detected webhook when something changes.
Can a page monitor click through the page first?
Yes. Page monitors accept up to 5 browser actions before each capture, plus plain-language instructions that describe which changes matter.
What can I monitor?
Monitors support pages, sitemaps, and a site’s key pages. Choose the target and detection mode that match the information your application needs to keep current.
Can I compare meaning rather than exact text?
Semantic detection is available for supported target types. Exact detection is useful when the precise content change matters.
How do I choose the schedule?
Set an interval schedule when you create the monitor. You can also update its schedule or trigger an additional run.
How are changes delivered?
Configure a webhook for change events. Verify the signature in your application and use delivery history to inspect attempts.
Know the moment the web changes.
Watch any page on a schedule and get changes sent to your webhook. The same API key works for scraping, batches, and research.