Data for proptech & real estate platforms
The data layer under your product.
Platforms need a stable parcel key, national coverage, daily change and an API with sane terms. We supply the property, listing, rental, valuation, license and owner-contact layers, and we do not compete with your product.
Because we are a boutique, licensing is negotiable and support is a phone call. Clients embed our license API, run our valuations behind their own UI, and load our assessor and transaction files into their warehouses under terms written for a product, not a marketing list.
Plays that work
| Play | Data behind it |
|---|---|
| Agent directory or CRM Every licensed agent with brokerage, status and contact, monthly | Real Estate License Data + Professional Graph |
| Home value features AVM and comps behind your consumer or agent UI | Home Valuations + Comparable Sales API |
| Market data Listings, rentals and ZIP intelligence for dashboards | On-Market Listing Signals + For-Rent Listings + Neighborhood Intelligence |
| Owner outreach Skip-trace and owner contact inside your product | Property Owner Contact + Identity Resolution |
How a project runs
- Send the briefAudience, geography, must-have fields, refresh cadence and how you want to receive it. A paragraph is enough. We reply within one business day, usually with questions and a rough count.
- Get a sample and a match reportFor appends we run a slice of your own file and report the match rate field by field. For lists we send sample rows for your geography. Both are free.
- Agree terms and take the first deliveryPer matched record, flat license or subscription, sized to the pull. The first file arrives with a data dictionary and fill rates.
- Refresh on a scheduleMost programs become a standing monthly or weekly delivery. Deltas are flagged so you only process what changed.
Compliance
Public-record data may be displayed subject to state-level restrictions that we document per dataset. Personal contact data is licensed for permitted uses only and cannot be redistributed as a standalone list.
Questions we get
What key do the files share?
One parcel identifier across assessor, recorder, mortgage, permit, listing and valuation files, one person key across consumer and contact files, and one company key across the professional graph. Keys are stable between refreshes.
Can we display the data inside our product?
Yes. Product licenses are written for display and derived use, not just internal analysis, and they say so explicitly. Tell us the surface and the expected volume and the terms follow.
Is there an API?
License lookup, valuation, comparable sales, identity resolution and phone verification run behind keyed endpoints with OpenAPI docs. Everything else ships as bulk files to S3, SFTP or a signed link, with daily deltas where the source changes daily.
Do you compete with our product?
No. We sell data and appends. We do not run a consumer or agent-facing product.