Today we're releasing Monitors, in beta, to everyone.
Monitors watch websites for changes so you don't have to. Point one at a page, a sitemap, or a whole site, pick a schedule, and Context.dev checks it for you, as often as every 10 minutes. When something changes, you get a record of exactly what changed and, if you want, a signed webhook to your endpoint the moment it happens.
We built this because so many of you were already building it yourselves on top of our scraping and extraction APIs: cron jobs re-scraping competitor pricing pages, diffing markdown snapshots, prompting an LLM to decide whether a change actually matters. That's a lot of plumbing for a simple question: "did this website change?" Now it's one API call.
Three ways to watch
Page monitors re-scrape a single URL and diff the content exactly. Good anywhere a literal change is the signal: pricing pages, terms of service, changelogs, docs.
Sitemap monitors watch a site's sitemap and tell you when URLs are added or removed. Good for catching new product pages, new blog posts, or delisted content the moment they ship.
Extract monitors are the interesting one. You describe what you care about in plain language, like "track pricing plans and their monthly cost", and each run extracts structured data from the site and semantically compares it to the last run. Cosmetic edits don't fire it; meaningful changes do, each with a confidence score you can threshold.
Built for pipelines, not just alerts
Every monitor keeps a full history of runs and detected changes that you can pull from the API, so this works as an event source for agents and data pipelines, not just a notification tool.
Webhooks are signed with HMAC-SHA256 (the X-Context-Signature header carries a timestamp and signature) so you can verify every delivery actually came from us.
Creating and managing monitors is free. You only pay credits when a run does real work, at the same price as the equivalent API call: 1 credit per page or sitemap run, 10 credits per extract run. Every plan includes monitors: 2 on Free, 50 on Developer, 500 on Pro, and 10,000 on Scale.
Try it
Monitors are live in the dashboard right now. There's even an AI generator that turns a sentence like "tell me when Stripe changes their pricing" into a configured monitor. Or create one from the API:
curl -X POST https://api.context.dev/v1/monitors \
-H "Authorization: Bearer $CONTEXT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Stripe pricing",
"target": { "type": "page", "url": "https://stripe.com/pricing" },
"change_detection": { "type": "exact" },
"schedule": { "type": "interval", "frequency": 6, "unit": "hours" },
"webhook": { "url": "https://myapp.com/hooks/context" }
}'This is a beta: the API shape is stable, but we're still tuning semantic change detection and adding capabilities based on what you build. If a monitor misses something it shouldn't have, or fires when it shouldn't, tell us. That feedback directly shapes what ships next.
Happy monitoring.
- Yahia Bakour, Founder of Context.dev