Parcel, characteristics, ownership, sales, tax, valuation, and geometry for any U.S. address. One schema and one API for search products, maps, analytics, and AI assistants, on plans that start free.
Search, maps, enrichment, analytics, or an assistant that answers property questions. Every feature runs on the same record.
Address, parcel ID, and map-bounds endpoints return the full record in about 10 ms, so property search never makes the user wait.
Parcel polygons and coordinates for 180M+ addresses, ready to draw on a map or run through a spatial query, all from one schema.
Append characteristics, sales history, tax, and valuation to the addresses in your own database, keyed by parcel so the join holds across counties.
Typed, parcel-keyed JSON with recorded dates gives assistants and agents facts to cite rather than priors to guess from. Serve it live over MCP or REST, and score your evals against the same record.
Bulk NDJSON for every parcel gives you the text to embed and the fields to filter on. Key each vector by parcel ID, filter by county, year built, or zoning, and refresh the index when the county record does.
Ship a value and the comparable sales behind it. The modelValue estimate and the comparables endpoint come with the same API key as everything else.
Most property data is priced for companies that already have a data budget. Realie is priced for the ones building one, and it scales with them without changing the integration.
Start free with the same endpoints, fields, and schema as every paid plan. A weekend build hits the real API, not a sandbox.
Move to $50, $150, or $350 a month as usage grows, with one token allowance across platform and API and the same response time in every county you add.
Take state or nationwide datasets into your own cloud on enterprise terms for feature pipelines, backtests, and indexes, with no aggregator markups and the same schema you started on.
And every platform 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.
The keys and coordinates every feature joins on.
Size, rooms, age, and the amenities a listing shows.
Recorded transfers, assessed values, and the estimate.
Owner of record and the document trail behind each sale.
Same data and same schema on every path.
REST endpoints for address, parcel ID, location, and comparables lookups inside search, listing, and CRM products, averaging about 10 ms per request.
State or nationwide datasets delivered to AWS, Google Cloud, or Azure for analytics, models, and features that need the whole dataset.
Give assistants and agents the same property record through MCP, the Realie CLI, or plain REST, with machine-readable docs built for them.
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 record sits behind a two-person prototype and a national platform, and the price scales with usage rather than with company size.
Assessor, recorder, and GIS records collected at the source by AI agents, not relicensed from an aggregator.
The same field names and types in every county, so the integration you write for one market works in all of them.
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.
An MCP server, a CLI with JSON output, agents.md, and a published agent skill, so AI products integrate the same way developers do.
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 a product needs, where the data comes from, and how to access it.
The entry-point explainer for teams evaluating property data.
The walkthrough from first key to first feature.
What an agent needs from a property data API.
What the free tier includes and where it stops.
Parcel geometry, and how it differs from the assessor record.
Start free on the API, or talk to us about bulk delivery when the whole dataset belongs in your cloud.