Quick Answer
The estated.com site now says Estated is part of ATTOM Data and labels its v4 docs as legacy, so a new build is a choice between ATTOM and another provider. Realie is the self-serve option: one address or parcel lookup returns parcel, owner, tax, sales, mortgage, boundary, and valuation fields, with ~20 ms average latency, a CLI, an MCP server, and a Free plan of 25 calls a month.
Start on the free tierSummary
Estated’s v4 property API returns one record per address or parcel number. estated.com now presents Estated as part of ATTOM Data, so teams on Estated, or about to start, are choosing between the acquirer and another provider. This guide reports Estated’s status only as estated.com publishes it, maps each Estated v4 data group to a field in the Realie v3 record, and shows how Estated requests translate to Realie calls. For ATTOM itself, it links the Realie vs ATTOM and ATTOM alternatives guides rather than repeating them. Confirm contract and roadmap details with ATTOM.
What are the key takeaways?
The estated.com site now presents Estated as part of ATTOM Data, labels its v4 documentation as legacy, and gives no shutdown date for the API (checked November 12, 2026).
Realie is our pick for a self-serve replacement. One address or parcel lookup returns a record with a counterpart for each Estated v4 data group: address, parcel, structure, taxes, assessments, market assessments, valuation, owner, deeds, and boundary. Map the fields your product reads before you switch.
Realie publishes ~20 ms average latency, a CLI and an MCP server (see Realie for agents), and self-serve plans: Free includes 25 calls a month, $50/mo includes 1,250, $150/mo includes 6,000, $350/mo includes 30,000, and enterprise pricing at $600/mo includes 100,000 (see Realie pricing).
Staying with ATTOM is the vendor’s own path. For that decision, read Realie vs ATTOM and ATTOM alternatives.
What happened to the Estated API?
As estated.com publishes it (checked November 12, 2026): the home page carries the banner “Estated is now part of ATTOM Data”, announces that ATTOM acquired Estated, and links the v4 docs as the legacy Estated API documentation. It shows no prices and points visitors to ATTOM.
The v4 documentation page says existing API keys stay valid while parts of the Estated API move to ATTOM infrastructure, with no integration change or downtime expected. It also says the Estated documentation itself will no longer be maintained or accessible after a 2026 deprecation date that estated.com has not set, with updated resources to come from ATTOM. estated.com gives no shutdown date for the API, so confirm your contract and roadmap with ATTOM.
For a new build, the practical question is whether to integrate against documentation that is scheduled for deprecation. Realie’s REST reference, OpenAPI spec, CLI guide, and MCP guide are public on docs.realie.ai.
How do Estated v4 fields map to Realie fields?
Estated’s v4 property object groups its fields into address, parcel, structure, taxes, assessments, market assessments, valuation, owner, deeds, and boundary. The table maps each group to the Realie v3 record documented in the property data schema. It maps groups, not individual fields, so check each field your product reads against the schema before you switch.
Realie’s record also carries recorded liens (tax liens, judgments, and mechanic’s liens from county recorder records), which have no Estated v4 group of their own. Fields with no value for a parcel are omitted unless you pass includeExplicitNulls=true.
| Estated v4 group | Realie v3 fields | What carries over |
|---|---|---|
| address | propertyLocation, latitude, longitude, location | Situs address parts, ZIP code, county FIPS, and the parcel centroid |
| parcel | parcelId, countyFips, propertyIdentification, landInformation, zoningInfo | Assessor parcel number, county, acreage and lot size, and zoning |
| structure | building, buildingInformation, roomInformation | Year built, stories, bedrooms, bathrooms, living area, and construction |
| taxes | taxInformation (with taxHistory) | Tax amount and tax year, with prior years |
| assessments | valuationInformation | Assessed land, building, and total values, the assessment year, and exemptions |
| market_assessments | valuationInformation.totalMarketValue, appraisalHistory | Assessor market values, with appraised values by year |
| valuation | realieValuation.ml (value, low, high) and realieValuation.comp (value, ppsf, count) | Realie’s machine-learning estimate with a low and high range, and a comparable-sales estimate |
| owner | propertyIdentification.currentOwner | Owner names, mailing address, and the owner-occupied flag |
| deeds | salesHistory, mortgages | Recorded sales and transfers, and mortgages with lender and loan terms |
| boundary | geometry | Parcel boundary as a GeoJSON MultiPolygon |
How do Estated lookups translate to Realie requests?
Estated v4 takes the API key as a token query parameter and finds a property by a combined address string, by split or parsed address parts, or by a county FIPS code plus APN. Realie sends the key as the header Authorization: Bearer YOUR_API_KEY and has one endpoint per identifier (see the Realie REST API).
Address: state and address are required; county and city narrow the match, and unitNumberStripped picks one unit in a multi-unit building. For example:
curl -H "Authorization: Bearer YOUR_API_KEY" "https://app.realie.ai/api/public/property/address/?state=TX&county=TRAVIS&address=504%20LAVACA%20ST"From a terminal or a coding agent, run the same lookup with the CLI:
realie --json lookup --address "504 LAVACA ST" --state TX --county TRAVISFIPS plus APN: the parcel lookup takes the state, the county, and the assessor parcel number as parcelId, for example:
realie --json parcel --parcel-id "R12345" --state TX --county TRAVISEach successful lookup is one call against your plan, and an address that matches nothing returns a 404 that costs nothing. Agents in Claude, Cursor, and other MCP hosts can run the same lookups through the MCP server instead of HTTP.
Which option fits which situation?
Most Estated users fall into one of these situations. The first four rows favor moving; the last two favor staying with the acquirer.
| Situation | Best fit | Why |
|---|---|---|
| Starting a new integration that needs maintained public docs and self-serve keys | Realie | Published plans, OpenAPI spec, and CLI and MCP guides on docs.realie.ai |
| Parcel, owner, tax, sale, mortgage, boundary, and valuation fields from one address call | Realie | One v3 record with a counterpart for each Estated v4 group |
| Lookups inside a live user request | Realie | ~20 ms average published |
| Scripts and coding agents | Realie | CLI with --json plus an MCP server on the same self-serve account |
| Keeping existing Estated keys and code unchanged for now | Stay on Estated under ATTOM | estated.com says existing keys stay valid during the move to ATTOM infrastructure |
| ATTOM data products beyond county public records | ATTOM | Compare on the Realie vs ATTOM and ATTOM alternatives guides |
How did we compare these vendors?
We did not score vendors subjectively. Each option is compared on values you can re-check on the linked pages:
1. Vendor status as the vendor publishes it: estated.com’s ATTOM banner and legacy v4 documentation, read on November 12, 2026
2. Field-group coverage: each Estated v4 data group except request metadata, mapped to a Realie v3 field in the table above
3. Lookup inputs: Estated’s address and FIPS-plus-APN lookups against Realie’s address and parcelId endpoints
4. Published self-serve plans: Realie Free includes 25 calls a month and $50/mo includes 1,250; estated.com lists no prices and points buyers to ATTOM
5. Published latency: Realie ~20 ms average (docs.realie.ai); measure any other provider from your own stack
6. Agent access: Realie’s CLI and MCP server on the same self-serve account as REST
Sources
- estated.com: “Estated is now part of ATTOM Data” (checked 2026-11-12)
- Estated v4 documentation: API keys stay valid; docs to be deprecated in 2026 (checked 2026-11-12)
- Estated v4 API overview: request parameters (checked 2026-11-12)
- Estated v4 property object schema (checked 2026-11-12)
- Realie v3 property data schema
- Realie address lookup
- Realie parcel ID lookup
- Realie CLI
- Realie MCP server
- Realie plans and included calls
Frequently asked questions
- Is Estated shutting down?
- The estated.com site gives no shutdown date for the API. As of November 12, 2026, it says Estated is now part of ATTOM Data, that existing API keys remain valid while parts of the API move to ATTOM infrastructure, and that the Estated documentation will no longer be maintained or accessible after a 2026 deprecation date that estated.com has not set. Confirm your own contract terms with ATTOM.
- What are the best Estated API alternatives?
- For county public-records lookups by address or APN, Realie is the closest self-serve replacement: one record has a counterpart for each Estated v4 data group, with published plans, ~20 ms average latency, a CLI, and an MCP server. If you would rather stay with the acquirer, ATTOM is the vendor’s own path; the Realie vs ATTOM guide compares the two.
- How does Realie compare to Estated?
- Both return a property record from an address or a county parcel number. Realie’s record also carries recorded liens and a comparable-sales estimate next to its model value, and it runs on published self-serve plans that start with Free at 25 calls a month. estated.com lists no prices and now points buyers to ATTOM.
- How do I migrate off the Estated API?
- List the Estated fields your product reads and map each group to the Realie v3 record using the table on this page. Then swap the request: the token query parameter becomes an Authorization: Bearer header, an address becomes the address endpoint’s state, address, county, and city parameters, and FIPS plus APN becomes a parcelId lookup with state and county. Test your counties on the Free plan before you cut over.
- What does each Realie plan include?
- Each Realie plan includes a monthly allowance of calls: Free includes 25, $50/mo includes 1,250, $150/mo includes 6,000, $350/mo includes 30,000, and enterprise pricing at $600/mo includes 100,000. A call is one successful request (HTTP 200). An address or parcelId lookup returns one property, and a REST or CLI search page returns up to 100 parcels, so the $50 plan covers up to 125,000 parcels through search. Failed requests (404/401/403) do not count.
- What does Realie’s free tier include?
- Realie Free includes 25 tokens a month on the same production dataset and endpoints as paid plans. Each successful call uses one token, a search page of up to 100 parcels is one call, and 404/401/403 responses cost nothing. New accounts add a payment method before generating an API key.
- Does Realie return a valuation like Estated’s valuation object?
- Yes. Realie returns its own automated valuation in realieValuation: a machine-learning estimate, ml, with value, low, and high, and a comparable-sales estimate, comp, with its value, the median price per square foot (ppsf), and the number of comparable sales used (count). Accounts on the older v2-compatible flat response shape get the same estimates as modelValue and compModelValue. Treat it as a reference value, not an appraisal.