Estated
Estated is a property-data company that operates a JSON REST API returning detailed U.S. residential and commercial property records — assessor data, parcel geometry, structure characteristics, taxes, assessments, market assessments, valuation (AVM), owner of record, deeds, and parcel boundaries. Lookups can be performed by split address, parsed address components, a single combined address string, or by FIPS county code + assessor parcel number (APN). The current public surface is the Property Data API v4 at `https://apis.estated.com/v4/property`, authenticated with a `token` query parameter. Estated was acquired by ATTOM Data in 2020 and its infrastructure is being migrated to ATTOM; the Estated developer documentation is scheduled to be deprecated during 2026, after which property data access will be served through ATTOM's documentation and endpoints. Existing Estated tokens continue to work through the transition and no integration changes are required during the migration window.
Estated publishes 1 API contract indexed on the APIs.io network: Property API. Tagged areas include Property Data, Real Estate, Property Records, Assessor, and APN.
The Estated catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
Estated’s developer surface includes authentication, documentation, signup flow, GitHub presence, and 15 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Real Estate and Proptech | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Estated Property API
The Property API from Estated — 1 operation(s) for property.
Open Collections 2
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Estated Data Property API
OPEN COLLECTIONEstated Property Data API
OPEN COLLECTIONEstated API pricing
Not yet checked against Estated's own pricing page. Compiled by API Evangelist; confirm before you rely on a figure.
| Plan | Price |
|---|---|
| Self-Serve / Developer usage-based | — |
| Subscription subscription | — |
| Bulk / Enterprise enterprise | — |
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Estated Rate Limits
RATE LIMITSService Levels 1
Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.
Estated
SLAFinOps 1
Cost, billing, and metering signals for API financial operations.
Estated Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Estated Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
Estated — jsonschema rules
SPECTRALEstated API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions for this provider's data models.
Estated Property
JSON SCHEMAExamples 1
Example request and response payloads for these APIs.
Estated Get Property Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 5
Properties that don't map to a standard resource type
Source (apis.yml)
Estated API — frequently asked questions
Does Estated have an API?
Yes. APIs.io lists 1 API from Estated, including Estated Property API.
Is there an OpenAPI specification for the Estated API?
Yes. APIs.io indexes 1 OpenAPI specification for Estated, each linked for download from this page.
How do I authenticate with the Estated API?
Estated uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Estated Authentication.
How much does the Estated API cost?
APIs.io lists 3 pricing plans for Estated, with each plan's price, limits and inclusions under Pricing on this page.
Is the Estated API ready for AI agents?
Estated has a Kin Score of 40.4 out of 100 (developing) and an Agent Readiness score of 28.9 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.