Skip to main content
Give smry a page that publishes no feed and it checks on a schedule, turning every change into an entry.

Point smry at a page

Most of the web announces nothing. A pricing page, a changelog, a careers board, a status page, a regulator’s notices — all of them change, and none of them tell you.
watch acme.example/pricing and tell me when the prices change
create_monitor · 1 call A day later, a change is an entry:

It is a feed, not a separate thing

A monitor does not live in its own corner of the product. Its changes arrive as an ordinary followed source, which means everything on Follow anything applies to it: ask what is new, put it in a Collection beside a newsletter and an X account, filter that Collection in plain English, or let a scheduled agent pick up only what it has not seen.
what changed across my Competitors collection this week?
A change worth more than a glance can be saved like anything else, and answers questions from your library afterwards.

Say what counts as a change

Left alone, a page changes constantly and none of it matters: a rotating banner, a timestamp, a testimonial carousel. Tell smry what you are actually watching for and it reports only that.
watch their careers page, but only tell me about new engineering roles
The alternative is exact detection, which reports any textual difference at all. Use it when the page is stable and every edit counts — a status page, a legal document, a published API contract.

Watch more than one page

The last one costs the most to run, because it is reading rather than comparing. Reach for a single page first.

A docs site that ships changes with no changelog

Watch the sitemap. New pages appearing is the signal — you learn a feature shipped from the fact that its documentation exists.
watch the sitemap at docs.acme.example and tell me when new pages show up

What cannot be watched

A page behind a sign-in cannot be monitored. Neither can a hard paywall or anything on a private network. smry sees what an anonymous visitor sees, so if the page needs your account to render, there is nothing for a monitor to read.

Questions

As often as every 60 minutes, and daily if you do not say. An hour is the floor — smry will not poll someone else’s page harder than that.
Runs are paid for in monthly credits. Watching a page or a sitemap reserves 1 credit per run; watching a whole site in plain English reserves 10, since each run reads rather than compares.
Three monitors and 150 credits a month. That comfortably holds three daily page monitors. It does not hold one hourly page monitor, because 24 runs a day for a month is 720 credits. Paid plans hold 10 monitors on 720 credits, and 100 on 7,200.
Usually credits rather than slots: the schedule you asked for reserves more than your monthly budget. Slow the schedule, watch a single page instead of a whole site, or drop a monitor you no longer read.
Unfollow it like any other source. That stops the checks and returns both the slot and its reserved credits straight away.
Yes. A scheduled agent asks what changed and smry holds its place between runs, so it acts on each change exactly once and stores nothing itself.

Next

Follow anything

Everything a monitor’s entries can do, because they are feed entries.

Read anything

Pull the full text of the page a change points at.

Watch a page

Target types, detection modes, schedules, and the credit maths.
Last modified on September 13, 2026