Building size, roof material, heating and cooling, lot dimensions, and year built for any U.S. address. One schema and one API, from the first estimate to the next territory.
From the first inbound request to the crew's work order, every step runs on the same property record.
Square footage, roof, systems, and lot size come with the address. The first number you give is one you can stand behind.
Every inbound request arrives with the facts of the home attached. Reps skip the guesswork and get straight to scoping the job.
Know how many homes in any area fit the work you do, by age, construction, pool, or lot size, before committing crews or budget.
Housing mix and recent sales activity by area show where work is coming. Plan routes and crews ahead of the season, not behind it.
Lot dimensions, building size, and systems ride along on the work order. Estimates hold up on site, and visits are sized right.
Unit counts, zoning, and land area separate single-family work from multifamily and commercial. Bids land with the team built for them.
Take a two-story home built in 1994 on a third of an acre. The same record answers a different question for every crew that pulls up to it.
Two stories, a hip roof in composition shingle, and 2,100 square feet of building area. Enough to size the tear-off and the materials before the ladder comes off the truck.
Forced-air gas heat, central air, and 2,100 square feet over two floors in a 1994 build. The replacement conversation starts at the right tonnage.
A third of an acre, 90 feet of frontage, and a pool out back. Fencing, irrigation, and a deck get priced from the lot, not a drive-by.
And every other trade that starts with an address
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 adds heating, cooling, and utilities.
Construction, roof, foundation, and the heating, cooling, and utility systems on file.
The dimensions that drive materials and labor.
Acreage, frontage, and outdoor features for exterior work.
Owner of record and the last recorded sale, so customer files stay accurate.
Same data and same schema on every path.
REST endpoints for address, parcel ID, and location lookups inside estimating, CRM, and scheduling tools, averaging about 10 ms per request.
State or nationwide datasets delivered to AWS, Google Cloud, or Azure for territory analysis and demand planning in your own warehouse.
Give the AI assistant that takes calls or drafts estimates 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 in about 10 milliseconds. The same trusted facts sit behind every quote, every route, and every expansion decision, whether you run one truck or a national brand.
Assessor, recorder, and GIS records collected at the source, not relicensed from an aggregator.
The same field names and types in every county, so an estimating tool works the same in every market you expand into.
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.
About 10 ms per request keeps estimate forms and call-center lookups fast, and bulk transfers cover territory-wide analysis.
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, or for any other FCRA-regulated purpose.
Answer-first reading on the data behind these workflows.
Which fields drive an estimate, where the data comes from, and how to access it.
Sourcing structure, materials, and size fields across counties.
Where acreage, frontage, and lot dimensions come from.
Owner of record and how it is keyed to the parcel.
Pulling recorded transfers and prices for a parcel.
How refresh cycles work and what a record's dates mean.
Start free on the API, or talk to us about bulk delivery for territory-wide planning.