4 ms·
As a California RE brokerage we join each MLS and get a direct feed from their RETS api. It's a dramatically better data feed than any of the aggregators offer
by rgbrgb 11y ago
As a California RE brokerage we join each MLS and get a direct feed from their RETS api. It's a dramatically better data feed than any of the aggregators offer and we get listings the minute they come on market (well our polling interval is more like 5 minutes). So far we have 100% coverage in San Francisco, Oakland/East Bay, Silicon Valley, and Los Angeles. We've just joined the San Diego MLS and will have data there soon. And yes, our strategy is to go deep on California, prioritizing data quality over sheer number of listings.
- JoshTriplett 11y agoAny plans to expand to other states?
- rgbrgb 11y agoDefinitely but I can't give you a date. California is a huge diverse market though and we think it's an amazing place to prove out the model and build our offer/transaction system. So we're trying to go really deep here before expanding out.
- encoderer 11y agoYou should check out https://rets.ly/ https://rets.ly/
- rgbrgb 11y agoBeen on their beta list for almost a year. They've since been acquired by zillow so we're not holding our breath.
- encoderer 11y agoMy understanding is that they are working hard to build APIs that will let Retsly power the next zillow, and that there's support for that internally. Time will tell!
- rgbrgb 11y agoCool, if that's the case I hope the API is available soon. In the meantime our internal implementation makes use of this great open source library from estately: https://github.com/estately/rets https://github.com/estately/rets
- ppohler 11y agoNice service! What are the vendor fees associated for the MLSs? Did you go to CRMLS and did you run into a requirement where you had to have a brokerage signed on previously? Running into MLS/vendor issues at my own real estate tech product.