Deed records and county recorder data, structured for use
Every transfer of real property leaves a recorded document behind. Deed records are the canonical account of who conveyed what to whom, on what date, for what stated consideration. The trouble is where they live: county recorder offices across the country, each with its own document types, indexing conventions, and idea of what a searchable field is. County recorder data is public, but it is not usable in the form it is published.
Recordpipe builds and runs the pipeline that turns recorded documents data into one schema. Warranty deeds, quitclaims, trustee's deeds, deeds in lieu, corrective deeds — each arrives with its instrument number, recording date, parties, and parcel linkage, normalized across every county in your footprint. Your team reads one table, not a different format per county.
We deliver the record as recorded. Document type is preserved from the source, not guessed. Where a county publishes a stated consideration or transfer tax, it comes through; where it does not, the field is null rather than estimated. The instrument number is your verification path back to the source, on every row.
Deed transfer data and grantor grantee data: reading the transaction
A deed transfer is a signal, and the parties on it are most of the signal. Deed transfer data from Recordpipe carries grantor and grantee as they appear on the instrument, plus the document type that tells you what kind of transfer it was. An arm's-length sale, a transfer into a trust, a quitclaim between family members, and a trustee's deed after foreclosure all look alike in a raw index. They mean very different things to an acquisitions desk, a title plant, or a lender's portfolio team.
Grantor grantee data is also how entities get tracked. An LLC buying across several counties shows up as a grantee in each recorder's index, but nobody joins those indexes for you. A pipeline that normalizes party names and delivers them alongside parcel identifiers lets your team see the pattern in one query, with the county's original spelling kept beside the normalized name.
To be clear about what this is: names on a public instrument, exactly as recorded. Not a people-search product, not skip tracing, no scraped private contact data. Mailing addresses come through when the instrument states them. Enrichment beyond the record is your call.
Easement records and chain of title data
Deeds are the headline instruments, but the recorder's index holds everything else that runs with the land. Easement records — utility, access, drainage, conservation — attach to a parcel and stay attached through every subsequent sale. Restrictive covenants, rights of first refusal, affidavits, and corrective instruments sit in the same index. If your work depends on knowing what encumbers a parcel, the deed alone is not enough.
Chain of title data is the ordered version of that index: every recorded instrument on a parcel, in recording order, linked by the references the documents themselves carry. Recordpipe delivers it as a per-parcel history, not a pile of unlinked rows. Each instrument points to the one it amends, releases, or follows, wherever the county's index makes that link available.
What we do not do is render a title opinion. The chain is the public record, structured, with gaps marked where a county's index has gaps. Examiners, underwriters, and analysts make the judgment calls. We make sure the record they are judging is complete, current, and traceable to its source.
Property records API, files, or webhooks — on your cadence
Deed data is only worth what your team can do with it, and that depends on how it arrives. Recordpipe delivers through whichever channel fits the workflow: a property records API your application queries directly, flat files dropped to your storage, webhooks that fire when a new instrument records against a parcel you watch, or a dashboard for teams that just need to look. One-time backfills and ongoing daily or weekly feeds use the same schema.
The AI analysis layer sits between the recorder and your inbox. It dedupes re-indexed instruments, flags the document types you asked for, joins recorded parties to parcel and assessor data, and ranks new activity by the criteria you set in scoping — a sale above a consideration threshold, a transfer into an entity, a trustee's deed in a target area.
Engagement is simple. Submit the intake form and we reply within 2 business days. The $500 scoping returns a feasibility read, a sample from your actual counties, and a fixed quote within 5 business days, credited against the contract. Contracts are fixed-price from $5,000, running on infrastructure that already processes over one million public records nightly.
What a delivery looks like
| Field | Description |
|---|---|
| instrument_number | The recorder's own document identifier — your verification path back to the source. |
| document_type | Warranty deed, quitclaim, trustee's deed, easement, covenant, or other instrument as the county classifies it. |
| recording_date | Date the instrument was recorded by the county. |
| grantor | Conveying party as named on the instrument, with a normalized form beside the original spelling. |
| grantee | Receiving party as named on the instrument, normalized the same way. |
| parcel_id | Assessor parcel number, joined from county records where the index links one. |
| property_address | Situs address of the affected parcel, standardized. |
| consideration_amount | Stated consideration or transfer-tax-derived value where the county publishes it; null otherwise. |
| related_instrument | Instrument this document amends, releases, or follows, where the index carries the reference. |
| first_seen_at | When the instrument entered your feed — your audit trail on freshness. |