Construction, roof material, year built, square footage, heating and cooling, and parcel geometry for any U.S. address. One schema and one API, from the first application to the portfolio review.
From the application to the claim to the book review, every step runs on the same recorded facts about the structure and the lot.
Year built, square footage, construction, roof material, stories, and heating and cooling arrive with the address. The applicant confirms facts instead of guessing at them.
Parcel identity, building area, stories, roof material, and pool, compared with what the county has on file. Differences surface early, while they're easy to resolve.
Construction type, exterior wall, roof, stories, building area, and year built feed the rebuild-cost tools you already use, straight from the record rather than a form.
At first notice of loss, the adjuster sees the structure, systems, and lot as recorded, so scoping starts before the site visit.
Aggregate construction, roof, age, and parcel geometry across the book by county, city, or map bounds to see where the housing stock is concentrated.
Rolling per-county refresh and recorded transfers show which properties changed since the last term, so renewals and inspections start from current facts.
Replacement cost comes from the estimator your team already uses, and nothing here replaces it. What the property record adds is the inputs it needs, recorded by the county rather than typed from memory: construction, exterior wall, roof material, stories, building area, and year built.
The estimator runs on recorded construction, size, and age instead of the applicant's best guess, so its first output rests on the structure as the county describes it.
The same inputs sit on the claim file, so the adjuster scopes the loss against the structure that was recorded, not the one described on the phone.
Rolling per-county refresh surfaces changes in the recorded structure since the last term, so the estimator reruns on current facts where something moved.
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.
What the building is made of, from foundation to roof.
The scale of the structure and when it was built.
The systems and extras an application asks about.
Where the property sits, down to the parcel polygon.
Same data and same schema on every path.
REST endpoints for address, parcel ID, and location lookups inside application, claims, and policy administration systems, averaging about 10 ms per request.
State or nationwide datasets delivered to AWS, Google Cloud, or Azure for book-of-business analysis in your own warehouse.
Give the assistant that handles intake or claims triage 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 recorded facts sit behind every application, every claim, and every portfolio review, whether you write one state or all fifty.
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 application form works the same in every state you write.
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.
Realie returns recorded property facts. It does not produce risk scores, ratings, or anything about the people who live at the address.
The record describes the property, not the policyholder. 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 insurance or for any other FCRA-regulated purpose.
Answer-first reading on the data behind these workflows.
Which fields describe the structure, where the data comes from, and how to access it.
Sourcing structure, materials, and size fields across counties.
Parcel geometry, and how it differs from the assessor record.
Where zoning codes come from and how to read them.
Which office publishes which facts about a property.
How refresh cycles work and what a record's dates mean.
Start free on the API, or talk to us about bulk delivery for book-wide analysis.