Snag Watcher

Guides

Conditions

This fires when the item is in stock at $120 or less:

JSON
"conditions": { "all": [
  { "field": "availability", "op": "=", "value": "in_stock" },
  { "field": "price", "op": "<=", "value": 120 }
] }

Put up to 10 conditions under all (every one has to hold) or any (one is enough). A field the page doesn't show reads unknown, and unknown never passes. Nothing is guessed for a blocked site.

Fields

fieldValues
priceDollars (120), "$119.99", or an exact amount like "$0.0137"
price_dropDown by "10%" or "$20". Needs compare_to
price_changeUp (positive) or down (negative) by "0.5%" or "-$2". Needs compare_to
price_moveEither way by "0.5%". Needs compare_to
kindproduct, listing, slot, ticket, fare, quote, release, post, record, region, document or profile
availabilityin_stock, low_stock, out_of_stock, back_in_stock, open_slot, closed
quantityHow many are in stock, if the site shows it
versionA number. Needs match: line or category
release_statusrumored, announced, preorder, available, sold_out. rumored comes only from news, never a store page
release_date, date, opens_at"2026-12-15" or a datetime
seller, or any attributeText or a number
text, text_hash, length, containsOn a page change or a document: the first 2,000 characters, a hash that changes with the text, the length in characters, and true when every phrase in target.attributes.contains is there
itemsThe whole list, for added and removed
itemThe whole result, for judge

in_stock includes low stock. low_stock is only low stock: 3 or fewer left, or the site marks it low (like Nike's low level) without showing more than 3. For slots, open_slot means in_stock and closed means out_of_stock. back_in_stock is true once, on the check where a variant goes from out of stock to buyable.

A document result is a policy, regulation or PDF that has versions, and { "field": "text_hash", "op": "changed" } fires on a new version. A profile result is a repo, a company or a business listing whose numbers change. Every condition works on both. Page changes have more fields, listed under Page changes.

Operators

opTrue when
=, !=, <, <=, >, >=The field compares that way with value
in, not_inThe field is, or isn't, in the value list
existsThe field has a value
changedThe field differs from the last check
added, removedWith field items: something joined or left the list
judgeAn LLM decides the rule you wrote in value holds

compare_to

Compare with an earlier check of the same variant on the same site instead of a fixed value:

JSON
{ "field": "price_drop", "op": ">=", "value": "10%", "compare_to": "first_snapshot" }
{ "field": "price", "op": "<", "compare_to": "last_snapshot" }
{ "field": "price", "op": "<=", "value": "$20", "compare_to": "first_snapshot" }

The last one is true once the price is at least $20 under the first price.

compare_to is first_snapshot, last_snapshot or window. It works on any number, like a price, a quantity or a site's rank or count. Other fields only take it with changed. With a value it means "by at least", so { "field": "rank", "op": "<=", "value": 10, "compare_to": "first_snapshot" } means the rank is up 10 places or more. A percentage like "10%" needs compare_to, and so do price_drop, price_change and price_move.

window

compare_to: "window" compares with the oldest check inside window, to catch moves over a stretch of time. Set every shorter than the window so there are checks to compare with.

JSON
{ "field": "price_move", "op": ">=", "value": "0.5%", "compare_to": "window", "window": "10m" }

That fires when the price has moved 0.5% or more either way from where it was 10 minutes ago.

Numbers, text and dates

Prices are exact, so a token at $0.0137 is compared as 0.0137, not rounded to a cent, and results carry price.amount and price.cents. A plain number on a price field is dollars. Numbers are compared to 12 significant digits, so 0.1 + 0.2 equals 0.3. Text is compared without case, so "Nike" equals "nike". Against a plain date, <= and > read it as the end of that day, so <= "2026-12-15" includes all of the 15th.

over

over asks about a set, like every size you listed, instead of one variant. This fires when all the sizes are in stock from the same seller:

JSON
{ "field": "availability", "op": "=", "value": "in_stock",
  "over": { "key": "sizes", "require": "all", "same": "seller" } }
KeyValues come fromNeeds
sizesattributes.sizetarget.attributes.size as a list, like [10, 10.5]
datesEvery dated slot foundA listing target, or a date range (from, to) in target.attributes
itemsEvery product the match foundmatch: line, category or listing

require is all, any, or min_n with n. Set same to site or seller when the set has to come from one place. seller needs two or more sites, or a site with several sellers.

Lists: added and removed

JSON
{ "field": "items", "op": "added" }
{ "field": "items", "op": "removed" }

added is true for a result that wasn't on the site at the last check. removed is true for one that was there and isn't now. It's reported as it looked when last seen, since the site no longer lists it.

They work for any list a site shows, like a sanctions list, an exchange's trading pairs or a store's new arrivals. Under all, putting { "field": "country", "op": "=", "value": "IR" } next to added reports only additions from Iran.

The first read is the starting list, so nothing is added on it. Only full reads count, so a blocked or unreachable check removes nothing. A list that held 3 or more items last time and reads empty now is treated as a bad read, but one that drops from 1 or 2 items to none counts as removals. If only the first page of a long list can be read, items that fall off that page show up as removed, so watch a page that shows the whole list. Each change is news only once, so it goes out even in the cooldown. matched and changed events carry added and removed, each a list of results. added and removed already compare with the last check, so leave out compare_to, window and over.

Judged conditions

JSON
{ "field": "text", "op": "judge", "value": "a plan's price went up, or a plan was removed" }

An LLM reads the result as it was at the last check and as it is now, and decides whether your rule holds. field is what it reads: item for the whole result, or one field like a page change's text. It's only asked when that field changed since the last check, so the condition is false when it didn't, and unknown on a site's first read. The same change is never judged twice.

A request can have up to 3 judged conditions of up to 300 characters each. They share 20 judged checks a day (UTC), with at most 10 in one check. Past that limit, or while the server's budget for the judge, or your account's monthly one, is used up, a condition that couldn't be asked reads unknown. A change that wasn't judged is kept and judged on a later check, oldest first, and the condition reads unknown until then. Up to 20 can wait, for up to 7 days, and if a result changes again, its new change is judged instead. A late verdict counts on the check where it's answered, so it fires then if your other conditions also hold.

Don't pair the judge with changed conditions. It only asks when the text changed anyway, and a late verdict can't fire on a check where nothing changed. Put simple conditions like kind = document next to it under all, so only results that pass them get judged.

text on a page or document carries its first 2,000 characters, but for a page change or a PDF the judge reads change_excerpt instead: the lines that changed since the last check, with one unchanged line either side, up to 3,000 characters, so a change on page 30 of a long document still gets judged. On other sites where the text is cut off, a change past the first 2,000 characters reads unknown, so judge a narrower region with selector there.

Events carry judged: [{ site, url, rule, reason }]. Previews don't call the judge, so judged conditions read unknown there. A server without an LLM refuses judged conditions with judge_unavailable.

Page changes

A page-change watch gives one result of kind region (part of a page) or document (a PDF), or one record per item with list. Conditions can use these fields:

Field
text_hashA hash of the region's text after noise is removed. { "field": "text_hash", "op": "changed" } fires when the text changes
containstrue when every phrase in target.attributes.contains is there, as whole words
contains_anytrue when at least one of them is
contains_<phrase>One per phrase, with the words joined by _, like contains_sold_out for "sold out"
lengthCharacters in the region. { "field": "length", "op": "<", "value": 500, "compare_to": "last_snapshot" } catches a page that lost 500 or more characters
foundfalse when selector matched nothing or the region has no text, once it has matched before (see elements)
elementsHow many elements selector matched. A selector that matches nothing on the first read fails the check with selector_not_found and suggests close selectors that do match. After it has matched once, it reports 0 instead of an error, so you can watch for a button to go away. To wait for one to appear, watch a larger region with contains
textThe first 2,000 characters, for the webhook
change_excerptThe lines that changed since the last run, with one line of context either side, up to 3,000 characters. The judge reads this
final_urlWhere the page redirected to, if it did
previous_hashThe hash before the latest change. Empty on the first read
version_seen_atWhen the current text was first seen
last_changeWhat changed last time, as a short line like changed "Rev. October 2018" to "Rev. March 2024"; added "...", up to 1,000 characters
last_change_added, last_change_removed, last_change_changedParagraphs added, removed and changed
last_change_summaryA one- or two-sentence summary of that change, with summarize: true
pages, pdf_title, pdf_created, pdf_modifiedFor PDFs
position, href, dateFor list items, with list
page_title, meta_description, canonical, meta_robots, noindex, h1, h1_count, lang, script_hosts, script_count, seo_hashWith seo: true. { "field": "noindex", "op": "=", "value": true } catches a page dropped from search, and { "field": "seo_hash", "op": "changed" } catches a new tag or script host

Put the phrases in target.attributes.contains and test for them with { "field": "contains", "op": "=", "value": true }.

Several sites

With several sites, where.aggregate decides what one notification covers:

aggregateSends
eachOne result per site (the default)
bestThe lowest price across sites, or the earliest date
firstThe first site to match, then the watcher stops
dedupeOne result per product, with every site's offer

Kind

The watcher's kind comes from the conditions that watch for a change: price, availability, release, or mixed when there's more than one of those. A fixed cap like price <= 180 only filters results, so it doesn't make a release watcher mixed.

In the examples