Introducing Highlights: the context that matters

Monitor website changes. Get a webhook when they matter.

Watch pages, sitemaps, or a site’s key pages on a schedule. Detect the changes that matter and send them to your application with a signed webhook.

Pricing changes

example.com/pricing

every 6 hours

change_detection: exact

Active

Change detected

Team plan · Monthly billing

Before

$20

  • Unlimited projects
  • Shared workspaces
  • Priority support

After

$24

  • Unlimited projects
  • Shared workspaces
  • Priority support

Runs

  1. No change

    18h ago

  2. No change

    12h ago

  3. No change

    6h ago

  4. Change detected

    now

Webhook sent

Signed

change.detected

Checks every 6 hours

Backed by Y Combinator. Teams build with Context.dev.

  • Mintlify
  • daily.dev
  • Daydream
  • Super.com
per page or sitemap run
1 credit
per page run with browser actions
2 credits
per extract run
10 credits
for failed or skipped runs
0 credits
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.dev

monitors.ts

import ContextDev from 'context.dev';

const client = new ContextDev({ apiKey: 'YOUR_API_KEY' });

const monitor = await client.monitors.create({
  name: 'Linear pricing changes',
  target: {
    type: 'page',
    url: 'https://linear.app/pricing',
  },
  change_detection: { type: 'exact' },
  schedule: {
    type: 'interval',
    frequency: 6,
    unit: 'hours',
  },
  webhook: {
    url: 'https://example.com/webhooks/context',
    events: ['change.detected'],
  },
});

console.log(monitor.id);

Choose the right kind of monitor.

Visual tools suit people who review alerts. An API suits software that acts on the change.

CompareContext.dev MonitorsManaged APIVisualpingVisual monitoring appDistill.ioBrowser extensionchangedetection.ioOpen source, self-hosted
Best forApplications and AI agentsNon-technical visual monitoringLightweight browser monitoringFree self-hosting
Change detectionExact text and sitemap diffs, or semantic change detectionScreenshot diffs, with AI importance rulesBrowser-based page watchesPage monitoring you configure and host
PricingFree to manage, runs from 1 credit, failed runs freeFree checks, published allowances varyReported free planFree when self-hosted

Competitor details as of July 2026. Check each vendor for current plans. Best website change detection tools

Build with the web as it changes.

Keep your content pipeline current and give users timely updates.

Ground RAG in fresh content

Keep your retrieval index current. Crawl a sitemap, convert every page to clean markdown, and pipe it straight into embeddings, with no brittle parsers in between.

  • acme.com/docs/api/auth

  • acme.com/blog/release-v3

  • acme.com/pricing

  • acme.com/changelog

markdown → your embeddings

Knowledge base

4 docs indexed

Run deep research on demand

Answer “tell me about this company” with actual sources. Resolve a domain to a typed profile, then expand with schema-based extraction from the live site.

Input

notion.com

Company domain

Notion

San Francisco, CA

Industry
Software (B2B)
Founded
2013
Product
Workspace
Source
notion.com

x · linkedin

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.

Start with your next request.

One API key for scraping, research, brand data, batches, and monitoring.