Deed records from every county you cover, in one schema.
Every property transfer, easement, and recorded instrument lives in a county recorder's index, and every county indexes it differently. Recordpipe collects deed records across your counties, normalizes parties, instrument types, and legal descriptions into one schema, and delivers deed data as a backfile, a daily feed, or an API.
Deed transfers and recorded documents
Instrument type, recording date, document number, grantor and grantee as recorded.
Easement and chain of title data
Easements, releases, and prior transfers linked by parcel for title and diligence work.
Parcel-joined
Recorder data joined to assessor parcel data so every instrument resolves to a property.
Backfile plus cadence
Years of history as one dataset, then daily or weekly deltas.
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. |
In the field.
Title and escrow operations: the index in one place
A title agency can pull every recorded instrument on a parcel — deeds, easements, covenants, corrective filings — as one ordered history the moment an order opens, across every county it works. Examiners start from a structured chain of title instead of rebuilding it by hand, and the instrument numbers let them verify any row at the source.
Acquisitions teams: entity buying patterns
An acquisitions team can watch deed transfer data for the entities buying in its markets — which LLCs and funds are taking title, in which counties, at what stated consideration. Normalized grantee names turn a scatter of county indexes into a single view of who is accumulating what, refreshed daily.
Right-of-way and land teams: easements before the survey
A utility or renewable developer's land team can screen candidate parcels for recorded easement records and covenants before spending on surveys and outreach. Per-parcel instrument history shows what already runs with the land, so the team prices and prioritizes with the encumbrances in view.
Lenders and servicers: transfers on collateral
A servicing team can get a webhook the day a deed records against a property in its portfolio — a sale, a transfer into a trust, a quitclaim. It is raw public data for portfolio monitoring, not a consumer report; anything touching a borrower's eligibility gets compliance review at intake.
Recorded documents data for title, proptech, lenders, and analysts
Fixed-price from $5,000 for ongoing feeds; single-county backfiles are a real order. Scoping is $500, credited, with a sample from your counties in 5 business days.