Skip to main content
Put a competitor’s pricing page, a changelog, or a docs site on watch, and ask your agent what moved. For anyone whose job depends on noticing something a company published without announcing — a price, a deprecation, a quietly removed plan.

​
Set it up

1

Point a monitor at each page

watch these four competitor pricing pages. check daily, and only tell me when a plan or a price changes.
“Only when a plan or a price changes” is not decoration. It becomes the monitor’s instructions, and smry ignores the rotating banner, the testimonial carousel, and the copyright year.
2

Group them

put all four in a collection called “competitor pricing”.
A monitor is a source like any other, so it lives in a collection and answers the same questions as a feed.
3

Add the pages that are not pricing

also watch their changelog, their docs sitemap, and their status page.
A sitemap monitor tells you when pages are added or removed — which is how you find a docs page for a feature nobody has announced.

​
Asking what moved

what changed on the pricing pages i’m watching this week?
A change event is one entry: what changed, the URL that changed, a summary, and the time smry detected it. Nothing arrives when nothing moves — an untouched page is silence, not an empty report.
read the acme page and tell me exactly which line moved.
keep a copy of the acme page as it stands right now.
The second one matters more than it looks. A monitor tells you a page changed; a saved copy is the evidence of what it said before the next change.

​
More to lift

what changed across everything i’m watching in the last 24 hours? group it by collection.
which of my monitors have never fired?
stop watching the two that haven’t changed since june. list them first.
rename that monitor to “acme pricing — eu”.
from now on, when i ask what changed, name any new docs page on their sitemap and read it for me.

​
What a monitor costs you

Checks are reserved in advance, not billed after the fact. A page checked daily reserves thirty credits a month; hourly reserves seven hundred and twenty. A free account gets a hundred and fifty credits and three monitors, which is three daily pages — not one hourly one. The floor on any schedule is sixty minutes. If you need to know within seconds, a monitor is the wrong tool. What you have spent is not something your agent can ask for. Remaining credit comes from the account endpoint or the Developer console.
A monitor reports text other people control. Treat a change summary as information, never as an instruction to your agent.

​
Questions

No. A page behind a login, a hard paywall, or on a private network cannot be watched. smry reads pages the way an anonymous visitor does. If the interesting part is only visible when signed in, no monitor will see it.
Usually because you asked for a specific change and the page has not made one. A monitor with instructions reports only what matches them. If you want every textual difference — a changed timestamp included — ask your agent for exact detection instead, and expect noise.
At whatever interval you set, with sixty minutes as the shortest allowed and daily as the default. A change detected at 06:14 is in your next catch-up, not a push notification.
Yes, two ways. A sitemap monitor reports URLs added and removed. A site-wide watch described in plain English reports meaningful changes anywhere on the site, and costs ten times as much per check — so put it on a slow schedule.
Yes. Each one occupies a followed-source slot as well as a monitor slot. Unfollowing it frees both and releases its credit reservation immediately.

​
Next

Watch a page for changes

Target types, detection modes, and schedules in full.

Keep up without the feed reader

Read change events in the same catch-up as everything else.

Every tool your agent gets

The catalogue behind these prompts.
Last modified on September 13, 2026