RealtyPad does not automatically download your local MLS in this version. You still get a lot done with what we have.
This is the usual path for a house a realtor texted you, or something you found off-portal.
Your assistant can search public listing sites (HUD, auction sites, Zillow-style portals, and similar) using tools that are already included — you do not need your own scraping account.
Those searches cost a little money on our side, so we cap spend. Follow each site’s rules. Do not scrape sites that forbid it.
A search card (price, beds, a thumbnail) is a starting point. The assistant should then open the detail page for each house — the same page you would read on Zillow, HUD, or an auction site — and save what is already there.
If you need more than that, you can plug in extra tools (Firecrawl, an MLS connection your board approved, etc.). See About MLS data.
When you add a lead, put in whatever you have — including assumptions you want to model.
When the assistant pulls a listing, it should copy what is already on the page:
The assistant will not invent a missing tax or rent. You can still type your own numbers afterward. Checking tax, rent, and repairs against county records and comps is the later research step.
When you say “update trends,” the assistant should refresh the official catalog (home values, rents, mortgage rates, jobs/building permits, and short-term rental stats where they exist). It should not make up trend numbers. If you have a custom source (for example Redfin), you can store that as an override.
Until we ship a real MLS hookup, use the paths above and About MLS data.