Assessor data and parcel data, normalized across every county.
Assessor rolls are the backbone of every property dataset: who owns each parcel, where they get their mail, what the property is, and what it is assessed at. Recordpipe collects tax assessor data across your counties, standardizes owner names, addresses, and characteristics, and delivers parcel data in bulk or behind an API built to your schema.
Parcel owner data
Owner of record and mailing address as the assessor publishes them, standardized.
Assessed values and property tax records
Values, exemptions, and tax status where published, tracked across roll years.
Property characteristics
Use codes, land and improvement data, and legal descriptions in one field set.
Parcel data API or bulk
Statewide backfiles, county subsets, or a hosted assessor data API with keys and docs.
Assessor data and parcel data, normalized across every county you cover
The assessor's roll is the closest thing the country has to a master list of real property. Every parcel, its owner of record, its situs address, its land use, its assessed values. Parcel data is the spine that every other property dataset joins to — deeds, liens, permits, foreclosures — which is why a bad assessor feed corrupts everything built on top of it.
The problem is the one every county dataset has. Each assessor office publishes on its own schedule, in its own format, with its own field names and its own idea of what a land-use code means. Tax assessor data from neighboring counties can disagree on something as basic as how to write a parcel number.
Recordpipe builds the pipeline that makes assessor data usable: one schema, parcel identifiers standardized, addresses normalized, land-use codes mapped to a common taxonomy while the county's original code is preserved beside it. Your analysts query a single table. The county's own values are always there when someone needs to verify a row at the source.
Parcel owner data and property owner data: what is public, what is not
Owner of record is a public fact. It is the name the assessor carries for the parcel and, where the county publishes it, the mailing address the tax bill goes to. Parcel owner data from Recordpipe delivers exactly that: owner name as the roll states it, mailing address as published, an owner-occupied flag where the county derives one, and the deed reference that last changed ownership.
Property owner data is also where the line has to be drawn clearly. We deliver names and mailing addresses from public filings. We do not deliver phone numbers, personal emails, or anything scraped from private sources. There is no skip tracing and no people-search. If your team wants enrichment beyond the public record, that is your decision to make and your compliance to own.
Entity owners are the interesting part for most teams. LLCs, trusts, REITs, and institutional holders appear as owner names across many parcels and many counties. Normalized owner names and a per-owner parcel roll-up, delivered alongside the raw roll, let a team see a portfolio where the county sees a list.
Property tax records: assessed values, exemptions, and delinquency
Assessed value is only the first number on the roll. Property tax records carry land and improvement values separately, the tax year they apply to, exemption codes — homestead, senior, veteran, agricultural — taxable value after exemptions, and in many counties the levied tax and its payment status. Each is a signal on its own. Together they describe a property's financial posture better than any listing does.
Recordpipe delivers the tax roll as the county publishes it, with year-over-year history where available, so a team can see reassessments, exemption changes, and value trends per parcel rather than a single snapshot. Where a county publishes delinquency status, it comes through as a flag with the tax year it applies to.
Publication varies widely here. Some counties post the full roll with payment status; some post values only; some post on a lag. That variation is exactly what the $500 scoping maps: which of your target counties publish which fields, on what cadence, with a sample of the real data delivered within 5 business days so nobody is surprised after signing.
Parcel data API and assessor data API: how delivery works
A parcel data API is the right shape when your product needs to look up a parcel on demand. A flat file is the right shape when your analysts need a whole county in the warehouse. A webhook is the right shape when your team needs to know the moment the owner of record changes on a parcel it watches. Recordpipe delivers through all of them, plus a dashboard, from the same normalized schema. Pick the channel that fits the workflow; change it later without rebuilding the pipeline.
Cadence is yours as well. A one-time county backfill, a weekly refresh, or a daily delta feed of changed parcels all run on the same infrastructure — the one that already processes over one million public records nightly. The AI analysis layer dedupes across roll versions, flags ownership and value changes, and ranks parcels by the criteria set in scoping.
Getting started is short. Submit the intake form and we reply within 2 business days. The $500 scoping delivers feasibility, a sample, and a fixed quote within 5 business days, credited against a fixed-price contract from $5,000 to $3 million.
What a delivery looks like
| Field | Description |
|---|---|
| parcel_id | Assessor parcel number, standardized across counties with the county's original format preserved. |
| situs_address | Physical address of the parcel, normalized. |
| owner_name | Owner of record as the roll states it, with a normalized form for entity matching. |
| owner_mailing_address | Mailing address as published on the roll — public record, no private enrichment. |
| land_use_code | County land-use or property-class code, plus a mapped common category. |
| assessed_value_land | Assessed land value for the current tax year as published. |
| assessed_value_improvements | Assessed improvement value for the current tax year as published. |
| exemptions | Exemption codes carried on the parcel — homestead, senior, veteran, agricultural — where published. |
| tax_delinquent_flag | Delinquent status and tax year, where the county publishes payment status. |
| last_deed_reference | Instrument number and date of the last recorded ownership change, joined from recorder data. |
In the field.
Insurance carriers: exposure by parcel
A carrier's exposure team can build a parcel-level view of every county it writes in — land use, year built, lot size, improvement value — to model concentration and check book-of-business addresses against the roll. Raw public data for portfolio analysis, not a consumer report; any eligibility use gets compliance review at intake.
Home services and solar: territories from the roll
A solar or roofing company's growth team can cut territories by land use, year built, and owner-occupied status, and mail to owners at the address the roll publishes. No scraped contact data, no skip tracing; the roll is the record, and how the team engages homeowners is its own call.
Planning and engineering consultancies: a multi-county parcel base
A planning consultancy can assemble one consistent parcel base across a region for land-use, housing, and infrastructure studies, instead of reconciling each county's export by hand. Normalized land-use categories and standardized parcel IDs make the regional analysis run on a single schema.
Proptech and valuation products: the parcel spine
A product team can key its property pages and valuation models to a parcel data API that returns owner of record, assessed values, exemptions, and the last deed reference for any parcel in its coverage, refreshed on cadence, with deeds, liens, and permits joined on the same identifier.
Property owner data for proptech, services, lenders, and government contractors
Owner names and mailing addresses are public record; we deliver them as published, with no private contact data appended. Fixed-price from $5,000; scoping is $500, credited.