Site screen
Find sites for large loads
Screen parcels for the acreage and zoning a data center campus, charging hub, or industrial plant needs, then test them against your capacity plan.
Parcel boundaries, acreage, zoning, land use, building facts, and owner of record across roughly 3,000 counties. One schema for siting, routing, load planning, and service requests.
Utilities plan around the buildings they serve. Developers plan around the land. Both work from the same parcel record.
Site screen
Screen parcels for the acreage and zoning a data center campus, charging hub, or industrial plant needs, then test them against your capacity plan.
Corridor routing
Trace a corridor across the parcel layer to list every parcel it crosses, with parcel IDs and legal descriptions for the right-of-way file.
Load planning
New construction, unit counts, and recent sales by area show where demand is heading, so capacity plans follow the housing stock.
Building size, age, stories, and heating fuel where the county records it give load forecasts recorded inputs instead of survey answers.
Roof, building size, and year built across a program area show which buildings merit a closer look for rooftop solar or efficiency upgrades.
New connection requests arrive with the size, units, and structure of the property attached, so engineers scope the service without a questionnaire.
Boundaries, frontage, and parcel IDs ride along on the work order, so every crew knows exactly which parcel it is working on before leaving the yard.
Realie doesn't map substations, interconnection queues, or hazard zones, and doesn't try to. It supplies the parcel layer those models sit on: boundary, acreage, zoning, land use, and owner of record, keyed by parcel ID so it joins cleanly to the layers you already maintain.
Filter a state of parcels by acreage, zoning, and land use, then overlay your own grid and interconnection layers to build the shortlist.
Owner of record, recorded transfers, and legal descriptions give land teams the facts behind lease, option, and easement work.
And every team that starts with a parcel
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 county land-use codes and heating fuel where the county records it.
Where the land is and how much of it there is.
What the land is zoned for and how it is used today.
The building facts load and service planning start from.
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, plus location search within up to two miles of a point, with ~20 ms average latency per request.
At scale
Explore bulkState or nationwide parcel datasets delivered to AWS, Google Cloud, or Azure, ready to load into GIS for screening and corridor work.
In your assistant
For agentsGive the assistant that drafts site memos or answers service questions the same parcel 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 parcel record sits behind every site screen, every route, and every service request, whether you plan for one service territory or projects in every state.
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 screening model built for one state 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.
Realie returns recorded land and building facts. It does not model interconnection, capacity, hazard, or energy use.
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 energy work runs on, where the data comes from, and how to access it.
Parcel geometry, and how it differs from the assessor record.
Where acreage, frontage, and lot dimensions come from.
Sourcing zoning and land-use codes across jurisdictions.
What a state or national bulk delivery contains.
How refresh cycles work and what a record's dates mean.
Start free on the API, or talk to us about bulk delivery for state-wide siting and planning.