Bulk real estate data licensing.
The whole population as a file, not a seat that lets you look records up. Assessor, recorder, mortgage, permit, listing, valuation and license data delivered to your bucket or warehouse on a schedule, under terms written for the way you will use it.
What bulk licensing means here
A bulk license gives you the data itself. Every row for a geography or the country, in a format your engineers already handle, refreshed on a cadence, with a data dictionary and fill rates so nobody has to guess what a column means. It is the right shape for a product, a warehouse, a model or a research panel. It is the wrong shape for someone who wants to look up one address a day, and we say so on the pricing page.
Most requests we see for bulk real estate data come from three places: proptech teams building a property or agent product, analytics and insurance teams that need the national file in a warehouse, and AI teams that need training data with provenance. The files are the same; the terms differ.
What is in the files
| File | What it carries | Cadence |
|---|---|---|
| Assessor and recorder | Parcel, owner, mailing address, land use, structure characteristics, assessed and market values, last sale, legal description | Monthly |
| Transactions | Every recorded deed with price, date, buyer, seller, document type and financing | Monthly, weekly on request |
| Mortgages and HELOCs | Open and historical liens with amount, lender, type, term and recording date | Monthly |
| Permits and contractors | Permits by parcel with type, value, dates and the contractor of record | Monthly |
| Listings and rentals | Active, new, sold, expired and withdrawn listings; for-rent listings | Daily deltas |
| Valuations | AVM estimate, range, confidence and comparable sales for every home | Weekly |
| Licenses | Every licensed agent and broker in the US and Canada with matched contact | Monthly |
| ZIP intelligence | Values, rents, demographics, schools and housing stock per ZIP | Monthly |
All property files share one parcel identifier, so a deed joins to its parcel, its mortgage, its permits and its listing history without address matching. Owner names carry a person key that joins to consumer and contact data where your license permits it.
How delivery works
- Scope the cut National or by state, county, metro or ZIP list. Full files or a column subset. We confirm the row count and the fill rate of the fields you care about before terms.
- Pick a format and a destination CSV, JSON, NDJSON or Parquet, compressed, with manifests and checksums. Delivered to your S3 or GCS bucket, our SFTP, a Snowflake or Databricks share, or a signed link.
- Take the first full load The complete file plus a data dictionary listing every field, its source and its fill rate on your cut.
- Receive deltas on the schedule Monthly for record files, daily for listings, weekly for valuations. Deltas carry the change type, so your pipeline processes only what moved.
How a bulk license is priced
Bulk data is priced as a flat annual license or a subscription, sized to the geography, the fields and the use. A single-state assessor file for internal analytics costs less than the national file displayed inside a consumer product, because the second is worth more and carries more obligations. There is no per-seat fee and no platform fee. The four pricing models are explained in plain terms, and the scoping conversation is free.
What moves the number: geography, number of files, whether personal contact fields are included, whether the data will be displayed or redistributed, and the refresh cadence. What does not: the number of people on your team who touch it.
Terms written for the use
Internal analytics, product display, model training and resale are different uses and get different clauses. We write the permitted use into the agreement rather than selling a generic license and hoping. Public-record data can be displayed subject to a short list of state restrictions that we document. Personal contact data is licensed for permitted uses and cannot be re-sold as a standalone list. AI training is a named permitted use on the training data package.
Bulk versus API
If your team needs the population, take the file. If it needs the answer for one record at a time inside a user flow, take the API. Most clients end up with both: the bulk file in the warehouse and an API key for the live lookups. The trade-off is laid out here.
Who this is for
- Proptech and real estate platforms building on a stable parcel key
- Insurers and lenders loading the national file into a warehouse
- AI teams training valuation, extraction and assistant models
- Research teams that need point-in-time history plus a live feed
- Agencies and data teams that would otherwise stitch county files together themselves, which we have a view on