Find the lots worth splitting — before anyone else does.
Private workspace · invited members only
A verification worklist — these are candidates only, never confirmed. Each is a single-family lot big enough to possibly subdivide, priced like an ordinary home. Open any card for photos, parcel facts, map & flood links, a verification checklist, and notes. Always verify zoning, frontage, Pinelands/wetlands, and the board's subdivision rules before acting.
Run the Ocean County sweep and parcels worth a second look will appear here.
loading…
How candidates narrow from found to confirmed-good.
Where the splits are. ✓ = verified zone · ★ = marked good.
Extra conforming lots each candidate could yield.
Asking price of current candidates.
How each district was resolved.
Wetlands / flood hits to verify.
checking…
Run the scraper and listings will appear here with photos, scores, and the AI's reasoning.
Where the brain hunts, and what counts as a deal in each.
Tell the AI what makes a great deal, what to look for, and what isn't — in plain English. It reads all of this on every listing. Numbers beat adjectives.
Rules the brain learned from your feedback — applied to every future score.
Only a score ≥ this fires a Telegram alert. Higher = pickier.
Which funnel runs first each cycle. Takes effect next cycle — no restart.
Controls the warm-session re-sweep loop without restarting the bot (the PerimeterX solve is kept). Applies next cycle.
Pull the Zestimate from search results and skip the per-listing detail-page loads — far less PerimeterX exposure. Tradeoff: no listing description or photos, and listings with no Zestimate in search results are skipped. Off by default.
Before moving to a NEW town (the main challenge trigger), wait until you mark yourself available — so it never advances into a challenge you can't solve and sits idle. Off by default.
Turn ON when you're around — the sweep advances town-to-town. Turn OFF (e.g., overnight) and it finishes the current town, then parks until you're back. Only matters when the gate above is enabled.
Each person gets a role; the role decides what they can see and do (configure roles on the Roles tab). Change anyone's role from the dropdown beside their name. Usernames are case-insensitive; passwords are stored salted + hashed.
Failed attempts show in red — a burst of ✗ rows from one IP is a brute-force attempt.
Create roles and choose exactly which pages each one can view and edit. Admin always has full access. Assign roles to people on the Users tab.
Requires your current password. Every other signed-in session is signed out after the change.
Your reason becomes a permanent rule for future scoring.