Monitor new listings and price changes for an iBuyer buy-box

Steps

1. Establish an incremental replication pipeline against a RESO Web API source (MLS Grid, Trestle, or Spark) using ModificationTimestamp as your watermark, running on a frequent schedule (e.g., every 5 minutes)
2. On each incremental pull, classify each changed record as: new listing, price reduction, status change (e.g., Active to Pending), or back-on-market by comparing incoming data to your local snapshot
3. Apply your buy-box filter in code against each new or changed record: property type, bedrooms, bathrooms, square footage range, year built, geography (polygon or radius), and list price range
4. For matching records, enqueue an evaluation job with the full listing payload; the job triggers AVM lookup, comparables pull, and offer calculation
5. Emit a structured alert event (webhook, queue message, or database insert) for downstream systems when a buy-box match is found, including the listing key, match timestamp, and matched criteria
6. Track price change history by storing each snapshot of ListPrice alongside its ModificationTimestamp so you can compute days-on-market, price reduction count, and reduction percentage