Deal sheet
Underwrite before the offer
Characteristics, recorded sales, tax, and a reference value arrive with the address, so the first pass starts from the record instead of a records request.
Characteristics, recorded sales, tax and assessments, zoning, acreage, and owner of record for any U.S. address. One schema from first look to closing.
Investors underwrite it, developers build on it, and agents sell it. Every deal starts from the same recorded property.
Deal sheet
Characteristics, recorded sales, tax, and a reference value arrive with the address, so the first pass starts from the record instead of a records request.
Comparable sales
Comparable sales come from recorded deeds, with the sale price, sale date, and property facts behind each one, so a number arrives with its evidence.
Site assembly
Map neighboring parcels from their boundaries, with the owner of record on each parcel, so a multi-parcel acquisition starts organized.
Acreage, zoning, land use, and lot dimensions show what the land can hold before anyone pays for a survey or a zoning review.
Square footage, lot size, year built, tax, and sale history for any address, so a seller presentation or buyer brief starts from the public record.
Assessed values, tax amounts, and the tax year come from the county roll, so carrying costs and assessment appeals start from the figures the county bills on.
Every field comes from the three offices that keep a property's official record, assembled into one record per parcel and kept in the same schema in every county.
Building size, rooms, year built, assessed values, and tax, from the roll the county uses to bill the property.
Deeds and transfers with recorded prices and dates, plus the owner of record, filed each time the property changes hands.
Parcel boundaries, acreage, and zoning, from the maps the county uses to define each parcel.
And every team that works from the record
Every field below belongs to the same normalized property record, keyed by address or parcel ID. Field names link to the schema reference, and the v3 schema carries each parcel's recorded sales and transfers, with prior sales where the county publishes them.
Size, rooms, age, and the features a buyer asks about.
Recorded prices, assessed values, tax, and the estimate.
What the parcel is, how big it is, and what it is zoned for.
Owner of record and the recorded trail behind each sale.
Same data and same schema on every path.
Real-time
View APILookups by address or parcel ID and comparable sales around a property, with ~20 ms average latency per request.
At scale
Explore bulkState or nationwide datasets delivered to AWS, Google Cloud, or Azure for market screens, site selection, and portfolio analytics.
In your assistant
For agentsGive the assistant that drafts deal memos or buyer briefs the same property record through MCP, the Realie CLI, or plain REST.
Realie collects property data directly from roughly 3,000 county assessor, recorder, and GIS offices, normalizes it into one schema, and serves it with ~20 ms average latency across endpoints. The same record sits behind every underwriting pass, every comp, and every client brief, whether you work one market or buy across the country.
Assessor, recorder, and GIS records collected at the source, not relicensed from an aggregator.
The same field names and types in every county, so a buy box built for one market runs in the next.
Records refresh from public county sources on a rolling, per-county cycle, so vintage varies by county and every record carries its own dates.
Start free, then $50, $150, or $350 a month with the same endpoints on every tier. Bulk and enterprise are licensed separately.
The modelValue estimate and the comparable sales behind it are a starting point for underwriting and pricing, never a substitute for an appraisal.
The record describes the property, not the person. Realie is not a consumer reporting agency, and its Terms of Use prohibit using the data as a factor in an individual's eligibility for credit, insurance, employment, or housing, including tenant screening, or for any other FCRA-regulated purpose.
Answer-first reading on the data behind these workflows.
Which fields a deal runs on, where the data comes from, and how to access it.
Where county-level records live and how to access them.
Pulling recorded transfers and prices for a parcel.
Where automated valuations come from and how to read them.
Sourcing assessed values and tax amounts across counties.
Where acreage, frontage, and lot dimensions come from.
Start free on the API, or talk to us about bulk delivery for market-wide screens and portfolio analytics.