The real estate data layer

Property data.
One clear API.

Bring property listings, source observations, and market context into your products. One contract across supported real estate platforms.

Get started Read the docs

Explore the API contract and check current source availability.

A common property language

Austin, Texas

Every observation has a source.

Typed prices & units

Source timestamps

Explicit coverage

REST & MCP

Illustration of the unified contract; not a live listing.

200

Platforms researched

Defined API operations

Common response contract

Built for the way property data works.

A listing is an observation from a source. A property is a physical asset. Keep the distinction, the original units, and the evidence.

Search across sources

Use consistent location and transaction selectors, with capabilities declared for each market.

Preserve provenance

Keep source URLs, timestamps, currencies, and explicit unknown values with your data.

Build with your tools

Use the REST API, OpenAPI contract, or MCP integration from your existing workflow.

FROM QUERY TO PRODUCT

Start with a location.
Keep the source.

Check source capabilities, choose your market, and request structured data. Unsupported operations return a clear error.

Explore the API

POST /v1/listings/search

curl https://realtycrawl.dev/v1/listings/search \
  -H "Authorization: Bearer $REALTYCRAWL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platforms":["zillow"],"location":{"kind":"bbox","bbox":[-97.82,30.2,-97.65,30.35]},"transaction":"sale","limit":10}'

Make room for better property products.

Explore the platform catalog and the API contract. Availability is published per source, operation, and market.

Explore platforms

Property data.One clear API.