PRMMonitor

PRM listing monitor: attach real-estate ad URLs to parcels in the caller's PRM pipeline, list them, stop monitoring. Report-driven: the server never fetches a listing page. Registering a URL again is an observation (status, price, content hash) that can emit listing events.

Errors use { "error": { "code", "message" } } and every response carries Cache-Control: private, no-store. A malformed JSON body answers 400 invalid_request and a body over the size cap 413 payload_too_large, both before authentication. After authentication, an unknown path under /res_api/prm_monitor answers 404 not_found.